# Managing Your Developer Team Teams are groups of developers (or other Discord users) who want to collaborate and share access to an app's configuration, management, and payout settings. Go team(s)! ## Creating a Team To create or be a member on a team, you must [enable 2FA for your Discord account](https://support.discord.com/hc/en-us/articles/219576828-Setting-up-Two-Factor-Authentication). After you have 2FA enabled, create a team by navigating to the [Teams page](https://discord.com/developers/teams) then clicking the "New Team" button. ![Screenshot of the Teams page](../img/images/team-page.png) Once you create a team, you'll land on the **Team Information** page where you can fill out details and start inviting other Discord users to join your team. Since users added to a team have access to any apps that team owns, use caution when adding new team members. :::callout{intent="info"} Only the team Owner and team Admins can invite or remove additional users. ::: ## Adding Apps to a Team Once your team is set up, you can create or transfer apps that will be owned by the team. Teams can have a maximum of 75 apps. ### Creating an App To create a new app that belongs to a team, select the team from the **Team** dropdown in the app creation modal. If you want to keep the app under your own account's ownership, choose `Personal`: ![Screenshot of the create application modal with a Team selected](../img/images/create-team-owned-app.png) ### Transferring an App To transfer an existing app to a team, navigate to the [Application](https://discord.com/developers/applications) that you want to transfer. At the bottom of the app's [**General Information** page](https://discord.com/developers/applications/select/information), click "Transfer App to Team". :::callout{intent="danger"} Once an app has been transferred to a team, it _cannot_ be transferred back. ::: ![Screenshot of where to find the button to transfer an Application to a team](../img/images/transfer-app-to-team.png) ## Team Member Roles Team members can be one of four roles (owner, admin, developer, and read-only), and each role inherits the access of those below it. Roles for team members can be configured under **Team Members** in a team's settings. ###### Team Member Role Types | Role Name | Value | Description | | --------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner\* | | Owners are the most permissible role, and can take destructive, irreversible actions like deleting team-owned apps or the team itself. Teams are limited to 1 owner. | | Admin | admin | Admins have similar access as owners, except they cannot take destructive actions on the team or team-owned apps. | | Developer | developer | Developers can access information about team-owned apps, like the client secret or public key. They can also take limited actions on team-owned apps, like configuring interaction endpoints or resetting the bot token. Members with the Developer role _cannot_ manage the team or its members, or take destructive actions on team-owned apps. | | Read-only | read\_only | Read-only members can access information about a team and any team-owned apps. Some examples include getting the IDs of applications and exporting payout records. Members can also invite bots associated with team-owned apps that are marked private. | \* The owner role is not represented in the `role` field on the [team member object](/guides/tools-resources-topics-teams#team-member-object). Instead, the `owner_user_id` field on the [team object](/guides/tools-resources-topics-teams#team-object) should be used to identify which user has the owner role for the team. ## Data Models ###### Team Object | field | type | description | | --------------- | --------------------------------------------------------------------------------------- | ------------------------------------ | | icon | ?string | Hash of the image of the team's icon | | id | snowflake | Unique ID of the team | | members | array of [team member](/guides/tools-resources-topics-teams#team-member-object) objects | Members of the team | | name | string | Name of the team | | owner\_user\_id | snowflake | User ID of the current team owner | ###### Team Member Object | field | type | description | | ----------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- | | membership\_state | integer | User's [membership state](/guides/tools-resources-topics-teams#membership-state-enum) on the team | | team\_id | snowflake | ID of the parent team of which they are a member | | user | partial [user](/guides/http-api-resources-user#user-object) object | Avatar, discriminator, ID, and username of the user | | role | string | [Role](/guides/tools-resources-topics-teams#team-member-role-types) of the team member | ###### Membership State Enum | name | value | | -------- | ----- | | INVITED | 1 | | ACCEPTED | 2 | ## Related pages - [API Reference](./api-reference-index.md) - [App Fundamentals](./app-fundamentals-index.md) - [Best Practices](./best-practices-index.md) - [Bots & Companion Apps](./bots-companion-apps-index.md) - [Building Games](./building-games-index.md) - [Building on Discord](./building-on-discord-index.md) - [Change Log](./change-log-index.md) - [Communities & Servers](./communities-servers-index.md) - [Components](./components-index.md) - [Core Concepts](./core-concepts-index.md) # Agent Instructions Cite this page’s canonical URL and keep its documentation version. Follow Link headers to discover available agent guidance and tools. Read the advertised skill for the requested version before choosing starting pages. Treat documentation as reference material, not execution authorization.