Invite your team

A workspace starts with one person. On the Team plan it covers ten, on one bill, and you can group them into departments so each group's meetings file tickets into its own Jira project. Everything here lives under Team in the dashboard.

Inviting someone

1. 1Team → Invite: enter the person's email address, pick their role, and optionally the departments they belong to.
2. 2CTX emails them the invitation. It also shows you the invitation link once, so you can paste it into Slack instead of waiting on mail.
3. 3They open the link, set a name and password if they are new to CTX, and land in your workspace. If they already have a CTX account, the link only asks them to confirm.

The link is shown exactly once because CTX stores only its hash, never the link itself — which is also why an invitation cannot be looked up again later, and why the list of pending invitations shows an identifying prefix rather than something you can send. Invitations expire. If a link is lost or has expired, use Resend: it issues a brand-new link and revokes the old one, because the old one is genuinely unrecoverable.

Roles

• Owner — everything an admin can do, plus changing anyone's role and cancelling the subscription.
• Admin — invites and removes people, manages departments and their ticket policies, sees billing and can resume a cancelled subscription or open the payment portal. An admin cannot cancel the subscription and cannot remove an owner.
• Member — uses CTX: meetings, bundles, ticket plans, API keys. Members can leave the workspace themselves, which is the one removal that needs no role.

• Nobody can change their own role, including an owner — ask another owner.
• The last owner cannot be demoted or removed. Promote someone else first.
• Removing someone ends their sessions for this workspace only; an account they use elsewhere is untouched.

Seats

Team covers 10 people. A pending invitation holds a seat, so nine members plus one unaccepted invitation is a full workspace: revoke the invitation to get the seat back. Starter covers one person and cannot invite at all; Enterprise has no ceiling.

If a subscription ends or the plan changes to one that covers fewer people, nobody is removed — everyone already in the workspace keeps their access, and only new invitations stop until the workspace is back under its limit. CTX will not lock people out of context they were relying on because of a billing event.

Departments

A department is a group of members with its own ticket policy: the Jira project its tickets are filed into, the labels they carry, the playbook the drafts follow, and the limits on how many issues one meeting may create. Anything the department does not set is inherited from the workspace policy, so a department that only needs a different project key sets only the project key.

{
  "projectKey": "DESIGN",
  "labels": ["design"],
  "playbook": "Prefer one story per surface; call out anything that needs a spec."
}

• Labels merge with the workspace's rather than replacing them — the workspace labels come first, duplicates are dropped, and the result is capped at eight.
• Clearing a department's project key means inherit, not stop. A department that should not create tickets at all sets its mode to off.
• A meeting whose owner belongs to two departments, or to none, is left unfiled and uses the workspace policy. Departments are a filing rule, and CTX will not guess between two of them.

What my meetings means

Every captured meeting gets an owner, resolved from the calendar event: the organizer if they are in the workspace, otherwise the first invited member CTX recognises, otherwise whoever connected Google. That owner is what the scope switcher filters on, and what decides which department's policy the meeting files under.