CliniConnects uses role-based access control to determine which parts of the platform a user can view and manage. Instead of giving all users the same permissions, the system assigns access based on role so users only see the modules and actions relevant to their responsibilities.
This structure helps separate operational, administrative, and financial responsibilities across the platform. It also supports secure access to sensitive areas such as company settings, billing, payroll, system configuration, and other restricted functions.
CliniConnects uses role-based access to help organizations:
Limit sensitive actions to authorized users
Separate operational work from administrative and financial controls
Keep navigation aligned with each user’s responsibilities
Support multiple internal roles working within the same platform
Role-based access appears in CliniConnects in two main ways:
Different sections of the platform are intended for different user groups. The SRS assigns sections and functions to roles such as:
Super Admins
Administrators
Clinicians
Intake Employees
Assigning Manager Employees
Assigning Employees
Recruitment Employees
Billing Admin
Treasury Employees
Some modules may be visible to a broader group, while specific actions inside them are still limited to certain roles. This helps ensure that higher-risk actions remain controlled even when a section is accessible.
Super Admins manage the overall platform and have access to high-level administration, company management, settings, and other system-wide controls.
Administrators manage many operational and administrative features across the platform, including patient workflows, agencies, clinicians, employees, reports, billing, and settings.
Healthcare employees support operational workflows based on their specific function. This includes intake, assigning, recruitment, billing, and treasury responsibilities.
Clinicians have a narrower access scope and use the platform for clinician-related workflows such as invoices, visits, calendar, schedule, and switching companies where permitted.
Understanding role-based access helps users know:
why some modules are visible and others are not
why certain actions may be unavailable
when a task needs a higher-level role or different permission
when they may need to contact an administrator for access support
This helps reduce confusion when a feature is restricted by role rather than missing from the system.
If a module, feature, or action is not visible, first check whether your role includes permission for that area. In CliniConnects, access is intentionally structured by role, so unavailable features may simply be restricted to another user type.