Sub-User Management

Manage administrative sub-users who assist the primary account owner in operating the platform. Create sub-user accounts with specific permission sets, assign module-level access, and maintain a clear separation between primary administrators and delegated operators.

Last updated 05/11/2026, 04:54 PM

Delegated Administrative Access

Not every team member needs full platform access. Sub-Users are administrative accounts created by primary account owners to delegate specific operational responsibilities. Each sub-user receives a tailored permission set that defines exactly which modules and actions they can access — from read-only viewing to full create/edit/delete capabilities.

👤 Sub-User Creation

Create sub-user accounts with name, email, and an initial password. Each sub-user logs in with their own credentials and sees only the modules they have permission to access. Their actions are tracked independently in the audit log.

🔒 Granular Permission Sets

Assign module-level permissions independently: a sub-user can have full access to Tickets and Knowledge Base but read-only access to Sales and no access to Settings. Permissions granularity includes: View, Create, Edit, Delete, Export for each module.

📊 Activity Monitoring

Track each sub-user's login history, last active time, and actions performed. This enables accountability and ensures delegated operators are performing their assigned duties effectively.

Use Case: Department-Specific Access

A company creates 3 sub-users: Sarah (Support Lead) gets full access to Tickets + Knowledge Base; Mark (Sales Rep) gets Orders + Quotes access with read-only Reports; Lisa (Content Manager) gets Knowledge Base + Media Library access. Each person sees only their relevant modules, reducing cognitive overload and accidental data modification.

Was this article helpful?

Still need help?

Our support team is ready to help you. Reach out and we'll get back to you shortly.

Comments

Leave a comment