Tenants & Accounts

RPA Watch uses a two-level organizational structure: tenants and accounts. This structure keeps data isolated between teams and clients while allowing centralized management.

Tenants

A tenant is the top-level entity representing your organization. When you register for RPA Watch, a tenant is created automatically.

Tenant Properties

Tenant Types

Choose Direct if all your users belong to one organization. Choose Consulting if you manage automation for multiple clients (see [Consulting](/docs/consulting-setup)).

Accounts

An account is an isolated workspace within a tenant. It acts as a boundary for data — processes, jobs, robots, API keys, and schedules all belong to a specific account.

When to Use Multiple Accounts

- Clients: Consulting firms create one account per client

- Environments: Separate production and development data

- Business Units: Large organizations with distinct automation teams

Account Properties

Creating an Account

Tenant admins can create new accounts:

1. Navigate to Accounts in the sidebar (tenant admin view)

2. Click Create Account

3. Enter the account name and slug

4. Select the RPA tool (can be configured later)

5. Click Create

Each new account starts empty — you'll need to configure RPA credentials, invite members, and either sync or ingest data.

Data Isolation

Data isolation is enforced at the account level:

- Account-scoped users (account_admin, account_user) can only see data in their own account

- Tenant-scoped users (tenant_admin, consultant) can see data across accounts within their tenant

- API keys are scoped to a single account — data ingested via API goes to the key's account

- There is no way for users in one tenant to see data from another tenant

What's Isolated Per Account

Checking Account Slug Availability

Before creating an account, you can check if the desired slug is available. Slugs must be unique within the tenant and can only contain lowercase letters, numbers, and hyphens.