This is the vocabulary SAQ uses in the app, in email, and in the API. The documentation uses these words exactly as the interface shows them. Each term links to its concept page.
Terms
| Term | Definition |
|---|---|
| Organization | The billing customer: plan, subscription, seats. Owns the workspace. |
| Workspace | The tenant everything lives in, with a fixed address (slug), ticket prefix, time zone, and period length. |
| Workspace user | A member of the workspace: Owner, Admin, or Member. Logs time, sees internal comments, uses the Inbox. |
| Owner, Admin, Member | The three workspace roles. Owners and Admins administer; Members work on their projects. |
| Project manager | A project role that lets a member manage that project's members and settings. |
| Agent account | A token-only workspace user for an AI assistant or integration, addressed as handle@slug. |
| Client | A customer account with users, contacts, billing recipients, pricing, and documents. |
| Client user | A person who belongs to one client. Regular by default; elevated when added to a project. |
| Elevated client user | A client user who is a member of a project, working there with a full login. |
| Billing contact | A client user flagged to download the client's timesheets and see bank balances. |
| Contact | An email identity without a login. Can correspond by email; grants no access. |
| Billing recipient | An address designated on a client that receives its timesheet documents. |
| Project | The collaboration boundary: members, a billing client, collaborating clients, tickets. |
| Billing client | The client a project's tickets are billed to by default; empty means internal work. |
| Collaborating client | A further client on a project whose users can be elevated and whose tickets can be billed to it. |
| Ticket | The one object: a request, a task, or a piece of work, with id ACME-184. |
| Kind | The type of ticket: Planning, Implementation, Bug, Support by default. Drives billing policies. |
| State | Where a ticket is in the workflow; each state is open or closed and is a board column. |
| Priority | An ordered list; boards sort by it. |
| Label | A free tag on a ticket, unique by name per workspace. |
| Ticket link | Blocks, relates to, duplicates, and parent/child. |
| Estimate | Planned effort on a leaf ticket; parents show the sum of their children. |
| Comment audience | Shared, Internal, or Staff: who may read a comment. |
| Viewer | An explicit access grant on one ticket. Mentions create viewers. |
| Inbox and Review | Where email waits: the shared Inbox for triage, restricted review for internal or unverified mail. |
| Time entry | A date plus a duration on a ticket, logged by a workspace user. |
| Period | A month or a week of time entries. Closing it freezes the work facts. |
| Correction | A signed adjustment to an entry in a closed period, made in the open period. |
| Consultant category | The category a person's time is priced under; snapshotted on each entry. |
| Rate card | Hourly rates per category and date, per client or per project. |
| Billing policy | Per kind: paid, free, or a time bank. |
| Time bank | Prepaid or recurring hours a client draws on. |
| Billing mode | Per period (time and materials) or when the ticket closes (deliverables). |
| Billing run | Prices one client's time for one closed period and produces the timesheet. |
| Client timesheet | The numbered, immutable document a run produces (HTML, PDF, CSV). |
| API token | A key (saq_…) for the API and MCP, personal or belonging to an agent. |
| Scope | What a token may do: read, write, triage. |
| Notification | An email about a ticket event, filtered by your preference and your access. |
Words SAQ does not use
If you come from another tool, these are the nearest SAQ equivalents.
| You might look for | In SAQ |
|---|---|
| Watcher, follower, subscriber | Viewer. Being a viewer grants access as well as notifications. |
| Approve or submit a timesheet | Close a period. There is no approval step; the close is the lock. |
| Status | State. |
| Tag | Label. |
| Epic, milestone, sub-task | A parent ticket with child tickets. See Ticket link. |
| Team | Project membership. Access is per project, not per team. |
| Sprint, iteration | None. Use start and due dates, priorities, and boards. |
| Plan or schedule work, capacity planning, resource allocation, workload | None. SAQ has no planning module. Work is planned by assigning a ticket to a person and giving it a start and due date and an estimate. See Update a ticket. |
| Timer, stopwatch | None. A time entry is a date and a duration. |
| Invoice | None. The client timesheet is the input to your invoicing system. |
| Custom field | None. Use kinds, labels, and the description. |
| Webhook | None. Integrations read through the API or MCP; notifications are email. |
| Group, department, organisational unit | None. A client is the only grouping of people outside the workspace. |