---
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


---

# Configure personas and roles

# Configure AES personas and roles {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Configure AES Personas and Roles

In App Engine Studio (AES), user responsibilities are managed through assigned roles rather than explicit personas.
Administrators assign roles to team members to control their permissions for configuring and using AES.
Understanding these roles helps ServiceNow customers appropriately allocate tasks and permissions to support efficient app development and governance.
Show full answer Show less  

## Key Roles and Their Responsibilities

* **Low-code/Citizen Developer:** These users are tech-savvy individuals who can submit app ideas and build applications in AES without formal coding training. They are assigned the `snappengstudio.user` role and are responsible for building, testing, and maintaining applications.
* **App Engine Studio Admin:** Admins manage app development processes, review app submissions, control user access, handle deployments, and coordinate application conflict resolutions. They possess multiple roles including `snappengstudio.admin` and collaborate closely with system administrators.
* **App Template Admin and Author:** Template admins control access to predefined and custom app templates, activating, deactivating, and sharing them. Template authors create and edit these templates and share them with users or groups.
* **Security Admin:** Responsible for creating and modifying roles and access control lists related to AES; this platform-level role is essential for managing security permissions.
* **System Administrator:** Holds full system privileges, including installing and configuring AES and its dependencies, defining environments and pipelines, provisioning admin access, upgrading AES, and setting intake guardrails. They also collaborate on resolving application conflicts and creating instance scan definitions.
* **Professional ServiceNow Developer:** These developers work in AES and ServiceNow Studio, often collaborating with citizen developers. They build and customize complex applications, ensure best practices, create ATF tests, and assist with application reviews and platform scans.
* **Granular Admin Roles:** Include AES admin, Collaboration Request admin, and Table Builder Wizard admin, each providing specific administrative privileges within AES for more controlled permission management. These roles cannot manage tables dependent on ServiceNow AI Platform tables and require additional granular roles for that purpose.

## Practical Implications for ServiceNow Customers

By properly assigning these roles, ServiceNow customers can:

* Enable low-code developers to contribute to app creation while maintaining governance and quality through admin oversight.
* Control access to app templates to streamline development and reuse standards.
* Secure AES environments through role-based access control and guardrails set by system and security admins.
* Leverage professional developers for complex app customization and quality assurance.
* Use granular admin roles to delegate specific administrative tasks without granting full system privileges.

This structured approach helps organizations manage app development lifecycle effectively while maintaining security and compliance.  
The responsibilities of your staff are controlled by roles assigned to each member.
Personas aren't explicitly part of App Engine Studio (AES) but administrators assign roles to give team members
permission to configure or use AES.

Low-code/citizen developer
:   Low-code/citizen developers are tech savvy and interested in creating apps. Though
    they might not have formal coding or app development training, citizen developers can
    submit ideas for new apps and, if approved, build them using AES.

App Engine Studio admin
:   App Engine Studio admins manage all processes related to app
    development in AES. They review new app ideas, manage
    app development and deployment, and manage collaborators, usually in the App Engine Management Center.

App template admin
:   The app template admin makes sure that the right people have access to appropriate
    predefined and custom templates for app development in App Engine Studio.

App template author
:   The app template author creates and edits custom app templates in App Engine Studio and can share them with other users or groups.

Security admin
:   The security admin creates and modifies roles and access control lists for apps. This
    role is set on the platform level, and it is required for making updates to roles in App Engine Studio.

System administrator
:   The system administrator has access to all system features, functions, and data,
    regardless of security constraints. Grant this privilege carefully. If you have
    sensitive information, such as HR records, that you must protect, create a custom admin
    role for that area and train a person who is authorized to see those records to act as
    the administrator.

Professional ServiceNow developer
:   Professional ServiceNow developers can work in App Engine Studio, usually as collaborators with citizen developers.
    Because of their coding knowledge and development background, though, they're more
    likely to build and customize apps on the ServiceNow AI Platform, using more complex
building tools.  
{#aes-personas-roles__table_pbn_ms3_rsb__entry__3}

| Persona | Roles required | Responsibilities |
|-|-|-|
| Low-code/citizen developer | App Engine Studio Users group (sn_app_eng_studio.user) | * Submit requests for new custom applications to build in App Engine Studio. * Understand ServiceNow and application development best practices. * Build and test applications in App Engine Studio. * Submit App Engine Studio applications for IT review. * Maintain and change the application during its life cycle if determined during the intake process. {#aes-personas-roles__ul_fmf_hw3_rsb} |
| Low-code/citizen developer | App Engine Studio User Limited group (sn_app_eng_studio.user) | * Collaborate with other users on applications they've been given permission to see. * Submit App Engine Studio applications for IT review. * Understand ServiceNow and application development best practices. {#aes-personas-roles__ul_bjs_qpn_vvb} Note: Users in the App Engine Studio User Limited group can't create new apps. |
| App Engine Studio admin group | * atf_test_designer * scan_admin * app_engine_admin * sn_app_eng_studio.admin * sn_collab_request.collab_request_admin * sn_table_bldr_wzd.table_bldr_wzd_admin {#aes-personas-roles__ul_w41_lv3_rsb} | * Manage App Engine Studio processes and properties. * Review and approve/reject submitted application requests based on intake guardrails defined by the system administrator. * Provision App Engine Studio user access. * Review submitted App Engine Studio applications. * Manage deployment requests. * Manage promotion of App Engine Studio applications across instances. * Execute ATF tests/suites in testing instances. * Ensure instance scans run with proper definitions. * Collaborate with the system administrator to resolve application conflicts that arise on the platform. {#aes-personas-roles__ul_p2l_lv3_rsb} |
| App template admin | app_template_admin | * Control access to custom and predefined templates. * Activate and deactivate templates. * Share templates globally or with users and groups. {#aes-personas-roles__ul_ggd_lzr_stb} |
| App template author | app_template_author | * Create and edit custom templates in App Engine Studio. * Share custom templates with users or groups. {#aes-personas-roles__ul_ehm_q5x_fwb} |
| Security admin | security_admin | * Create and modify roles and access control lists. * Required for making updates to roles in App Engine Studio. {#aes-personas-roles__ul_fpx_sbq_tvb} |
| System administrator | Admin | * Install and configure App Engine Studio and its dependent apps. * Define environments. * Configure pipelines. * Provision access to the App Engine Studio administrator group. * Upgrade the App Engine Studio application, when applicable. * Define guardrails for which AES administrators can approve or reject application intake requests. * Collaborate with professional ServiceNow developers to create instance scan definitions for the platform. * Collaborate with AES administrators to resolve application conflicts that arise on the platform. {#aes-personas-roles__ul_m1t_3v3_rsb} |
| Professional ServiceNow developer | * atf_test_admin * delegated_developer * scan_admin * sn_app_eng_studio.user * sn_collab_request.collab_request_admin {#aes-personas-roles__ul_fs5_mv3_rsb} | * Build and test applications in ServiceNow Studio and App Engine Studio * Collaborate with citizen developers on an as-needed basis to deliver applications in App Engine Studio, including the following tasks: * Ensuring application development and organizational best practices are followed by citizen developers. * Helping with review and testing of submitted App Engine Studio applications. * Building complex configurations involving UI Builder, Mobile App Builder, Workflow Studio, or other builder tools. {#aes-personas-roles__ul_pgm_nv3_rsb} * Create ATF tests/suites for applications. * Collaborate with a system administrator to create instance scan definitions for the platform. {#aes-personas-roles__ul_ogm_nv3_rsb} |
| AES admin | sn_app_eng_studio.admin | Granular admin role that provides access to App Engine Studio and enables administrative access to AES tables. Can be combined with other granular admin roles or delegated development for additional permissions. For more information about granular admin roles, see [Platform security granular admin roles](https://www.servicenow.com/docs/access?context=platsec-granular-roles&version=brazil&pubname=brazil-platform-security&ft:locale=en-US). |
| Collaboration request admin | sn_collab_request.collaboration_request_admin | Granular admin role that provides administrative access to collaboration tables. |
| AES Table Builder Wizard admin | sn_table_bldr_wzd.table_bldr_wzd_admin | Granular admin role that provides access to manage permissions during table creation in AES. |
[Table 1. Personas for AES]

{#aes-personas-roles__table_pbn_ms3_rsb}  
Important:  
Granular admin roles cannot manage tables that depend on ServiceNow AI Platform tables, such as the Experience Visibility Control table (sn_udc_experience_visibility_control) or Preferred Tables (sn_preferred_table). To manage such tables, additional granular admin roles are necessary. For more information, see [Platform security granular admin roles](https://www.servicenow.com/docs/access?context=platsec-granular-roles&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

