Support Access

Quant Support can only look at your organisation when you let it. You give that consent by issuing a support token from Settings → Security → Support access, and you withdraw it by revoking the token. The page is also your record of that access: which tokens you issued, who issued them, and every request Quant Support made with them.

What a support token allows

  • Read-only. The token holds read-only permissions. Quant Support cannot change findings, risk acceptances, control evidence, incidents, policies or any other record. The token enforces this, so it does not depend on how the support agent behaves.
  • Time-limited. You choose how long it lasts, up to 30 days. It stops working when it expires, and you can revoke it sooner.
  • One organisation. The token is bound to the organisation that issued it and cannot reach any other.
  • MCP only. It works with the Assure MCP server that the support agent uses. The REST API refuses it.

You cannot widen these limits. The permissions are set by QuantAssure, not chosen on the page.

Issuing a token

  1. Go to Settings → Security → Support access.
  2. Optionally give the token a label, such as the support case it is for. The default is "Quant Support".
  3. Choose when it expires: 1, 3, 7, 14 or 30 days. The menu starts on 7 days.
  4. Click Issue token and copy the token.
The token is shown once and cannot be recovered. Give it to your Quant Support contact over a secure channel. Never paste it into Slack or a support chat.

Only owners and admins can issue or revoke support tokens, and only they see the Security tab. Members can still review the access history with the Support Access report.

Revoking a token

Open the token in the Support tokens list and click Revoke. Access stops straight away. The revoked token disappears from the list, and its issue and revocation stay in your audit log. In the audit log they show in each row's action badge as api key.support created and api key.support revoked (the underscores are shown as spaces). Expired tokens stay in the list, marked Expired, until you revoke them.

Support access history

Every tool call and resource read made with a support token is recorded before any data is returned. If the record cannot be written, the request is refused. Each entry shows:

  • when it happened
  • the tool or resource used, such as get_finding or list_runs
  • the ids it was given, such as the finding id
  • the support case it was made for. No case means Quant Support did not give a case reference
  • the token it was made with

Filter by case id (exact match) or by date to answer "what did support look at for this case?". The history holds what was accessed, never the data returned or any free text Quant Support searched for.

The same entries appear in your audit log as support.access events, attributed to Quant Support (marked Support), alongside the rest of your organisation's activity. To see only these, choose Support Access in the audit log's Action menu.

Using it as evidence

For a review of third-party access, the support access page and audit log show who authorised Quant Support's access, when it was issued and revoked or expired, and what was accessed under each support case.

To hand that evidence to an auditor, generate a Support Access report from Reports for the review period. It lists the support tokens live in the period (issued, by whom, expiry, revoked) and every access grouped by support case, as a print view, CSV or JSON. See Reports. Accesses recorded before this report existed show no token name.