Clarix
Administration

Managing Users

Invite users, assign roles, edit accounts, ban departing employees, and manage the role hierarchy in Clarix for 503B compounding facility administration.

The Users page at /admin/users is where administrators manage every person who has access to Clarix at your facility. Here you can invite new team members, adjust role assignments as job functions change, view the last login date for every account, and immediately revoke access when personnel leave. Keeping this page accurate and up to date is one of the most important administrative responsibilities in a 503B GxP system.

Admin users

Role required: Administrator or Super Administrator. All user management actions are logged in the audit trail with the administrator's identity and timestamp.

The user table

The main users table shows every account in your organization with the following columns:

  • Name — The user's display name
  • Email — The account's login email address
  • Role — The user's current assigned role (see role list below)
  • Organization — Which organization(s) this user belongs to (relevant in multi-site setups)
  • Status — Active, Invited (pending), or Banned
  • Last login — Timestamp of the most recent successful login

The table supports search by name or email, and filtering by role and status.

Inviting a new user

To add a new team member to your Clarix organization:

  1. Navigate to Admin → Users.
  2. Click Invite User in the top-right corner.
  3. Enter the new user's email address.
  4. Select their role from the dropdown (see role descriptions below).
  5. If your organization has multiple sites, select the organization they belong to.
  6. Click Send Invitation.

Clarix sends the user an email with a link to complete account setup (set a password and configure their profile). The invitation link is valid for 72 hours. If it expires, you can resend it from the user's row in the table by clicking Resend Invitation.

While the invitation is pending, the user's status shows as Invited and they cannot log in yet.

Editing a user

To change a user's name, role, or organization membership:

  1. Click on the user's row in the table, or click the Edit button (pencil icon) at the end of their row.
  2. In the edit panel, update the fields you need to change.
  3. Click Save Changes.

Role changes take effect immediately — the user's permissions update on their next page load or API call, without requiring a logout.

User profile fields

In addition to name, email, and role, each user record supports extended contact and organizational fields:

FieldDescription
PhoneDirect contact phone number for the user
SupervisorReference to the user's manager or supervisor within your organization hierarchy
Honorific titlePrefix such as Mr, Ms, or Dr — used on printed reports and labels where configured
SuffixName suffix such as Jr or Sr
AddressContact address fields: address line 1, address line 2, city, state, and postal code

These fields are optional. Populate them for personnel directories, training records, and audit trail display. The supervisor reference establishes your org chart in Clarix without affecting role-based permissions — a user's access is determined solely by their assigned role.

Note: Changing a user's role is a significant action in a GxP system. If you are demoting a QA Officer to a lower-privilege role (for example, due to a job function change), review any open deviations or CAPAs assigned to that person and reassign them before changing the role. The change is logged in the audit trail with the previous role and new role recorded.

Banning a user

Banning prevents a user from logging in immediately without deleting their account or their activity history. Use this action when an employee leaves the facility or when access needs to be suspended pending an investigation.

  1. Click the Ban User button on the user's row (or from their edit panel).
  2. Confirm the action in the confirmation dialog.
  3. The user's status changes to Banned and any active sessions are terminated immediately.

Banned users remain visible in the user table and their historical activity (batch steps, deviations, audit entries) is preserved and fully traceable. You can unban a user at any time by clicking Unban User on their row.

Note: Do not delete a user account if you want to preserve audit trail traceability. Deletion removes the user record, which can make audit entries display as "[Deleted User]" instead of the person's name. Ban instead of delete for departing employees, unless your data retention policy specifically requires deletion.

Deleting a user

To permanently remove a user account:

  1. Open the user's edit panel.
  2. Click Delete User at the bottom of the panel.
  3. Enter your own password to confirm the destructive action.
  4. Click Confirm Delete.

This action is irreversible. Historical audit entries for the deleted user will display as "[Deleted User]."

The role hierarchy

Clarix uses a structured role hierarchy to enforce separation of duties across 503B operations. Roles are cumulative from bottom to top — a higher role includes the permissions of all lower roles unless explicitly restricted.

RolePrimary function
ViewerRead-only access to batches, formulas, and inventory
TechnicianExecute batch steps, receive inventory lots
Senior TechnicianTechnician + can create batches, request amendments
Visual InspectorExecute visual inspection steps on assigned batches via iPad or web
VI TrainerTrain and qualify visual inspectors; manage VI qualification records
VI Trainer SupervisorSupervise the visual inspection training program and VI trainers
Technician TrainerTrain and qualify compounding technicians on SOPs and batch execution
Technician Trainer SupervisorSupervise the compounding technician training program and technician trainers
Lab TechnicianLab sample entry and result recording
EM TechnicianEnvironmental monitoring data entry
QA TechnicianQA review queue access, view deviations and reports
QA OfficerCreate and manage deviations, CAPAs, and OOS records
QA ManagerClose deviations and CAPAs, manage EM program, approve SOPs
Inventory ManagerFull inventory management including lot disposition
Equipment ManagerAsset management, calibration records, PM scheduling
Training CoordinatorTraining plan management, qualification records
Human ResourcesPersonnel administration, user onboarding support, org hierarchy maintenance
IT AnalystSystem support, integration configuration, and technical troubleshooting
PharmacistFormula authoring, batch review, label verification
PICPharmacist-in-Charge — full operational authority, batch release
AdministratorUser management, system configuration, audit access
Super AdministratorCross-organization admin, system-wide settings

Custom organization roles

In addition to the standard role hierarchy, administrators can create custom organization roles — role names specific to your facility's job titles that map to one of the standard system roles. For example, you might create a custom role called "Senior Compounder III" that maps to the Senior Technician system role. Custom roles appear in the role assignment dropdown for your organization and are visible to users in their profile, but the underlying permissions are determined by the mapped system role.

To create a custom role, navigate to Admin → Users and click Manage Roles in the page header.

Permission preview

When assigning a role, click the Preview Permissions link next to the role dropdown to see a full list of what actions that role can perform. This is especially useful when onboarding a new team member and you are deciding between two adjacent roles.

Best practices

Principle of least privilege — Assign the lowest role that allows each person to perform their job function. Do not assign PIC or QA Manager roles to technicians simply for convenience.

Separation of duties — FDA and USP <797> require that the person who executes a batch cannot also be the person who releases it. Enforce this by ensuring compounders hold Technician or Senior Technician roles and release authority is restricted to PIC.

Regular access review — At least quarterly, review the user table and confirm that every Active account belongs to a current employee with a legitimate need for access. Document your review in your quality system.

On this page