OrbitusOrbitus
  • Home
  • About
  • Pricing
  • Contact
Sign InSign Up
OrbitusOrbitus

Build amazing web applications with Orbitus

Products

FeaturesPricingDocsStorybook

Support

Getting StartedFAQCommunityContact

Newsletter

Get the latest updates and articles directly in your inbox.

You can unsubscribe at any time. Read our

Privacy Policy
© 2026 Orbitus • All rights reserved.
v1.0.1
website.help.helpCenter/Users/Sub-User Management

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: 04/14/2026, 10:13 AM
<div class="features-wrapper"> <h2>Delegated Administrative Access</h2> <p>Not every team member needs full platform access. <strong>Sub-Users</strong> 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.</p> <div class="feature-grid"> <div class="feature-card"> <h3>👤 Sub-User Creation</h3> <p>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.</p> </div>
<div class="feature-card">
  <h3>🔒 Granular Permission Sets</h3>
  <p>Assign module-level permissions independently: a sub-user can have full access to <strong>Tickets</strong> and <strong>Knowledge Base</strong> but read-only access to <strong>Sales</strong> and no access to <strong>Settings</strong>. Permissions granularity includes: View, Create, Edit, Delete, Export for each module.</p>
</div>

<div class="feature-card">
  <h3>📊 Activity Monitoring</h3>
  <p>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.</p>
</div>
</div> <div class="usecase-example"> <h3>Use Case: Department-Specific Access</h3> <p>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.</p> </div> </div>

Was this article helpful?

Comments0

Still need help?

Contact Support