System-managed developer and deployment roles
Although system admins can still manually assign and remove the user roles, they’re encouraged to let the system manage the following delegated developer roles.
To learn more about managing per-user subscriptions, see Managing per-user subscriptions in Subscription Management and contact your account representative.
| Role | Description |
|---|---|
| delegated_developer | User has one or more developer permissions. |
| Roles that start with an sn_dd prefix (for example, sn_dd_<app_name>_upgrade_app) | User has an application-specific developer permission. The role name indicates the application scope to which it applies. For example, after a user with a sn_appclient.app_client_company_installer role installs a company application, the system automatically grants a sn_dd_<app_name>_upgrade_app delegated deployment role. This role enables you to upgrade the application when future updates are published to the Application Client page. |
| glide.security.add_admin_contained_roles_to_system | Default Value: true if the property is true, then all the roles, directly or indirectly contained by the admin role, are added to the system user, including the scoped-admin roles. Note:
Setting the property to false results in the system user having the admin role, but not any of the scoped-admin roles contained by the admin role. Example: The admin role contains the sn_templated_snip.template_snippet_admin role Old behavior: The system user doesn’t have the sn_templated_snip.template_snippet_admin role. New behavior: The system user has the sn_templated_snip.template_snippet_admin role and other scoped roles that it contains. |