Switching Between Accounts

Users with multiple memberships can switch between different tenants, accounts, and roles without signing out. This is called context switching.

When Do You Need Context Switching?

Context switching is relevant for consulting tenants that manage multiple client accounts. It is useful when:

- You belong to multiple organizations (tenants) — e.g., a user who has memberships in more than one tenant

- You manage multiple client accounts within a consulting tenant — e.g., a tenant admin or consultant overseeing several clients

- You have different roles in different scopes — e.g., tenant_admin in one tenant, account_user in another

> Note: Direct tenants have a single default account, so there is no account switching within a direct tenant.

How It Works

Your Current Context

When you sign in, RPA Watch loads your default membership — this sets your current:

- Tenant — which organization you're viewing

- Account — which client account you're viewing (consulting tenants only)

- Role — what permissions you have

All data you see is filtered by this context. Flows, runs, robots, schedules, and everything else are shown based on your current tenant and account.

Switching Context

If you have more than one membership, a context switcher dropdown appears in the top-left corner of the header, showing your current tenant and account name. To switch:

1. Click the context switcher dropdown in the header (tenant/account name with the up-down arrow icon)

2. A "Switch Context" menu opens listing all your memberships with their roles

3. Select the membership you want to switch to

4. RPA Watch issues a new session token with the new scope and redirects you to the dashboard

The switch is instant — no re-authentication is needed.

> Tip: If you have multiple memberships, you'll also see the Select Organization page right after login, where you can choose which context to start with.

Context Switching by Tenant Type

Direct Tenants

Direct tenants represent a single company monitoring its own automation. They have one default account created automatically during registration. Since there is only one account, there is no account switching — context switching only applies if the user has memberships in other tenants.

Consulting Tenants

Consulting tenants manage automation for multiple clients. Each client is represented as a separate account within the tenant. This is where context switching is most useful.

Context Switching by Role

Tenant Admin (consulting tenants)

Tenant admins have a tenant-level membership account_id is null). They can:

- View the tenant overview across all client accounts

- Switch into any client account to see its flows, runs, robots, and settings

- Switch between client accounts freely using the account selector

Consultant

Consultants also have a tenant-level membership. They can:

- View their assigned flows across client accounts

- Switch into a specific client account context when needed

- Only see flows they've been assigned to, regardless of which account they're viewing

Account Admin / Account User

Account-level users are tied to a specific client account. They can:

- Switch to a different tenant if they have memberships in multiple tenants

- Switch to a different account within the same tenant only if they have a separate membership there

Default Membership

When you have multiple memberships, RPA Watch signs you into your most recently used context. If this is your first sign-in, it uses the membership that was created first.