Support Access

Support Access governs whether, and for how long, TraceUnified support can access your organization’s environment. It puts that decision firmly in your hands: support has no standing access, and any access you grant is bounded and recorded.

The design principle here is that vendor access should be an exception you grant, never a standing arrangement you tolerate. Many incidents trace back to a support back door that was opened once and quietly left open; time-bounded, self-expiring grants make that failure mode impossible by construction. For a regulated system, being able to prove that even the vendor’s access was explicitly authorized, strictly bounded, and fully logged is part of demonstrating that you control all access to your data — including ours.

Granting access on your terms

When you need hands-on help, you enable support access for a defined duration — a window after which it expires automatically, so access doesn’t linger past the problem it was granted for. While it’s active, a support agent can assist within your environment; once the window closes, that access ends without you having to remember to revoke it.

Logged and accountable

Every action taken under support access is logged, so there’s a complete record of what was done, by whom, and when. This is essential for a regulated system: even legitimate vendor access has to be transparent and auditable, never a quiet back door. You can see the history of support access that’s been granted, and the activity that occurred under it.

Control over vendor access

The principle is least-privilege applied to the vendor relationship: support gets access only when you decide, only for as long as needed, and always under a recorded, expiring grant. Combined with the authentication logs and the platform’s audit trail, it ensures that all access to your regulated data — including ours — is something you can see, bound, and account for.