Here, we discuss what roles and permissions are needed to manage webhooks. We also discuss how to create a role that can manage webhooks and assign that role to a member.
In order to see, configure, and use webhooks, members of your organization must have the right permission/role.
Note: In order to manage webhooks, your plan must enable them. A user with the proper permission/role will not be able to manage webhooks if the organization’s subscription does not enable them.
A member must have a role with the
Change Organization Profile permission1 to manage webhooks.
Note: As the name implies, this permission gives the user the ability to do more than just manage webhooks. Since webhooks work at the organization level, it makes sense to have this permission tied to managing webhooks.
By default, the only role to have the above permission is the
Owner System Role. This means the owner is initially the only person who can do anything with webhooks.
The organization’s owner (or any member with the
Manage Roles permission) can create another role to have the
Change Organization Profile permission. They can then give a member this role, and that member will be able to manage the webhooks.
To create a role with the permissions to manage webhooks, follow these steps:
Settings. If you were in another organization, on the left menu, click the organization you’re interested in.
Rolesin the list of links for that org’s settings.
Change Organization Profilepermission.
(steps 5-7 not shown in image)
This role is now available for use. Members with this role will have the ability to manage webhooks.
Note: These steps are for creating a new role, but you can also modify an existing, custom role to have this permission.
Once you’ve created a custom role with the
Change Organization Profile permission, you can assign it to an existing member with the following steps:
Settings. If you were in another organization, on the left menu, click the name of the organization you’re interested in.
Membersin the list of links for that org’s settings.
Editnext to the applicable member’s name.
Now this member has a role with the permission needed to manage webhooks. They will see the
Webhooks link in the organization’s settings links, be able to add and modify webhooks through the website, and access webhooks through the API.
Now you can get started using webhooks!
This permission is called
can_update_organization in the API. ↩