Create and manage client workspaces, invite users, configure roles, and navigate between accounts.
Loading the guide...
Did this answer your question?
Help us make the guides more useful.
0 helpful · 0 not helpful
Create and manage client workspaces, invite users, configure roles, and navigate between accounts.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Sub-accounts are client workspaces in Seedly CRM. Each sub-account is isolated - it has its own contacts, conversations, pipelines, workflows, invoices, and settings. Data from one sub-account is never visible from another.
This page covers creating sub-accounts, managing users and roles, and switching between accounts.
Seedly CRM uses a three-tier hierarchy:
There are two types of sub-accounts:
Every brand has one admin sub-account, created automatically when the brand is set up. The admin sub-account:
The admin sub-account is your brand's own operational workspace. Use it for your agency's internal work or as a sandbox for testing workflows before deploying them to client accounts.
Standard sub-accounts are created for each of your clients. They operate independently - each account manages its own settings, phone numbers, email domains, and integrations. Brand settings do not automatically cascade to standard sub-accounts.
The new sub-account is assigned to your currently active brand.
Sub-accounts move through these states:
| State | What It Means |
|---|---|
| Active | Normal operation - fully accessible to all assigned users |
| Suspended | Temporarily blocked - data is preserved but all access is paused. Agency owners and brand admins can still manage the account |
| Deactivated | Soft delete - data is preserved but non-admin users lose access. Can be reactivated |
| Cancelled | Permanently closed - data is preserved for a retention period |
Admin sub-accounts cannot be deactivated, suspended, or cancelled.
Seedly CRM includes four built-in system roles, arranged in a strict hierarchy:
| Role | Scope | What They Can Do |
|---|---|---|
| Agency Owner | Full agency + all sub-accounts | Unrestricted access to everything - billing, plans, system configuration, all sub-accounts. An agency owner cannot be locked out of a sub-account they own (removing their own membership no longer leaves them unable to re-enter). |
| Brand Admin | Brand + its sub-accounts | Manages all sub-accounts within their brand, including branding, billing schedules, and integration overrides |
| Sub-Account Admin | Single sub-account | Full control within their assigned sub-account - user management, settings, and all modules |
| Sub-Account User | Single sub-account | Day-to-day permissions controlled by their role assignment |
You can create custom roles at the agency level or sub-account level. Each custom role defines exactly what a team member can and cannot do, across 35 modules with four actions each (view, create, update, delete).
To speed up role creation, start from a template:
| Template | Description |
|---|---|
| Full Access | All permissions on all modules |
| Admin (No Billing) | Full access except billing and plan management |
| Sales Rep | Contacts, pipelines, conversations, tasks, and calendar - no settings or admin |
| Standard | Common day-to-day permissions for most team members |
| Limited | Read-only access with create/edit only on assigned records |
For each permission, you can also set a scope that controls which records the user can access:
| Scope | What It Means |
|---|---|
| Own | Only records assigned to the user |
| Team | Records assigned to anyone on the user's team |
| All | All records in the sub-account |
For example, a sales rep might be able to view all contacts but only edit the ones assigned to them.
Users cannot create or assign a role that is equal to or higher than their own. This is enforced at the backend and cannot be bypassed.
Paste or enter multiple email addresses to invite a group in one pass, with the same role and the same sub-account access applied to all of them. Each person still gets their own invitation.
If an invitation email cannot be delivered, the invitation says so rather than appearing to have been sent. That matters because the invite itself is still valid: you can pass the person their link another way instead of waiting on an email that is never going to arrive.
Pending invitations appear below the users table. For each invitation you can see the email, who sent it, the assigned role, and whether it has expired. Click Revoke to cancel a pending invitation.
You only ever see invitations for sub-accounts you have access to.
Anywhere you pick a team member, assigning a conversation, @mentioning someone in a note, choosing an owner, the picker is searchable. Type part of a name to filter. On a large team this is the difference between a usable list and one that quietly stops short of everyone.
To quickly match one user's access to another:
This clones the source user's role assignment to the target user.
Teams let you group users for scope-based access control. When a permission scope is set to "Team", users can access records assigned to anyone on their team.
A user can belong to multiple teams. Team membership affects which records they can see and edit when their role uses "Team" scope.
If you have access to multiple sub-accounts, use the account switcher in the sidebar to navigate between them.
The switch is instant - all modules (contacts, pipelines, conversations, and everything else) immediately reflect the selected account's data. No page reload is needed.
You can be in one sub-account at a time. If another browser tab or device switches to a different sub-account while a page is open, that page shows a message saying the workspace is open somewhere else, with Use it here and Leave this page. Whatever you had open underneath, such as a half-typed reply, is left as it was.
Pin your most-used accounts so they are always easy to reach.
| Capability | Detail |
|---|---|
| Sub-account types | Admin (1 per brand, auto-created) + Standard (1 per client) |
| Lifecycle states | Active, Suspended, Deactivated, Cancelled |
| Data isolation | Complete - no cross-account data access |
| System roles | 4 (Agency Owner, Brand Admin, Sub-Account Admin, Sub-Account User) |
| Custom roles | Unlimited, at agency or sub-account level |
| Role templates | 5 (Full Access, Admin No Billing, Sales Rep, Standard, Limited) |
| Permission modules | 35 |
| Actions per module | 4 (view, create, update, delete) |
| Scope options | 3 (own, team, all) |
| Invitation expiry | 7 days |
| Account switching | Instant, with search and pin-to-favorites |