Documentation

How SAQ works, for the people who use it every day, the people who set it up, and the developers who connect other systems to it.

Written for
user, admin, integration-developer
Roles
Requires
Feature
docs

SAQ is a ticket system with project management, time tracking, and client billing built around one object: the ticket. This documentation is the reference for how the product behaves. It is written so that every page can be read on its own, and it is the same source the app's AI tools and the MCP server answer from.

Start here

New to SAQ? Read these four pages in order. Together they take about fifteen minutes.

  1. What SAQ is: the idea behind one ticket for support, project work, and billable time.
  2. Core concepts: how a workspace, clients, projects, tickets, time entries, and billing fit together.
  3. First login: invitations, passwords, passkeys, two-factor authentication, magic links, and single sign-on.
  4. Finding your way around: the sidebar, My work, the command palette, and keyboard shortcuts.

Then pick the page for your role under Documentation by role.

Find an answer

  • Something about a ticket, time, or billing does not behave as you expect. Open the feature page for the task; every task page has a "Common problems" section with the exact error text and what it means.
  • You cannot do something. Every page states who can do it under "Before you start". The permission model explains the three roles, client user modes, and project roles.
  • A word you do not know. See the terminology list and the Concepts section.
  • You are integrating another system. Start with the integration developer overview and the API reference.

Sections

  • Getting started

    What SAQ is, the words it uses, first login, and where things are.

  • Documentation by role

    What each kind of user can do, with links to the tasks that matter to them.

  • Tickets

    Create, work, comment on, link, and find tickets. Boards and My work.

  • Projects and clients

    Projects, project members, clients, client users, and viewers.

  • Time tracking

    Log time, check the week, close periods, correct closed time, and report.

  • Billing and timesheets

    Consultant categories, rate cards, billing policies, time banks, billing runs, and client timesheets.

  • Email and the Inbox

    Connect a mailbox, triage the shared Inbox, and handle restricted review.

  • Administration

    Members, workflow, labels, workspace settings, authentication, tokens, audit, export, and plans.

  • Concepts

    The domain model: one page per term, and how the terms relate.

  • Integration developers

    The REST API, MCP, authentication for integrations, SCIM, single sign-on, and recipes.

  • API reference

    Every public HTTP operation by resource: purpose, permissions, parameters, examples, errors.

  • What SAQ is SAQ keeps support, project work, and billable time on one ticket, so the same record is followed from the first email to the client's timesheet.
  • Core concepts How a workspace, its users, clients, projects, tickets, comments, time entries, periods, and billing relate to each other in SAQ.
  • First login Accept your invitation, choose a login method, set up two-factor authentication if you are an Owner or Admin, and find your workspace.
  • Documentation by role How workspace role, client user mode, and project role combine into what a person can do in SAQ, with the full permission matrix and a page for each role.
  • Integration developer overview What you can connect to SAQ, what does not exist, where the OpenAPI document is, and a five-minute first call with an API token.