Check on customers
See every customer's answers, deadlines and setup in the Platform area, and read a customer's records and requests while they give you support access.
Customers in the Platform area lists every project on the deployment, with what needs attention first. It shows counts, dates and setup only. A person's records and requests open only while the customer gives you support access.
Before you start#
- To see the list and each customer, you need
Consent.PlatformServices.fetchCustomers. - To read records, requests and the audit log under support access, you also need
Consent.PlatformServices.viewCustomerDataWithSupportAccess.
Find who needs attention#
Due now lists every late duty across customers, then the rights requests due within 5 days, most urgent first. Each line says who acts on it. The Customers tab counts the customers with something late.
The table below puts urgent matters first, then the customers with the most answers in the last 30 days. Choose a column head to sort by it. Needs attention leaves out setup hints. Quiet and Setting up show those customers alone. A link keeps the filter, search and sort.
| Shown | When |
|---|---|
| Board report overdue | A breach is past its 72 hours, or its extension, without a report to the Data Protection Board |
| Requests past their deadline | An open rights request is past its due date |
| Processor tasks overdue | A task sent to a processor is open past its due date |
| SDF assessment overdue | The latest assessment of a kind is past its next due date |
| Over the monthly limit | This month's records are over the project's monthly limit |
| Heading over the monthly limit | At this month's pace, the records pass the limit by the month's end |
| No answers for a week | The project has a live key and a published form, but no answer for 7 days |
| Key waiting for you to approve | A key waits for live approval. See Approve live keys |
| Not live yet | A form is published, but there is no live key |
| Nothing published | The project has a site but no published form |
The figures are worked out at most once a minute. Refresh works them out again, and Download CSV saves the table as you see it, counts and setup only.
A customer appears once their project has a site or saved settings, or someone from it signs in. The organization's name is filled in when someone from it signs in. Until then the list shows the name on the customer's notices.
Look at one customer#
Choose a customer to see:
- What needs doing, late duties first, then setup still missing
- Answers in the last 30 days against the 30 days before, and the share that allowed everything
- Answers per day for 30 days on live sites
- Where their rights requests arrive, their Data Protection Officer and grievance officer, and how many people hold each role
- Each site with its keys, region rules, last tracker scan and forms
- Their rights requests by kind
Read records and requests#
- Ask the customer to give support access. See Give support access.
- Open the customer. Records, requests and audit log shows until when access lasts, who gave it, why, and what it covers.
- Choose Records, Requests or Audit log, whichever the customer ticked. Open a record from the list, or by its consent ID.
Each page you open is written to the customer's audit log with your name before you see it. The customer sees the same list in Settings. Read only what their reason needs.
| Answer | Meaning |
|---|---|
403 SUPPORT_ACCESS_NOT_GRANTED |
The customer has not given access, or it has ended |
403 SUPPORT_VIEW_NOT_IN_SCOPE |
The customer's access does not cover this view |
503 SUPPORT_VIEW_NOT_LOGGED |
The audit entry could not be written, so nothing is shown |