← All use casesUSE CASE 07 / TEAM2FA

Support clients with defined access.

Give technicians the codes for the customers they support, with separate membership and reviewable activity.

No application subscription · Enterprise coming soon
T²TEAM2FA / EXAMPLE WORKSPACE● ● ●
CODE GROUP / CUSTOMER TENANT

Customer Tenant

◉ Assigned technicians · Viewer
CCloud tenant••• •••
NNetwork console••• •••
HHelp desk••• •••
Illustrative labels · Codes concealed
A REALISTIC SCENARIO

Picture this.

An MSP technician needs an administrator code for a client’s cloud tenant during a support ticket.

THE WORKFLOW

Set up the right access in three moves.

Start with the actual accounts and responsibilities involved. Adjust group membership as the work changes.

  1. 01

    Separate customer environments into organizations where appropriate.

  2. 02

    Invite technicians and grant the minimum group role for their assignment.

  3. 03

    Remove access at handoff and rotate external secrets after sensitive departures.

THE SECURITY BOUNDARY

Keep the wider login in view.

A shared code should never stand in for the customer’s service permissions, ticket approval, or privileged access process.

A COMMON QUESTION

Can technicians support several customers?

Yes. A technician can be invited into multiple organizations and switch between their memberships.

READY WHEN YOUR TEAM IS

Make access easier to manage.

Start with Pro at $0 per month. Create a team or join one through an invitation.

Create your team ↗

Explore another workflow

Essential session cookies and a local privacy preference keep the service working. Optional analytics is currently inactive, even if you allow it.