Governance
Why Your Discord Bot Shouldn't Depend on a Single Owner's Account
A bot tied to one person's account risks losing all access if that person leaves or is locked out.
Is this your situation?
You run a bot under one owner's account and want it to keep working if that person steps away. You want a structure where the bot continues under developer team control.
Where teams go wrong
- No developer team You keep the bot under one personal account.Why it happens: A developer team is the foundation for building and managing apps on Discord.
- No invited collaborators You are the only one who can manage the bot.Why it happens: Developer teams let users invite collaborators to their project.
- Shared owner credentials You want faster access without a formal team structure.Why it happens: Team owner credentials should be kept secure as a security best practice.
- Mismatched permission levels You assign roles without checking what each member needs.Why it happens: Appropriate permission levels should be used for each team member.
What good practice looks like
| Approach | Single owner account | Developer team |
|---|---|---|
| Ownership | Not stated by Discord | Developer teams let users share ownership of their Discord applications. |
| Continuity | Not stated by Discord | Developer teams help maintain continuity if members of the working team change over time. |
| Collaboration | Not stated by Discord | Developer teams let users invite collaborators to their project. |
| Management scope | Not stated by Discord | Having a developer team gives centralized management for multiple applications. |
How Discord handles this
- A developer team is the foundation for building and managing apps on Discord.
- There can only be 1 owner per developer team.
- The Owner team role has full control over the team and all applications.
- The Admin team role can manage team settings and applications.
- Ownership of a developer team can be transferred.
Before you start
- Developer team existence Confirm the app is managed through a developer team rather than a personal account.Verify: Developer teams are required for app verification.
- Team roster Check who holds a role on the team.Verify: Inviting a team member requires entering the Discord username or user ID of the person to invite.
- Role assignment Review which permission role each member holds.Verify: Inviting a team member requires setting their permission role.
- Owner count Confirm only one person holds the owner role.Verify: There can only be 1 owner per developer team.
- Read-only members Check whether any member only needs to view applications.Verify: The Read-only team role can view applications but cannot make changes.
Which scenario is yours?
- Is the bot currently owned by one personal account? A user must navigate to the Teams section of the Discord Developer Portal to create a developer team.
- Does a developer team already exist for this app? Additional settings can be configured under Team Details.
- Do multiple people need to manage the bot day to day? Inviting a team member requires entering the Discord username or user ID of the person to invite.
- Does ownership of the team need to move to someone else? Ownership of a developer team can be transferred.
- Does the team currently have only one person holding any role? There can only be 1 owner per developer team.
Keeping this working over time
- Appropriate permission levels should be used for each team member.
- Team owner credentials should be kept secure as a security best practice.
- See how ownership of a developer product moves between people when a transfer becomes necessary.
- A support request can be submitted through the Developer Support Portal for assistance with developer team issues.
If control is already lost — Reclaim a Discord Server Owned by a Former Team Member
Keeping track of who has access
A bot tied to a single account concentrates access in a way that is hard to reverse later. Spreading management across people through defined roles keeps the bot running when one person steps back. Delvia helps you see who holds access to what, across people and time. That view makes it easier to confirm the structure still matches who should hold it.
Was this helpful?