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.
Permission
A member must have a role with the Change Organization Profile permission 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.
Roles
System Role
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.
Custom Role
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.
Creating a Role for Webhooks
To create a role with the permissions to manage webhooks, follow these steps:
Click Roles tab in the navigation pane/sidebar on the left side of the Fulcrum web app.
Click Add Role.
Enter a Role Name (and optional Description).
Check the Change Organization Profile permission and any other permissions you would like to have this role to have.
Click Save Role.
This role is now available for use. Members grant 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.
Next Step
Now you can get started using webhooks!