User Types
AutoRABIT (ARM) separates users into three distinct categories—each with its own set of privileges and responsibilities. Understanding these roles helps administrators grant the right level of access and manage the platform efficiently.
Registered Admin
The Registered Admin is automatically created when someone in your organization purchases an ARM subscription and signs up for the first time. Acting as the primary liaison with AutoRABIT, this user has privileges that no one else—including Org Administrators—can match.
Special capabilities
Subscription Management – upload license keys, configure seats, and view subscription details.
Team Management – create and configure teams/company settings.
Exclusive communication channel with AutoRABIT for requests such as:
Installing or configuring agents
Reassigning the Registered Admin role
Increasing license counts or extending subscription validity
Org Administrators
Org Administrators—often just called Admins—manage the day-to-day configuration of ARM. They can:
Create, edit, or delete users
Assign or revoke roles and permissions
Enforce SSO requirements
Export user lists to CSV
Perform nearly every task the Registered Admin can, except those reserved for subscription management
Admins can hold multiple roles. When more than one role is assigned, ARM applies the most permissive set of rights.
General Users
General users operate ARM based on the permissions granted by their Org Admins. They:
Cannot access the Admin dashboard
See only the modules and controls assigned through roles
Focus on development tasks like EZ-Commit, CI jobs, deployments, or data loading—without administrative overhead
Assigning the appropriate role ensures General Users have just enough access to do their work while protecting sensitive settings and data.
Quick Reference
Registered Admin
Subscription, license, team, and agent management; escalation point for AutoRABIT support.
Yes (full)
Org Administrator
User/role management, SSO enforcement, environment setup, CI/CD configuration.
Yes (full, except subscription page)
General User
Day-to-day dev tasks: commits, merges, deployments, reports, etc.
No
Use these roles to delegate responsibilities appropriately and maintain a secure, well-governed ARM instance.
Last updated
Was this helpful?