An organization's members are managed under Configure → Members. Every member has two independent settings: a role, which says what they're allowed to administer, and a seat kind, which says whether they can change anything at all.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including owner-only settings and billing. |
| Admin | Manage members, projects, and compute. Cannot change owner-only settings. |
| Member | Work in the organization — create projects, write training requests, review, queue runs. |
The owner is the person who created the organization. Some settings are deliberately owner-only rather than admin-accessible — notably the permissions configuration that decides which admins may set training-request controls, described in Training requests. The point is that admins can't quietly widen their own authority.
Member is the right role for most people. Give someone Admin when they need to add other people or manage compute, not as a general seniority marker.
Seats
Seat kind is separate from role, and it's the one people find surprising:
| Seat | Means |
|---|---|
| Writer | Can create and change things — projects, training requests, reviews, runs. |
| Reader | Read-only. Can see the organization's work but not modify it. |
A reader seat is read-only regardless of role. Reader controls are disabled throughout the dashboard rather than hidden, so it's clear you're looking at something you can't change rather than something that isn't there.
Reader seats exist for people who need visibility without participation — a manager tracking progress, someone in a neighbouring team, an auditor.
Writer and reader seats are counted and billed differently. For what each plan includes, see treqs.ai/pricing — plans and prices live there rather than here so they stay current.
Inviting someone
From Configure → Members, choose Invite, and supply:
- Their email address.
- A role — Admin or Member. You can't invite someone directly as owner.
- A seat kind — Writer or Reader.
Because adding a writer seat can change what the organization is billed, the dashboard shows the billing impact before the invitation is sent, and asks you to confirm it when the change is significant. Nothing is charged silently.
The invitation lifecycle
An invitation is in one of four states:
| State | Meaning |
|---|---|
| Pending | Sent, not yet accepted. |
| Accepted | They joined. They're now a member. |
| Expired | It sat too long. Send a new one. |
| Revoked | An admin withdrew it before it was accepted. |
The recipient sees it under Invitations, showing the organization, role, seat kind, and expiry, and joins explicitly — nothing is auto-accepted by opening a link.
You can revoke a pending invitation at any time. Once it's been accepted, revoking is no longer the tool — remove the member instead.