{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1592,"path":"application-development/app-engine-studio/installed-with-aes.md","title":"Components installed with AES","bundle":null,"doc_type":null,"release":"australia","body":"\n# Components installed with AES\n\nSeveral types of components are installed with activation of the App Engine Studio \\(AES\\) plugin, including tables and user roles.\n\n**Note:** The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/find-components.md).\n\n## Roles installed\n\n\n
\n\nRole title \\[name\\]\n\n\n\nDescription\n\n\n\nContains roles\n\n
\n\nApp Engine admin\n\n \\[app\\_engine\\_admin\\]\n\n\n\nAdministers AES, including users, app configuration, and other management tasks.\n\n This role is assigned automatically to users in the App Engine Studio Admins group.\n\n\n\n- sn\\_request\\_read\n- sn\\_request\\_write\n- sn\\_app\\_eng\\_studio.user\n\n
\n\nApp Engine Studio app template admin\n\n \\[app\\_template\\_admin\\]\n\n\n\nAdministers the use, sharing, and activation or deactivation of templates.\n\n This role is assigned by an admin to individual users. For more information, see [Manage template access](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/manage-template-access.md).\n\n\n\n- app-template-author\n- app-template-runner\n- flow-designer\n- flow-operator\n\n
\n\nApp Engine Studio admin\n\n \\[sn\\_app\\_eng\\_studio.admin\\]\n\n\n\nGranular admin role that grants access to App Engine Studio and enables administrative access to App Engine Studio tables. You can combine this role with other granular admin roles or delegated development for additional permissions. For more information about granular admin roles, see [Granular admin roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md).\n\n\n\nsn\\_app\\_eng\\_studio.user\n\n
\n\nApp Engine Studio user\n\n \\[sn\\_app\\_eng\\_studio.user\\]\n\n\n\nBuilds applications in App Engine Studio.\n\n This role is assigned automatically to users in the App Engine Studio Users group. For more information, see [Grant user access to AES](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/grant-aes-access.md).\n\n\n\n- catalog\\_builder\\_editor\n- app\\_template\\_runner\n- sn\\_g\\_app\\_creator.app\\_creator\n\n
**Note:** Additional granular admin roles are installed with App Engine Studio dependent applications, including:\n\n- Collaboration request admin \\[sn\\_collab\\_request.collaboration\\_request\\_admin\\]\n- AES Table Builder Wizard admin \\[sn\\_table\\_bldr\\_wzd.table\\_bldr\\_wzd\\_admin\\]\n\nYou can combine these granular admin roles with other roles to provide the level of access needed for a user's function. For more information about roles in App Engine Studio, see [Configure AES personas and roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/aes-personas-roles.md). For more information about granular admin roles, see [Granular admin roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/granular-admin-roles.md).\n\n## Tables installed\n\n\n
\n\nTable\n\n\n\nDescription\n\n
\n\nApp Details\n\n \\[sn\\_app\\_eng\\_studio\\_app\\_details\\]\n\n\n\nDetails about the operations that a developer used to create an application in App Engine Studio. The table is updated automatically as developers build applications in App Engine Studio.\n\n
\n\nApplications in Projects\n\n \\[sn\\_app\\_eng\\_studio\\_project\\_application\\_m2m\\]\n\n\n\nApplications that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio.\n\n
\n\nEnvironment\n\n \\[sn\\_pipeline\\_environment\\]\n\n\n\nInstances that you use for the developing, testing, or launching an application. You update this table as you define environments for App Engine Studio.\n\n
\n\nDeployment Request\n\n \\[sn\\_deploy\\_pipeline\\_deployment\\_request\\]\n\n\n\nRequests to review and publish an application that a developer created in App Engine Studio. From the deployment request form, a reviewer can deploy the application to different environments, accept or reject an application, and send feedback to a developer. For more information, see [Deployment Request form in the Pipelines and Deployments app](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-management-center/deployment-req-form-d-and-p.md).\n\n
\n\nPipeline\n\n \\[sn\\_pipeline\\_pipeline\\]\n\n\n\nConfigurations for deploying applications to different environments. Only one pipeline can be active at a time. You update this table as you create a pipeline for the deployment of applications from App Engine Studio. For more information, see [Managing deployments using Pipelines and Deployments](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-management-center/manage-deployments-using-p-and-d-aemc.md).\n\n
\n\nProject\n\n \\[sn\\_app\\_eng\\_studio\\_project\\]\n\n\n\nDetails about App Engine Studio development sessions. A project is created automatically when a developer creates an application in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio.\n\n
\n\nResources Content\n\n \\[sn\\_app\\_eng\\_studio\\_resources\\_content\\]\n\n\n\nHelp resources that a developer can access in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio.\n\n
\n\nResources Content Topic\n\n \\[sn\\_app\\_eng\\_studio\\_resources\\_content\\_topic\\]\n\n\n\nCategorizations of help resources in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio.\n\n
\n\nTaxonomy\n\n \\[sn\\_app\\_eng\\_studio\\_taxonomy\\]\n\n\n\nApplication files that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio.\n\n
\n\nTaxonomy Category\n\n \\[sn\\_app\\_eng\\_studio\\_taxonomy\\_category\\]\n\n\n\nCategorizations for application files in App Engine Studio. By default, application files are categorized as data, experience, logic and automation, or security. This table includes configurations to support the default user experience for App Engine Studio.\n\n
\n\nTaxonomy Details\n\n \\[sn\\_app\\_eng\\_studio\\_taxonomy\\_details\\]\n\n\n\nDetails about application files that a developer creates in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio.\n\n
**Note:** Data preservers are added for the following tables related to pipelines:\n\n- Environment\n- Pipeline\n- Pipeline Environment Order\n- Pipeline Types\n\nThe data preservers prevent records in these tables from being overwritten during cloning on a non-production instance. For more information, see [Create a clone preserver](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/create-new-clone-preserver.md).\n\n**Parent Topic:**[Installing App Engine Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-engine-studio/install-aes.md)\n\n"}}