Support access
Sometimes a person at Katara needs to look inside your environment to help with something: a run that stopped mid-effect, a notice that never arrived, a charge you disagree with. When that happens it is written down, and you can read what was written.
What a record says
Section titled “What a record says”Each grant is one purpose and one deadline, with the reason it was given. The purposes are reconciling a run, resending a notification and inspecting the ledger. A grant carries the account it was given to, when it was given and when it expires.
The list includes access that has ended, because a page showing only what is live now would answer “has anybody had access” with “not at this moment”.
What was done under it
Section titled “What was done under it”Each grant has its own record of what happened: when it was given, each time it was used, and when it ended. Asking whether the access was still live is itself recorded, so somebody who looked and then decided not to act still looked.
Ending an access
Section titled “Ending an access”You can end any grant, at any time, without asking. It stops the reading immediately and stays on the record as something you did, named as your organization rather than as a database connection. Ending one twice is ending it once, so a second attempt cannot move the time the access actually stopped.
Access to your own account
Section titled “Access to your own account”A notice to your own account, such as a security or billing notice, belongs to no organization. When one never arrives, support can be given access to resend it: one grant names your account, the reason and a deadline, and allows nothing but resending notices that never arrived. Nobody is given access to resend their own notices.
You read these grants, and end them, on the account security page. Only you can see
them. listAccountSupportAccess / list_account_support_access lists them,
listAccountSupportAccessUses shows what was done under one, and
revokeAccountSupportAccess ends it. These calls need your signed-in session; an API
key cannot make them.
What this page does not do
Section titled “What this page does not do”Granting happens outside the product. Katara staff are given access against a purpose and a deadline; nothing here creates a grant, and no request to this API can. This is the record of it, and the control to stop it.
Reading these records is limited to organization owners and administrators. Somebody who has to find out whether a person reached into their environment should not have to ask the people who did it.
See access and API keys for account binding and Test/Live separation. The product API reference documents the exact request and response fields.