Managing Client Accounts
Creating accounts per client, configuring RPA tools per account, and user isolation
In a consulting tenant, each client gets their own account — an isolated workspace with its own processes, jobs, robots, API keys, and members. This article covers how to create and configure client accounts.
Creating a Client Account
1. Navigate to Accounts in the sidebar (requires Tenant Admin role)
2. Click Create Account
3. Fill in:
- Name: Your client's name (e.g., "Acme Corporation")
- Slug: URL-friendly identifier (e.g., acme-corp) — must be unique within your tenant
4. Click Create
The account is created empty and ready for configuration.
Configuring RPA Tool Per Account
Each client account can use a different RPA tool. This is one of the key benefits of the consulting model — you can manage clients running Robomotion, UiPath, or any other tool from a single platform.
Setting Up the RPA Tool
1. Switch to the client's account context (use the account selector in the navigation)
2. Go to Account Settings
3. Select the RPA Tool for this client:
- Robomotion
- UiPath
- Power Automate
- Automation Anywhere
- Blue Prism
4. Enter the client-specific credentials (API token, OAuth credentials, etc.)
5. Click Save and Test Connection
Credentials are stored encrypted and scoped to the account — no other account can access them.
Different Tool Per Client Example
```
Your Consulting Tenant
├── Acme Corp → Robomotion (API token from Acme's workspace)
├── Beta Inc → UiPath Cloud (External App from Beta's org)
└── Gamma Ltd → UiPath On-Prem (Client creds from Gamma's server)
```
Data Isolation
Data isolation between client accounts is absolute:
- Processes, jobs, robots, schedules in Account A are invisible to Account B
- API keys in Account A cannot submit data to Account B
- Account-level users in Account A have zero access to Account B
- Audit logs are scoped to each account
The only users who can see across accounts are tenant-level roles (Tenant Admin, Consultant).
## Inviting Client Users
To give your client direct access to their data:
1. Switch to the client's account
2. Go to Members
3. Click Invite Member
4. Enter the client user's email and select a role:
- Account Admin — Full control of their account (settings, members, API keys)
- Account User — View-only access to assigned processes
Authentication for Client Users
In consulting tenants, client users must use local authentication (email/password). When the invitation is accepted, the client creates a password — they cannot use your firm's Entra ID.
## Account Limits
Your license determines how many accounts you can create:
| Tier | Default Account Limit |
|------|----------------------|
| Trial | 10 accounts |
| Consulting Basic | Based on license |
| Consulting Pro | Based on license |
To see your current usage, go to Tenant Settings → Usage.
Managing Account Settings
As a Tenant Admin, you can manage settings for any client account:
- RPA credentials — API tokens, OAuth settings
- Members — Invite, update roles, remove users
- API keys — Create keys for programmatic data ingestion
- Sync — Trigger manual sync with the RPA provider
Switch to the target account using the account selector before making changes.
## Deactivating a Client Account
If you stop managing a client:
1. Remove all active members from the account
2. Deactivate API keys
3. The account remains in the system with historical data preserved
> Note: Account deletion is not currently supported to preserve audit history. Contact support for data removal requests.