Team & Roles
Use the organization Team page to see who has access, create invite links, change roles, set server access, remove members, and revoke invites.
Members are listed in a table you can search, 10 to a page. A member's join date is in their row menu.
Roles
Every person in an organization has exactly one role.
| Role | Can do |
|---|---|
| Owner | Full control over billing, team, servers, settings, and deletion |
| Admin | Manage servers, regular members, and Member invites, and read tickets on every member server |
| Member | View the organization dashboard, and read tickets on the servers where they hold a ticket role |
There is one Owner per organization. The Owner cannot leave or be removed while they hold that role; ownership must be transferred first.
Organization roles control the organization's own pages. Whether someone can open a member server's dashboard is set separately, with server access.
Ticket access through server roles
The organization's Tickets and Transcripts pages are for everyone who handles tickets on your servers, not just people with a seat. Anyone with a ticket role on at least one member server can open them, and they don't count toward your member limit.
Each person sees only the servers and categories they could see on that server's own Tickets page:
| Where their access comes from | What they see on that server |
|---|---|
| Owner or Admin of the organization | Every category |
| Manage Server in Discord, or an Admin or Manager dashboard role | Every category |
| Support Staff dashboard role | Categories whose support roles they also hold |
| Organization Member with no dashboard role on that server | Categories whose support roles they hold |
| None of the above | Nothing. The server is hidden, including from filters |
So someone with a support role on three of your five servers sees tickets from those three servers only.
People who reach the viewer this way get the Tickets and Transcripts pages and nothing else in the organization. They find it under the server switcher, or on their dashboard home as an organization marked Ticket viewer.
Owners and Admins can see who has this access under Ticket access through roles on the Team page. It lists each person, the servers they can see, the categories on each, and the roles that grant it. Change someone's access by changing their roles in Discord or on the server's Permissions page.
Single sign-on organizations
If your organization requires single sign-on, only people with a member seat can open the ticket viewer.
Server access
Each Admin and Member has a Server access setting on the Team page. It decides what they can do on the dashboards of the servers in the organization.
| Server access | What they get on every member server |
|---|---|
| Org only | Nothing extra. They use the organization pages only. This is the default. |
| Support Staff | View and work tickets and transcripts, view feedback and the knowledge base |
| Manager | Support Staff access, plus categories, panels, flows, commands, automations and the knowledge base |
| Admin | Full dashboard access, including settings and permissions |
These are the same dashboard roles you can give Discord roles under a server's Permissions page. Server access applies to every server in the organization, including servers added later, and it works even if the person is not in that Discord server or holds no role there. Those servers appear in their server list.
If someone also has access through Discord, such as Manage Server or a role set up under Permissions, they get whichever gives more access. Server access only covers the dashboard. It does not give anyone roles or permissions inside Discord. It also counts as that dashboard role on the organization's Tickets and Transcripts pages.
The Owner can set server access for anyone. Admins can set it for Members, but not for themselves or other Admins. The Owner's own dashboard access still comes from Discord.
Security settings still apply
If the organization requires single sign-on, server access works only after the person signs in through it. A suspended server stays closed. If a server requires two-factor authentication for admins, someone with Admin server access has to use it too.
Admin limits
Admins can handle common team maintenance, but the Owner controls Admin access.
Admins can:
- Remove regular Members.
- Create Member invites.
- Delete Admin invites they created themselves.
Only the Owner can:
- Promote a Member to Admin.
- Demote or remove another Admin.
- Create Admin invites.
- Manage billing.
- Transfer ownership.
Member limits
Team organizations can have up to 10 members, including the Owner; Enterprise has no limit. People who only reach the ticket viewer through a server role don't count. The Team page shows the live member count under its title.
When the organization is full, Create Invite is disabled and existing invite links cannot be accepted by new people until capacity is available. If an organization is over the limit, for example after moving to a smaller plan, its existing members keep their access but no one new can join.
Invite teammates
Invite links carry a role, optional usage limit, and optional expiry. Owners and Admins can create invites; only Owners can create Admin invites.
Open Create Invite
On the Team page, select Create Invite.
Set the options
Choose the role, the usage limit and the expiry from the table below.
Share the link
Copy the generated link and send it to the people you want to add.
| Option | Choices | Notes |
|---|---|---|
| Role | Member or Admin | Admin invites can only be created by the Owner. |
| Max uses | Blank, or a number up to 100 | The link stops working when the cap is reached. On a plan with a member limit, a link never allows more uses than the seats left when it was made. |
| Expires | 1 day, 7 days (the default), 30 days or Never | Expired links stay listed until deleted. |
Invite links look like this:
https://dash.ticket-tool.app/invite/<code>
Anyone with a valid link can use it, so share invite links only with people you want in the organization.
Join outcomes
When someone accepts an invite, they sign in with Discord and join with the invite's role. If the invite is expired, out of uses, the person is already a member, or the organization is at its member limit, they cannot join and see the relevant message.
Each successful join counts as one use against the invite's max uses.
Manage invites
Invites are listed under Invite Links with their code, role, usage count, and expiry. The three most useful show first, usable links ahead of expired or used-up ones, and Show more opens the rest. Expired or fully used links are dimmed.
- Copy shares a link again.
- Delete revokes the link for future use.
Deleting an invite does not remove people who already joined with it.
Change roles
Use the actions menu next to a member:
- Promote to Admin raises a Member to Admin. Only the Owner can do this.
- Demote to Member lowers an Admin to Member. Only the Owner can do this.
- Transfer ownership makes that member the Owner, after a confirmation. The new Owner takes over billing and deletion, you stay on as an Admin, and only the new Owner can transfer it back.
The Owner's own role cannot be changed from this menu.
Remove or leave
Use Remove from a member's actions menu and confirm. The person immediately loses access to the organization and any server access it gave them, but their Discord account and the servers are not affected. They can be invited again later.
Admins can remove regular Members. The Owner can remove anyone except themselves.
A Member or Admin can leave the organization themselves. The Owner cannot leave until they transfer ownership to another member.
Access changes are immediate
Removing a member or deleting an invite takes effect right away.