Authority & Permissions

Manage user access, roles, and project-level permissions within Ticket Mate.

Overview

Ticket Mate uses a Role-Based Access Control (RBAC) system to ensure users only have access to the data and actions they need. Permissions are managed at both the account level and the project level.

User Roles

1. Owner

  • Full control over the account, including billing and seat management.
  • Can delete the account or change the subscription plan.
  • Has all permissions of an Admin.

2. Admin

  • Can manage all projects, integrations, and automation rules.
  • Can invite/remove users and change user roles.
  • Access to all system logs and reliability tools.

3. Editor

  • Can create and modify tickets, project hubs, and common settings.
  • Can view all reports and insights.
  • Cannot manage integrations or billing.

4. Viewer

  • Read-only access to tickets, boards, and reports.
  • Cannot make changes to any data.

Project-Level Permissions

Permissions can be further refined per project:

  • Lead: Can manage specific project settings and membership.
  • Member: Standard access based on their global role.
  • Restricted: Can only see specific ticket types or components.

Managing Access

  1. Navigate to Admin → Team Management.
  2. Invite new users via email.
  3. Use the Role dropdown to update permissions for existing members.
  4. Use the Projects tab to assign users to specific teams.

Best Practices

  • Principle of Least Privilege: Assign users the minimum role they need (e.g., make developers "Editors" rather than "Admins").
  • Audit Regularly: Periodically review the member list in Admin → Team Management to remove inactive users.

Related Documentation


Last Updated: February 11, 2026 10:55 PM EST