Roles can be applied to various modules to customize the experience of your teams. Applying a role is specific to a context. For example, you can select who will be administrators of a space, who will be able to interact with our CLI in a site, etc.
Modyo has 10 default roles with different functions by area or application. The platform also allows you to create more custom roles, depending on the area of the platform.
This are the predetermined roles that Modyo Platform offers:
Account-level roles:
Default user: You have all existing permissions, except editing the settings for each context. This user must be invited to each context to access its functionality.
Default admin: You have all existing permissions, but you must be invited to an area of the platform in order to access its functionalities.
Owner: You have all existing permissions and can access all contexts without needing to be invited to them.
Site-level roles:
Site developer: You can only edit resources (you cannot publish, delete, roll back, or edit the configuration).
Site developer CLI: Same permissions as a Site developer with access to modyo-cli.
Site reviewer: A site admin, but without the ability to edit the site configuration.
Site admin: You have all the permissions at the level of a site, but you cannot create new sites.
Space-level roles:
Space writer: You can only edit content (you cannot publish, delete, roll back, or edit settings).
Space editor: A space admin, but without the ability to edit the space configuration. This role does not have asset permissions, nor can it create types.
Space admin: You have all the permissions at the level of a space, you can create and delete assets, but you cannot create new spaces.
To assign permissions to a group of members, you can use Groups.
For more information about Teams, Groups, and Roles, visit our documentation.