Skip to main content
Tars staff have no standing access to your organization. When support work needs access, a Tars admin grants one staff member a temporary membership with a fixed role, a fixed end time, and a written reason. You can see that membership on the Organization page in Settings, remove it there, and read every action it took in your audit log.

​
What a support grant is

A support grant is a real membership in your organization, created by a Tars admin. Nobody in your organization is asked to approve it, and there is no request flow in your dashboard. The grant records four things: To change the role of an active grant, staff must end it and create a new one. Every check of a grant fails closed. If the grant has expired or ended, the staff member’s requests to your organization are refused with Support access has expired or Support access has ended.

​
What you see while access is active

Open Settings, select Organization, then open Members. The staff member appears in the list with the granted role, like any other member, for as long as the grant is active. When the grant ends, the membership is removed automatically. A support membership cannot hold a live-chat seat, so staff cannot reply to your end users from the inbox.

​
How access ends

Access ends in one of four ways, and each way is written to your audit log with its own wording. To end access yourself, open Settings, select Organization, open Members, and choose Remove member from the row menu of the staff member. Removal takes effect at once and the grant is closed behind it.

​
What your audit log shows

Open Settings, select Audit log, and filter the Category to Support. Every action taken under a grant, from the grant itself to each change the staff member made, appears with the actor TARS Support and a Support badge. Select a row to open its drawer. In the drawer, the Actor section shows TARS Support without a name or email, and the Reason section shows the typed note. The staff identity is masked only in your view. Tars keeps a second, internal record of the same action with the real staff identity, so every action stays attributable to one person. The two records are linked, so a dispute can be traced end to end without exposing staff details to you.
One action under a support grant written twice: your audit log shows the actor TARS Support with the staff identity removed, while the internal record keeps the real staff identity, and the two records are linked
Support rows are part of the same hash chain as the rest of your log, so they are covered by Verify chain integrity and by exports. See Search and export the audit log.