Client Roles & Permissions
Roles for the people who log into your client portal — kept entirely separate from your internal team's roles.
What is this?
Client Roles & Permissions works exactly like the employee-facing Roles & Permissions page, but every role, user, and permission here is scoped to your client portal instead of your internal team. A new tenant starts with one built-in role, Owner, described as having full access to all client-portal modules.
Why use it?
If you invite multiple contacts from a client's organization into your portal, roles let you decide what each of them can see — for example, someone who can view invoices but not download them, versus someone who can do both.
Before you start
- Required role: Owner or Admin (on your internal tenant — not to be confused with the client-facing “Owner” role itself).
- Warning: use the Grid view and its “Open” button to open a client role's detail page. Opening a role by clicking its name in List view can fail to load (see Common Problems below) — use Grid view if that happens.
How to open it
Settings › Roles & Permissions › Client Roles & Permissions
How to use it
- Open Client Roles & Permissions. Switch to Grid view if it isn't already selected.
- Click + New Role to add a client-facing role, exactly as you would for an employee role.
- Click Open on a role's card to manage its users and module permissions.
- Add or remove client users and module permissions the same way as on the employee Roles & Permissions page.
Employee roles vs. client roles
| Employee Roles & Permissions | Client Roles & Permissions |
|---|---|
| Controls access to your internal EnOpSy dashboard. | Controls access to your client-facing portal. |
| Assigned to your team members. | Assigned to your clients' contacts. |
| Comes with many existing roles by default (varies per tenant). | Comes with a single built-in “Owner” role by default. |
| Permissions map to internal modules (ETA, Drive, Teams, etc.). | Permissions map to client-portal modules (Tickets, Billing, Company Details, etc.). |
Employee and client roles are stored and managed completely separately — a permission granted on one side has no effect on the other.
What happens after saving?
Changes save immediately, the same as on the employee Roles & Permissions page.
Common problems
Problem: The page shows “Loading department…” forever and never opens the role.
Why it happens: A known issue with the List view's title link for client roles.
How to fix: Switch to Grid view and click the Open link on the role's card instead — this path works correctly.
Problem: The Owner role's permission count looks empty.
Why it happens: Owner-level access for the client role may be granted by its role type rather than by explicit checkboxes; this is being confirmed with the engineering team.
How to fix: No action needed on your end — if your Owner-level client contacts report missing access, contact support rather than trying to fix the permission grid yourself.
FAQs
- Can a client role see my internal Settings?
- No — the client portal and the internal dashboard are separate applications with separate role systems. Client roles cannot reach internal Settings pages.
- Do client roles support permission expiry dates the same way employee roles do?
- The Add User flow follows the same pattern as employee roles; confirm the expiry-date field is present for your tenant's version before relying on it for a specific client contact.