--- 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 --- # Personas and roles # ServiceNow Studio personas and roles {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 ServiceNow Studio personas and roles ServiceNow Studio supports various personas and roles that define access levels and development capabilities within the platform. These roles enable admins, delegated developers, Guided Application Creator users, and specialized admins to collaborate effectively on app creation and management. Understanding these roles helps you assign appropriate permissions and streamline app development workflows. Show full answer Show less ## Roles and Capabilities * **Delegated Developer (delegateddeveloper)**: Access is limited to assigned applications. Capabilities include accessing ServiceNow Studio, updating apps they have permission for, creating update sets, modifying app files and metadata, and submitting apps for deployment. * **Admin**: Full access to ServiceNow Studio functionalities. Admins can create and edit apps and metadata, delegate development tasks, manage update sets, approve development tasks, and create Fluent apps from source code. * **Guided Application Creator (GAC) roles**: Users with these roles can create custom applications in ServiceNow Studio. Upon app creation, they gain delegateddeveloper permissions for that application. The GAC Global role additionally allows creating global scoped apps. * **ServiceNow Studio admin / Unified Developer Core (UDC) admin (snudc.admin)**: Provides granular administrative control over Studio system properties, settings, roles, permissions, and experience switcher configurations across development tools. * **Preferred tables admin (snprfrdtables.admin)**: Enables configuration of preferred tables specifically for Table Builder, enhancing table management within the instance. * **Metadata-specific admin roles** (e.g., Business rule admin, Script include admin): Grant CRUD permissions on specific metadata types, allowing focused administrative control over elements like script includes within ServiceNow Studio. ## Practical Implications for Customers * Assign **delegateddeveloper** roles to users who need focused access to specific app projects without full admin privileges. * Use **Admin** roles for users responsible for overarching app development, approval, and delegation. * Leverage **GAC roles** to empower business users or developers to quickly create applications with automatic assignment of delegated developer rights. * Utilize **granular admin roles** to delegate specific administrative functions related to Studio configurations and metadata management, promoting security and operational efficiency. 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://servicenow-prod.fluidtopics.net/CgpnWB2etwd_1u317hbZkg "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 | |-|-|-| | 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} | | 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} | | 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=australia&pubname=australia-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}