{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1999,"path":"application-development/creator-studio/creator-studio-collaboration-roles.md","title":"Collaborating with others to build apps in Creator Studio","bundle":null,"doc_type":null,"release":"australia","body":"\n# Collaborating with others to build apps in Creator Studio\n\nSometimes you need help with building out your app, and that’s OK! And sometimes other people need your help building their apps, which is great! This point is where collaboration comes into play.\n\nYou can collaborate on apps you don't own by requesting permission to edit them, and invite other people you work with to collaborate on your apps with you.\n\nCollaboration, also referred to as [delegated development](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-glossary.md), builds on the existing delegated development feature set in the ServiceNow AI Platform. It enables developers to invite other developers into apps so they can co-create and develop the app together. Depending on your permissions, you can invite others to collaborate on an app with you, or request to join someone else's app.\n\n**Note:** You must have an App Engine Enterprise license to take full advantage of collaboration.\n\nThe ServiceNow AI Platform Collaboration app is automatically installed with Creator Studio. For more information about the Collaboration app, see [Application collaboration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/application-collaboration.md).\n\n## Collaboration descriptors: Owners and Editors\n\nSo, you realize you either need help with your app, or you want to help someone else build their app. What’s next? You need the appropriate collaboration role.\n\nThere are two standard types of collaborators when you co-develop an app with other people: Owners and Editors. These two roles are called [collaboration descriptors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-glossary.md). The collaboration descriptor that someone is assigned determines if they can assign, manage, and monitor delegated development permissions. For example, people who are Owners can do more than people with the Editor collaboration type.\n\nIf needed, your admin can define custom collaboration descriptors to select when managing collaborators, either in the Creator Studio Guided Setup or in the Collaboration app. For more information on custom descriptors, see [Configure Creator Studio using Guided Setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/config-creator-studio-guided-setup.md) and [Create collaboration descriptors to assign permissions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/create-collaboration-descriptors.md).\n\n\n
\n\nDescriptor\n\n\n\nDescription\n\n
\n\nOwner\n\n\n\nOwner of the application.- If you created the app, you're automatically the owner.\n- Owners can manage other collaborators for the app.\n- Owners have the delete app permission, which enables them to edit app settings, such as name, description, and icon.\n- Owners automatically get the delegated\\_developer role for the app.\n\n
\n\nEditor\n\n\n\n- Editors can invite collaborators.\n- Editors have limited ability to edit the app.\n\n
## Collaboration development permissions\n\nYou’ve designated Owners and Editors in your app, now what? You must invite other collaborators to work in your app.\n\nCollaboration permissions enable you to control who's building apps in Creator Studio. You assign permissions to developers \\(or users who deploy applications\\) so that they can develop and deploy applications.\n\nIf you invite someone to collaborate on an app and they don't have the Delegated developer \\(delegated\\_developer\\) role, an App Engine admin must approve the collaboration request. For more information, see [Delegated development and deployment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/delegated-development-and-deployment/c_DelegatedDevelopment.md).\n\nWhen you add a user or group, a collaboration task is generated behind the scenes, and an approval flow kicks off. If you have App Engine Management Center \\(AEMC\\) installed, your admin can review and approve/deny these collaboration request tasks there. If you don’t have AEMC installed, admins can navigate to **All** > **App Engine** > **Collaboration** > **Collaboration Tasks**.\n\nThe collaboration task that goes to your admin provides information on which application a developer is being added to, and what permissions are granted. Approvers sometimes need to review these task records before they add developers to the application.\n\n## What can owners and editors do?\n\nIf you’re in the Creator Studio users group, you can see all users and groups collaborating on an app, as well as their collaboration descriptors.\n\nIf you can’t see the users and groups, you may have a different permission with more restrictions. But fear not! You can always contact your admin if you have any questions about who's working on an app.\n\nThe following table provides a list of general defaults for what owners and editors can do in Creator Studio.\n\n**Note:** For the full list of default Owner and Editor collaborator collaboration type permissions, see [Customized app collaboration permissions in Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-collab-custom-permissions.md).\n\n|Creator Studio feature|Owner|Editor|\n|----------------------|-----|------|\n|Invite collaborators|Yes|Yes|\n|Manage collaborators|Yes|No|\n|Edit app settings, such as name, description, and icon|Yes|No|\n|Create, edit, and delete forms|Yes|Yes|\n|Create, edit, and delete automation|Yes|Yes|\n|Manage the fulfiller workspace list configurations and records|Yes|Yes|\n|Submit app for deployment|Yes|No|\n|Delete app|Yes|No|\n\n## Collaboration roles and instances on different versions\n\nAs admins implement Creator Studio, they may have it installed on a non-production instance while their production instance is on a previous version of the ServiceNow AI Platform that doesn't have Creator Studio. This mis-match of instance versions affects the Collaboration Approval Workflow, which specifies the non-production instance as the source and the production instance as the controller. If the controller doesn't have the version of the collaboration plugin that supports Creator Studio, collaboration is unsupported.\n\nTo ensure that users can use the Collaboration Approval Workflow regardless of instance versions, admins must assign the catalog \\_builder\\_editor role to Creator Studio user groups.\n\n- **[Ask to work on an app in Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-request-join-app.md)** \nWant to work on an app but don't have access to it? No problem. We'll show you how to ask for access.\n- **[Manage collaborators for an app in Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-manage-collaborators.md)** \nAdd or remove people who can work on an app, or change their permissions for the app using the **Manage collaborators** option.\n\n**Parent Topic:**[Building apps with Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/building-apps-with-creator-studio.md)\n\n"}}