Creator Studio roles and personas
Roles control what everyone you work with can do in Creator Studio. Administrators assign roles to give team members permission to configure or use Creator Studio.
The two roles for Creator Studio are used to restrict access from creating new apps, which helps make sure your instance isn't overfilled with redundant, unplanned, or unused apps.
Personas that use Creator Studio
Personas aren’t explicitly part of Creator Studio, but administrators assign roles to give team members permission to configure or use Creator Studio.
- Low-code/citizen developer
- Low-code/citizen developers are tech savvy and interested in creating apps. Though they might not have formal coding or app development training, citizen developers can submit ideas for new apps and, if approved, build them
using Creator Studio.
Low-code/citizen developers have either the sn_creatorstudio.user or sn_creatorstudio.restricted_user role.
- App Engine admin
- App Engine admins manage all processes related to app development in Creator Studio. They review new app ideas, handle app deployment, and manage collaborators, usually in the App Engine Management Center.
App Engine admins have the app_engine_admin role and must be in the app_engine_admin group.
- Security admin
- The security admin creates and modifies roles and access control lists for apps. This role is set on the platform level, and it is required for making updates to roles in Creator Studio.
- System administrator
- The system administrator has access to all system features, functions, and data, regardless of security constraints. Grant this privilege carefully. If you have sensitive information, such as HR records, that you must protect, create a custom admin role for that area and train a person who is authorized to see those records to act as the administrator.
Roles and what they can do in Creator Studio
In addition to the roles in the following table, users with the admin and delegated_developer roles can also access Creator Studio.
For complete details on which roles each role contains, see Components installed with Creator Studio.
| Role | Name | Description |
|---|---|---|
| Creator Studio User | sn_creatorstudio.user |
注:
This role gets assigned the delegated_developer role when they create or get access to an app. |
| Creator Studio Restricted User | sn_creatorstudio.restricted_user |
|
| App Engine Admin | app_engine_admin |
|
| Now Assist for Creator | now.assist.creator | Grants users access to Now Assist for Creator skills to create forms in Creator Studio. |
| Creator Studio configuration admin | sn_creatorstudio.configuration_admin | Granular admin role that contains the following Creator Studio granular admin roles:
|
| Task admin | sn_creatorstudio.task_admin | Granular admin role that grants users access to change several fields on the Request Task table or a table that extends Request Task. This role contains the following:
|
| App configurator | sn_creatorstudio.app_configurator | Granular admin role that grants users access to change the associated table for an app built in Creator Studio. |
| Reports viewer | sn_creatorstudio.reports_viewer | Granular admin role that grants users access to run reports on tables. |
To ensure that users can use the Collaboration Approval Workflow regardless of instance versions, admins must assign the catalog _builder_editor role to Creator Studio user groups.
User groups and what they can do in Creator Studio
Groups are a standard functionality that help you quickly control people's access to Creator Studio by adding them to a group.
| Group | Description |
|---|---|
| Creator Studio Users |
|
| Creator Studio Restricted Users |
|
Developer roles and testing apps on instances
If you have a Creator Studio role of sn_creatorstudio.user or sn_creatorstudio.restricted_user, you won't be able to test the apps you build on the non-production instance's Request App Workspace. You should be able to test the app on the non-production instance using Creator Studio's app previews. You will be able to test the apps as a fulfiller in the workspace on the app that's been deployed to production.
Let's say that a user is in the Creator Studio Users group, so when that user builds an app, that user gets delegated development permissions for that app. That user can then publish a request form, and if there are no roles required for the form, that user can submit requests with the form.
However, that user won't be able to fulfill requests or access the Request App Workspace because that user won't have the x_acme_user_app.agent role, and that user can't give that role to themself. Administrators must assign additional roles as necessary.
Collaboration roles and instances on different versions
As admins implement Creator Studio, they may have it installed on a non-production instance while their production instance is on a previous version of the ServiceNow AI Platform that doesn't have Creator Studio. This mis-match of instance versions affects the Collaboration Approval Workflow, which specifies the non-production instance as the source and the production instance as the controller. If the controller doesn't have the version of the collaboration plugin that supports Creator Studio, collaboration is unsupported.
To ensure that users can use the Collaboration Approval Workflow regardless of instance versions, admins must assign the catalog _builder_editor role to Creator Studio user groups.
Roles and app development collaboration
Roles define user access to Creator Studio. Permission to work on individual apps is controlled on an app-by-app basis. That is, you must manage the collaborators for each app by inviting other citizen developers to work on the app with you, or request to join someone else's app. For more information, see Collaborating with others to build apps in Creator Studio.