Dashboard Access
Dashboard Access lets a community owner delegate day-to-day Submitt administration to trusted Discord roles without giving those members Discord Administrator or Manage Server permission.
Submitt checks the member's current roles directly from Discord. If the owner grants a role dashboard access, members with that role can enter the licensed community dashboard. Removing that role in Discord removes the delegated dashboard access automatically.
Who can configure access
The Discord server owner is the authority for community dashboard access and can manage the Dashboard Access policy. The Submitt subscription owner is separately authoritative for billing, server-slot licensing and White Label ownership controls. Paying for a server does not automatically make that account a community administrator when someone else owns the Discord server. Ordinary Discord Administrator permission also does not automatically grant Submitt dashboard access.
Grant a role dashboard access
- Open the licensed community in Submitt.
- Open Dashboard Access.
- Enable the Discord role you trust.
- Select the dashboard sections that role may use.
- Save the access policy.
Overview is optional. A delegated role can be Tickets-only, Moderation-only, Applications-only or any other selected combination. When a member does not have Overview, Submitt lands them in the first dashboard section their role is actually allowed to use. Operations & Health, Data Export and Data Purge are separate permissions so read-only operational access does not imply destructive data access.
Multiple roles
If a member has more than one allowed Discord role, Submitt combines the dashboard permissions from those roles. For example, a Support role can grant Tickets while a Moderator role grants Moderation & Safety; a member with both roles receives both sections.
Always owner-only
Payment methods, invoices, plan changes, cancellation and subscription management remain restricted to the Submitt subscription owner.
Assigning or releasing paid server slots remains restricted to the subscription owner.
Custom bot credentials, activation/deactivation and other White Label ownership controls are not delegated through community roles.
Only the Discord server owner can change which roles may administer the community dashboard. Delegated staff cannot grant themselves or other roles additional permissions.
Server-side enforcement
Hiding a sidebar item is not the security boundary. Submitt checks the required dashboard permission again on the server before loading protected community data or accepting a protected dashboard action. Typing a hidden URL manually does not bypass the access policy.
Owner-only by default
New communities do not automatically expose their community dashboard to staff. Until the Discord owner enables a role in Dashboard Access, only the Discord owner has community-administration access. The subscription owner continues to have their own billing/licensing controls without being silently promoted to community administrator.
Role-based access depends on Submitt being able to verify the member and roles in Discord. If the bot is removed or Discord role data is unavailable, delegated access may be temporarily unavailable while owner recovery access remains protected.