---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Personas and roles

# ServiceNow Studio personas and roles {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Admins, delegated developers, and users with Guided Application Creator roles can access and develop in ServiceNow Studio. Each role has different capabilities and permissions.

## What can each role do in ServiceNow Studio? {#sn-studio-personas-roles__section_ys2_pnd_dbc}

Admins and delegated developers have different capabilities in ServiceNow Studio. Admins can delegate users to work on specific apps and app files by assigning delegated_developer permissions.  
For more information about roles and access to different app development tools, see [Roles and access in app development tools](https://www.servicenow.com/docs/2NtXOjHA4vO9eDNZsLeTZQ "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.").{#sn-studio-personas-roles__table_clb_2w1_xcc__entry__3}

| Role | Permissions | Capabilities |
|-|-|-|
| Admin | Admins can review and approve tasks related to custom application development. | * Access ServiceNow Studio. * Create apps in ServiceNow Studio. * Create Fluent apps in source code from the Explorer tab. * Edit existing apps and metadata records, or delegate development to another user. * Create, edit, and manage update sets. * Update existing metadata records. * Create and edit global (unscoped) metadata records. {#sn-studio-personas-roles__ul_vz5_pk2_ycc} |
| Delegated developer (delegated_developer) | Delegated developers have access only to the apps they are assigned to. Permissions may vary based on your configuration. | * Access ServiceNow Studio. * Update apps they have delegated development permissions for. * Create an update set to package changes. * Create and update app files and other metadata records. * Submit an app for deployment through update sets, pipelines, or the Application Repository. {#sn-studio-personas-roles__ul_ilg_kk2_ycc} |
| Delegated admin (Delegated developer with delegated_admin permission) | Delegated admins only have access to the scopes they have delegated developer access to. | Grants access to all delegated development permissions for a specific scoped application so that permissions don't need to be granted individually. For more information, see [Developer and deployment permissions](https://www.servicenow.com/docs/ZLbgCOrPSPAna2NJCiQgEg "Using Manage Developers, administrators can assign one or more developer and deployment permissions to a group or user for a specific application. These permissions designate the specific actions the assigned user can perform for the application."). |
| Guided Application Creator (GAC) roles (sn_g_app_creator.app_creator, sn_g_app_creator.global) | Users with GAC roles can access ServiceNow Studio and create apps. After creating an application, the user receives the delegated_developer role for that application. | * Access ServiceNow Studio. * Create custom applications. * With the GAC Global role, create custom global apps. {#sn-studio-personas-roles__ul_q5w_53t_ydc} |
| ServiceNow Studio admin / Unified Developer Core (UDC) admin (sn_udc.admin) | Provides administrative access to tables within ServiceNow Studio scope and configuration access to the experience switcher roles. | Granular admin role that enables the following actions: * Manage all ServiceNow Studio system properties, settings, and configurations. * Manage roles and permissions specific to ServiceNow Studio. * Configure the experience switcher roles across Creator Studio, ServiceNow Studio, and ServiceNow IDE. {#sn-studio-personas-roles__ul_jwk_nkf_fhc} For more information about granular admin roles, see [Granular admin roles](https://www.servicenow.com/docs/access?context=granular-admin-roles&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). |
| Preferred tables admin (sn_prfrd_tables.admin) | Provides administrative access to configure preferred tables for Table Builder. | Granular admin role that enables you to configure preferred tables in your instance for Table Builder. Note: Table Builder does not require an additional admin role. |
| Metadata-specific admin roles * Business rule admin * Script include admin {#sn-studio-personas-roles__ul_zxl_14f_fhc} | Provide access to ServiceNow Studio. | Metadata-specific admin roles are existing roles on the ServiceNow AI Platform that provide developers with admin access to a specific metadata type. For example, the script include admin role enables a developer to create, read, update, and delete (CRUD) any script include on the ServiceNow AI Platform and perform development on script includes in ServiceNow Studio. Each metadata-specific admin role must: * Enable CRUD access to the metadata types it represents directly within ServiceNow Studio. * Be configurable within the experience switcher. {#sn-studio-personas-roles__ul_xlx_jpf_fhc} |
[Table 1. Roles and capabilities]

{#sn-studio-personas-roles__table_clb_2w1_xcc}