Skip to content
Ticketon Logo Ticketon
A new Dashboard has been released - some parts of the docs may be outdated. Please report any issues.

Access Control

The dashboard and certain commands can be restricted to specific users or roles. The access control is managed in the dashboard.

The server owner can toggle a switch to disable the default access check, which allows all users with Manage Server or Administrator permissions to access the dashboard and use all commands. This is the default setting for all servers.

When this setting is enabled, only users with explicit permissions (and the owner) will be able to access the dashboard and use commands. Continue reading to learn about explicit permissions.

Explicit permissions can be set for both users and roles. If a user has explicit permissions, they will be able to access the dashboard and use the respective commands.

You can set up to 100 users and roles (combined) with special permissions. Each role or user can be granted a different set of permissions based on what access they need.

PermissionDescription
Admin *Grants all permissions. Can only be granted by the owner.
Global SettingsAccess to server-wide settings and configuration.
View TicketsAbility to view and browse all support tickets.
CategoriesManage ticket categories.
FormsManage support forms.
MessagesManage custom messages.
AutomationManage automation actions.
Custom BrandingCustomize the bot’s appearance in your server.
ScheduleManage your support schedules.
BlacklistManage the blacklist.
Audit LogView the audit log of dashboard actions and changes.
AnalyticsAccess analytics and statistics.

* Only the server owner and users with this permission can manage other permissions. Only the server owner can grant this permission to others.

The permission system uses a combination of roles and user permissions:

  • A user can receive permissions through roles they’re assigned to (coming from Discord)
  • A user can also receive individual permissions assigned directly to them
  • If a user has a permission through either a role or a direct assignment, they can access that feature

This means if a user is in a role that grants them access to a feature, they have access to it - even if another role or permission doesn’t. The system checks all available permissions and grants access if any of them match.

The same permission system that protects dashboard sections also protects certain bot commands. If a user doesn’t have the required permission for a command, they’ll receive an error message explaining what permission they need. This ensures consistent access control across the entire dashboard and bot.

Note, that some commands require default permissions in Discord, which are separate from the explicit permissions in the dashboard.

Learn about Discord’s native command permissions