Backlog
Features, bugs and reports across every SQN tool — in one place.
Open
0
In Progress
0
Done
0
High priority
0
Open 0
Nothing here
In Progress 0
Nothing here
Done 0
Nothing here
Future builds 0
Bigger asks, parked — nobody is chased about theseDrag anything here that's worth doing but not now
Google Chat notifications
Posts a card into a Space when a request is raised, replied to, or resolved. In Google Chat: open the Space → Apps & integrations → Webhooks → Add webhook, then paste the URL here. Stored server-side and never shown again.
QC Feedback
Every hallucination or false positive reviewers have flagged on the Survey QC tool, grouped by root cause. Only covers feedback submitted from today onward.
Flagged
0
Distinct issues
0
Sent to Claude
0
Fixed
0
No feedback matches this filter.
QC Trends
Every audit the Survey QC tool has processed, not just the ones someone flagged — what it finds most often, and on whose reports. These are AI-flagged findings, not confirmed defects; check for anything marked a false positive.
Audits processed
0
Total findings
0
Critical
0
Surveyors
0
Most common findings — click one for affected reports
By category
By surveyor — click a row for their findings
| Surveyor | Audits | Critical | Warning | Info | Total |
|---|
No audits in this range.
System health
Live status of every service, integration and data link.
Notifications
What Atlas pings people about, who gets it, and how.
Send a custom message
Straight to Chat and/or email, right now. Not saved as a rule — each send is its own message to whoever you pick below.
Nobody picked yet.
Google Chat spaces
An incoming webhook posts into one Space — good for a team channel. Messaging a person directly is a different thing and needs the Chat scopes below.
Chat messages reach whoever has the Atlas app
Atlas sends as a Chat app, and a Chat app can only post into a
direct message that already exists — it cannot start one. So
somebody who has never been given the app gets an email instead,
automatically, with nothing to fix per person.
To cover everyone at once, an admin installs the Atlas app for the
whole domain from the Google Workspace Marketplace. Until then it
reaches only the people listed on the Chat API Configuration page.
Permissions
Choose which apps each staff member can see and whether they can edit.
| Staff | Status | Preset |
|---|
Checkpoint — branch flag admins
Who sees a branch's open flags on the dashboard "Branch flags" card and can mark them done. Separate from the Checkpoint (manage) grant above — no permission needed, just an email per branch. Comma-separate more than one person.
Management access
Which parts of the Management dashboard each person can open. Everything here is enforced on the server, so a section that's off is refused, not just hidden.
Default means nobody has decided for this person yet, so they get whatever the old rules gave them — the exec list for financials, a Management Dashboard grant for the rest. The resolved answer is shown beside each row, so you can always see what Default actually means for them.
Setting any section here also lets that person into the dashboard — you don't need to grant Management Dashboard on the Apps tab as well. That tab still controls whether they see every branch or only their own, which is a separate question from which screens they get.
Approval matrix
Who may approve what, by dollar amount and branch — one matrix, and it decides both purchase order approval and expense claim approval. Claims add three rules on top that this table can't express: no auto-approval (a purchase order's on-charged codes skip approval because the cost is recovered from the client — a claim is still somebody asking to be paid), no self-approval ever (the second signature IS the control), and a Director may approve a claim of any amount. Editing here changes routing in both apps at once — this is the identical matrix Purchasing's own Admin tab edits.