{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":2531,"path":"application-development/servicenow-studio-classic/servicenow-studio-collab-permissions.md","title":"Collaboration permissions for ServiceNow Studio","bundle":null,"doc_type":null,"release":"australia","body":"\n# Collaboration permissions for ServiceNow Studio\n\nCollaboration permissions determine what delegated developers can do when working on an app in ServiceNow Studio. Admins or app owners set these permissions.\n\nFor more information, see [Collaborating on apps using ServiceNow Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-studio-classic/manage-app-collab-servicenow-studio.md).\n\n## File types custom collaboration permissions\n\n|Permission|Description|Owner default setting|Editor default setting|\n|----------|-----------|---------------------|----------------------|\n|All File Types|Access to all file types, including additional file types not granted by the other options.|Yes|Yes|\n|Integrations|Access to web service APIs, REST APIs, data sources, and Integration Hub - Import.|Yes|Yes|\n|Reporting|Access to reports and scheduled reports.|Yes|Yes|\n|Mobile builders|Access to build mobile experiences, such as with Mobile App Builder.|Yes|Yes|\n|UI Builder|Access to UI Builder to build complex interfaces.|Yes|Yes|\n|Workflow|Access to Workflow Editor and Activity Creator.|Yes|Yes|\n|Service Portal|Access to Service Portal editors and tools.|Yes|Yes|\n|Workflow Studio|Access to the Workflow Studio design environment to create flows and actions.|Yes|Yes|\n|Service Catalog|Access to catalog-related file types such as catalog items, record producers, and variables to add catalog items to apps.|Yes|Yes|\n|Tables & forms|Access to model and layout-related file types such as table columns, form layout, and list layout.|Yes|Yes|\n|Decision Tables|Access to decision tables to create decision logic based on multiple if-else rules.|Yes|Yes|\n|Playbooks|Access to the Playbooks design environment to create processes. Editing activity subflows or actions requires the **Flow Designer** permission.|Yes|Yes|\n|Notifications|Access to create automatic email notifications and work with email templates.|Yes|Yes|\n\n## Security/Entitlement custom collaboration permissions\n\n**Manage access control** grants access to security management files, such as Access Control Lists and roles.\n\nThe default setting for both owners and editors is selected.\n\n## Programming tools custom collaboration permissions\n\n**Allow scripting** grants access to script fields, such as those in Business Rule, UI Action, and Client Script.\n\nThe default setting for both owners and editors is de-selected.\n\n## Application management custom collaboration permissions\n\n|Permission|Description|Owner default setting|Editor default setting|\n|----------|-----------|---------------------|----------------------|\n|Delete application|Access to delete the app.|Yes|No|\n|Manage collaborators|Access to change the developers and their permissions to collaborate on an app.|Yes|No|\n|Source control|Access to source control tool integrations.|No|No|\n|Invite collaborators|Access to invite developers to collaborate on an app.|Yes|Yes|\n\n## Deployment custom collaboration permissions\n\n|Permission|Description|Owner default setting|Editor default setting|\n|----------|-----------|---------------------|----------------------|\n|Upgrade app|Access to upgrade applications.|No|No|\n|Submit for deployment|Access to request deployment for an app.|Yes|No|\n|Publish app to repo|Access to publish the app to your repo.|No|No|\n|Publish to app store|Access to publish the app to your app store.|No|No|\n\n**Parent Topic:**[ServiceNow Studio reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-studio-classic/servicenow-studio-reference.md)\n\n"}}