Working with roles and access in app development tools

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Working with Roles and Access in App Development Tools

    Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE is determined by roles and permissions set by an administrator. Understanding these roles is essential for developers to effectively utilize the available development tools within ServiceNow.

    Show full answer Show less

    Key Features

    • Role-Specific Access: Each development tool requires specific roles for access. For example, the delegateddeveloper role allows access to ServiceNow Studio but not to other tools unless additional roles are assigned.
    • Experience Switcher: Users must have the necessary roles to see the experience switcher. If it is not visible, users should contact their admin.
    • Role Assignment: Admins can assign roles to users, affecting their access to various tools. Certain roles grant access to multiple tools, while others restrict it.

    Key Outcomes

    • To access all development tools, users must have the required roles for each tool individually.
    • Assigning the delegateddeveloper role allows access to both ServiceNow Studio and Creator Studio, but not to ServiceNow IDE.
    • Users assigned sncreatorstudio.user or sncreatorstudio.restricteduser roles will be limited to Creator Studio and cannot access ServiceNow Studio or ServiceNow IDE.
    • Admin permissions or specific ServiceNow IDE roles are necessary for access to ServiceNow IDE.

    Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE depends on the roles and permissions your admin sets. However, there are some scenarios in which you might want to update the roles allowed to access each tool.

    Each development tool that you can access through the experience switcher has roles that it is available for and not available for. To access every development tool, you need to have the roles required for each tool individually. For example, if you have the delegated_developer role, you can work in ServiceNow Studio. However, if you don't also have admin and sn_creatorstudio.user or sn_creatorstudio.restricted_user roles, you won't see the experience switcher because you don't have access to the other tools.
    Note:
    If you're expecting to see the experience switcher and don't see it, please contact your admin. Custom configurations may affect the experiences you can see.
    Table 1. Development experiences and roles
    Experience Available for NOT available for
    Access to the pro-coding experience in ServiceNow IDE admin sn_creatorstudio.restricted_user, sn_creatorstudio.user
    Access to the platform developer coding experience in ServiceNow Studio delegated_developer, admin, sn_g_app_creator.app_creator sn_creatorstudio.restricted_user, sn_creatorstudio.user
    Access to the no-code experience in Creator Studio delegated_developer, admin, sn_creatorstudio.user, sn_creatorstudio.restricted_user Not applicable.
    Important:
    No matter what your role is (including admin and delegated developer roles), if you have one of the Creator Studio roles, you won't be able to access ServiceNow Studio or ServiceNow IDE.

    For more information, see Creator Studio roles and personas, ServiceNow Studio personas and roles, and ServiceNow IDE roles.

    Role assignment examples

    As an admin, you can assign permissions to use ServiceNow Studio, Creator Studio, and ServiceNow IDE. Some roles give access to more than one tool and could be used in the following scenarios:
    • If you want to assign access to ServiceNow Studio and Creator Studio, assign your user the delegated_developer role. This will give them access to both tools. However, this role does not give access to ServiceNow IDE.
    • If you want users to stay in Creator Studio, assign them the sn_creatorstudio.user or sn_creatorstudio.restricted_user roles. These roles give access to Creator Studio but not ServiceNow Studio.
    • If you want to assign access to ServiceNow IDE, your user must have admin permissions or other roles specific to ServiceNow IDE. If your user also has the delegated_developer role, they will not be able to access ServiceNow IDE. For more information, see ServiceNow IDE roles.