Review what ANKATech support did in the tenant
See every support session in which ANKATech support acted as your organisation, who entered, for how long, why each session ended, and every action taken during it.
Who can do it
A tenant administrator or a tenant auditor, and a platform super administrator or platform auditor. The session history needs an audit-reading role: a person who may read the support-access state but holds no such role sees the state and a history that says it cannot be loaded for that reason.
Before you start
- Support access applies only to a deployment hosted by ANKATech. Where your own organisation operates the platform, the screen says support access is not used on this deployment, and there is no history to read.
- The history is read from the signed audit events, so it stays readable after you withdraw an authorisation.
Steps
- Open Support Access from your tenant's navigation.
- Scroll to Support sessions.
- In Period, choose Last 7 days, Last 30 days or Last 90 days. The history opens on the last 90 days.
- Read each session: the Operator who entered, the Window it was open, whether it is still Open, Ended by, and the Actions taken, each as an entity type, an operation and a time.
What you see when it worked
One entry per session, most recent first. A session with no recorded action says "The session opened and closed with no recorded action." On a deployment hosted by ANKATech the operator appears as "Platform operator" followed by a short reference, never by name; the reference is the same for every session and action of one operator, and ANKATech can answer for each one when you quote it.
An authorisation that lapsed with nobody entering leaves no session here; its declaration is in your Audit Log.
If it fails
| What you see | Cause | What to do |
|---|---|---|
| "You do not have permission to read the session history. It requires an audit-reading role." | You hold no audit-reading role | Ask for one, such as the tenant auditor role |
| "The session history could not be loaded. This does not mean there were no sessions." | The read failed | Try again |
| "No support sessions in the selected period." | No session started in that period | Select Show the last 90 days, or read the API with a wider window |
Without the console
| Surface | How |
|---|---|
| API | GET /api/v3/audit/tenants/{tenantId}/support-access/sessions (operation listSupportAccessSessions), optional from and to. Without them the window is the last 90 days; the widest window is 365 days. Each session lists at most 500 actions |
There is no CLI command and no admin SDK method for the session history.
Related
- Support Access: authorising and withdrawing support access, and what a session can and cannot do.
- Search the audit log