---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Roles and access in app development tools

# Roles and access in app development tools {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE is controlled by the roles and permissions your admin assigns. Update role assignments when you need to change which tools a user can access.  
Each development tool available through the experience switcher has specific role requirements. To access all development tools, you need the roles required for each tool individually. For example, the delegated_developer role provides access to ServiceNow Studio, but without the admin and sn_creatorstudio.user or sn_creatorstudio.restricted_user roles, the experience switcher is not visible because you do not have access to the other tools.  
Note:  
If you expect to see the experience switcher but do not see it, contact your admin. Custom configurations may affect which experiences are visible.
{#working-with-roles-and-access__table_sjh_nrn_zdc__entry__3}

| Experience | Available for | NOT available for |
|-|-|-|
| Pro-coding experience in ServiceNow IDE | admin | sn_creatorstudio.restricted_user, sn_creatorstudio.user |
| Platform developer coding experience in ServiceNow Studio | delegated_developer, admin, sn_g_app_creator.app_creator | sn_creatorstudio.restricted_user, sn_creatorstudio.user |
| No-code experience in Creator Studio | delegated_developer, admin, sn_creatorstudio.user, sn_creatorstudio.restricted_user | Not applicable. |
[Table 1. Development experiences and roles]

{#working-with-roles-and-access__table_sjh_nrn_zdc}  
Important:  
Regardless of your role --- including admin and delegated_developer --- if you have a Creator Studio role, you cannot access ServiceNow Studio or ServiceNow IDE.

For more information, see [Creator Studio roles and personas](https://servicenow-prod.fluidtopics.net/HrOQlP2NVlDxTiy7c5uTlw "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."), [ServiceNow Studio personas and roles](https://servicenow-prod.fluidtopics.net/oxT2dyWKptcpz35guxx38g "Admins, delegated developers, and users with Guided Application Creator roles can access and develop in ServiceNow Studio. Each role has different capabilities and permissions."), and [ServiceNow IDE roles](https://servicenow-prod.fluidtopics.net/zwkm76iWqHl5lLRxWtZeXg#servicenow-ide-roles "The following roles are installed for use with ServiceNow IDE.").

## What are some role assignment examples? {#working-with-roles-and-access__section_frs_2tq_12c}

As an admin, you can assign permissions to use ServiceNow Studio, Creator Studio, and ServiceNow IDE. Some roles provide access to more than one tool:

* To grant access to ServiceNow Studio and Creator Studio, assign the delegated_developer role. This role provides access to both tools but does not include access to ServiceNow IDE.
* To restrict users to Creator Studio only, assign the sn_creatorstudio.user or sn_creatorstudio.restricted_user role. These roles provide access to Creator Studio but not ServiceNow Studio.
* To grant access to ServiceNow IDE, the user must have admin permissions or other roles specific to ServiceNow IDE. Users with the delegated_developer role cannot access ServiceNow IDE. For more information, see [ServiceNow IDE roles](https://servicenow-prod.fluidtopics.net/zwkm76iWqHl5lLRxWtZeXg#servicenow-ide-roles "The following roles are installed for use with ServiceNow IDE.").
{#working-with-roles-and-access__ul_ynw_jwq_12c}