User Roles¶
Note
Predefined user roles are available starting from the Basic plan and above. Custom Flotiq user roles can be customized in the Growth plan and above.
What is a User Role?¶
A user role represents a specific set of actions assigned to a group of users. By assigning user roles, you can control the actions each user can perform in the system. The actions that can you determine are:
- Read: Permits users to view existing content without making changes.
- Create: Allows users to add new content.
- Update: Grants permission for users to make changes to existing content.
- Delete: Provides authority for removing content.
User role allows you to restrict the actions for specific Content Type Definition or Content Type Objects.
Note
Managing user roles is available only for Organization Admin
. It’s important to note that a user without any assigned role has unrestricted access to all resources.
Predefined User Roles¶
In Flotiq, predefined user roles streamline the management of user permissions, ensuring that users can perform only the actions their roles permit. These roles cover typical organizational needs.
Warning
Users without any assigned role have unrestricted access.
Note
Predefined roles can be modified in the Growth plan and above
Available Predefined Roles¶
Admin¶
- Description: Full access to all resources.
- Permissions:
- CO: Read, create, update, delete.
- CTD: Read, create, update, delete.
Content Editor¶
- Description: Manages and edits content.
- Permissions:
- CO: Read, create, update, delete.
- CTD: Read.
Viewer¶
- Description: Limited to viewing content.
- Permissions:
- CO: Read.
- CTD: Read.
These predefined roles help control user actions and maintain system security. For custom permissions, please contact our support team.
List User Roles¶
To manage user roles, navigate to the dedicated User Roles section within the application. In this section, you have the ability to customize grid column widths and set the results per page limit.
Assign User Role¶
- Navigate to the
Users
tab in the Organization management view. - Find a user and edit their details.
- In the right sidebar, you’ll find a dropdown with existing user roles within a single space. If you have multiple spaces, you’ll see several forms with roles. If a space doesn’t have any roles added, the form won’t be visible.
Custom User Roles¶
Note
Custom Flotiq user roles are available starting from the Growth plan and above.
Add User Role¶
You can create new user roles by clicking the Add User Role button or duplicate existing ones in the list view.
- Role Creation: To add a new user role, complete the form by providing a name, description, and at least one rule. These rules determine the permissions associated with the role.
- Assigning Actions: You can assign various actions to different Content Types. If you need additional rules, click Add Rule. To remove a rule, simply click the trash icon.
- Rule Types:
CO
: These rules apply to specific Content Objects of a certain Type. However, for managing the type definition itself, add a separate rule with theCTD
type.CTD
: These rules apply to Content Type Definitions.
Note
An essential point to note is that every Content Type has read access to its definition via the API. However, these definitions remain hidden in the dashboard until you explicitly add a rule granting read access for a specific definition.
Examples¶
Hint
In the examples, the media, webhook, and plugin pages are not visible in the menu. They require additional permissions for managing.
Read Blogposts¶
Users have read access to Content Objects of Type Blogposts. However, they won’t be able to view the definition of Blogposts in the Definition Builder section.
Outcome for the user with the assigned role:
Manage Blogposts and read Content Type Definitions¶
We grant users permission to perform any action with Content Objects of type Blogposts and allow them to read any Content Type Definitions in the Dashboard.
Outcome for the user with the assigned role:
Manage Content Type Definitions¶
We grant users permission to perform any action with any Content Type Definitions, but disallow them from interacting with their Content Objects.
Outcome for the user with the assigned role: