Advocate Roles and Permissions enable admins to manage Advocate access to the Advocacy Board's features and capabilities. Each Advocate is assigned a role when they are invited to the Board. Each role has a set of permissions associated with it.
By default, Click Social offers three pre-configured roles:
- Advocate: Can view the Leaderboard and share Messages added to the Board by Admins. Cannot recommend content for sharing or publish their own content.
- Contributor: Default role. Can view the Leaderboard, share Messages added to the Board by admins, and recommend content for sharing. Cannot publish their own content.
- Champion: Has access to all Advocacy features: can view the Leaderboard, share Messages added to the Board by admins, recommend content for sharing, and share their own content (including image attachments) from the Board to their connected social profiles. This is available for X (Twitter) and LinkedIn posts.
Please note that some of the permissions (Leaderboard, Suggestions, etc.) are available only based on which features are enabled in the Board's Settings.
Advocate roles can be assigned one-by-one or in bulk, and later changed under Board > Advocates.
You can also create and define Custom Roles based on the specific requirements of your Advocacy program.
Creating a Custom Role
Board admins can configure Custom Roles per each Board under Board > Settings > Roles. Each permission reflects the access level to one of the Board functions.
The four available access levels are View, Create, Update, and Delete. The permission types for advocates are described below.
- Posts: Create and share Advocates' own content.
- Messages: Edit and share existing advocacy Messages.
- Leaderboard: Access the Leaderboard
- Suggestions: Send content suggestions to admins.
- Media: Add and remove media attachments for advocacy messages.
When creating a new role you can define the access level to each function by checking the appropriate checkbox. If a checkbox is missing from a certain permission, that means that this permission does not apply to that specific function.