Configure Creator Studio using Guided Setup
- UpdatedSep 9, 2025
- 8 minutes to read
- Zurich
- Creator Studio
So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
Before you begin
Creator Studio must be installed on the instance before you can configure it. Find out more about that in Installing Creator Studio from the ServiceNow Store.
To ensure that forms appear correctly for users, the non-production and production instances must have the same Service Catalog and all of its categories.
Role required: admin
About this task
Guided Setup streamlines configuring Creator Studio, and keeps track of what you have completed, so you can stop and start again where you left off.
In this Guided Setup, you'll configure user access and collaboration settings to control who can do what in Creator Studio.
Procedure
What to do next
- Set up the Creator Studio admin group
- Set up Creator Studio collaboration descriptors
- Set up Creator Studio full access users
- Set up Creator Studio restricted access users
- Set up Creator Studio playbook activities
- Configure the table for Creator Studio apps
- Set up Creator Studio custom notification emails
What to do next
After you finish configuring Creator Studio, you can configure Pipelines and Deployments to enable apps built in Creator Studio to be deployed to production. For information on how, see Configure Pipelines and Deployments.
Set up the Creator Studio admin group
Set up the admin group to enable ServiceNow administrators access to work on and configure Creator Studio.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Before you begin
Role required: admin
Procedure
What to do next
Set up Creator Studio collaboration descriptors
Set up collaboration descriptors to manage what app Owner and Editor collaboration types can do in Creator Studio.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Role required: admin
Procedure
What to do next
Set up Creator Studio full access users
Set up who has full access to Creator Studio to decide which users get full access to work on app in Creator Studio, and who has more limited capabilities.
About this task
For example, restricted users must request that an admin create a new app for them. For more information, see Creator Studio roles and personas.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Role required: admin
Procedure
What to do next
Set up Creator Studio restricted access users
Set up limited access for Creator Studio users. People in the Creator Studio Restricted Users Group have limited access to working with apps, and must request that admins create apps for them.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Role required: admin
Procedure
- Navigate to .
- Select the Configure button for the Grant Creator Studio Restricted access to users section.
- Add users to the Creator Studio Restricted Users Group.
- Update the record to save your changes.
- Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.
Set up Creator Studio custom notification emails
Configure customized email notifications that Creator Studio apps send. For example, you can add branding to notification emails that a request was opened.
About this task
Customized email templates can be applied to notifications that are sent when users request something from an app, or the request was changed or closed.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Role required: admin
Procedure
Set up Creator Studio playbook activities
Configure the activities that appear when users build playbooks in Creator Studio.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
Role required: admin
Procedure
What to do next
Users who are actively working in Creator Studio must refresh their browser to see the changes you just made.
Configure the table for Creator Studio apps
Use Guided Setup to change the table that the app saves its requests to.
About this task
- If you change an app's table to one that doesn't extend a Request Task-extended table, it could affect automations.
- If the new table doesn't have the request_type field, the app's automations won't be correctly triggered.Note: You can change the Request type field, which specifies the form, on the Request Task table or a table that extends Request Task. To do so, you must be an admin or have the sn_creatorstudio.configuration_admin or sn_creatorstudio.task_admin role.
- The request_type field for the new table should have the label Request type, and it should be a reference to the Record Producer table.
- If the new table isn’t in the same scope as the app, the scope of the table must allow updates from other scopes.
Before you begin
Initiate the Guided Setup as described in Configure Creator Studio using Guided Setup.
The app must already be created before you can change the table for it.
Before you begin
Role required: admin, app configurator (sn_creatorstudio.app_configurator), or Creator Studio configuration admin (sn_creatorstudio.configuration_admin). For more information on working with granular roles, see Granular admin roles required to secure your instance.
Procedure
Result
The associated table for an app changes to the new table. Any users currently in Creator Studio may need to refresh their browser to see the change.
or press Enter.