Team Administration
Invite team members, assign role-based permissions with stackable bundles, configure directory sync with Entra ID or Okta, and manage external identity mappings — all scoped to your tenant.
How It Works
Vorian Connect separates identity from authorization. Zitadel OIDC handles authentication — who you are. The Team Administration page handles authorization — what you can do. After sign-in, every user has a role (member, technologist, supervisor, admin, director) and optional permission bundles that stack additional capabilities on top of the base role.
Permissions are enforced at the API layer. Every dashboard route and API endpoint checks for the required permission before allowing access. Source-scoped users only see instruments explicitly assigned to them — a technologist assigned to Chemistry Analyzer 1 cannot view Hematology Analyzer 2 data.
What's Included
- Member roster — view all team members with their role, permission bundles, source scopes, and account status (active, disabled, pending invitation).
- Email invitations — invite new members by email with a specific role. Invitations expire after 7 days. Each invitation generates a unique token link.
- Bulk onboarding — upload a CSV to invite multiple team members at once. Preview mode validates emails, roles, and permission templates before sending. Downloadable CSV templates with reference column documentation.
- Permission templates — nine pre-built presets: Lab Operations, Supervisor, Rules Admin, QC Manager, Interface Engineer, PHI Troubleshooter, Migration / Validation, Audit / Privacy, and Team Admin. Each template bundles the right permissions and source scope mode for a common role.
- Stackable permission bundles — add individual bundles (lab-operations, qc-management, rules-management, interface-configuration, delivery-configuration, migration-validation, phi-troubleshooting, audit-privacy, team-administration) on top of any role.
- Source-scoped access — limit a user to specific instrument sources. Scoped users only see data from their assigned instruments across all surfaces — messages, QC, worklist, preanalytical, and routing.
- Member management — update roles, permission bundles, and source scopes for existing members. Disable accounts (preserves audit trail for reactivation) with a required reason.
- External group mappings — map IdP group claims to Vorian roles and permission bundles. When a user authenticates through Entra ID or Okta, their group memberships automatically grant the correct Vorian permissions. Supports priority ordering and preview evaluation.
- Directory sync — connect to Entra ID, Okta, ADFS, or any SCIM-compatible directory. Scheduled syncs automatically create invitations for new users, update pending invitations, and flag accounts for deactivation review when users leave the directory.
- Deactivation review queue — when directory sync detects users missing from the directory, they appear in a two-step review queue. A Team Admin approves the review, then a separate Team Removal admin executes the account disable. Approve and execute are distinct actions with audited reasons.
Permission Templates
Nine templates cover common lab roles. Each template sets a base role and bundles the right permission bundles:
- Lab Operations — technologist base role. Live feed, worklist, specimens, storage, add-on orders, preanalytical review. No configuration access.
- Supervisor — supervisor base role. Operator workflows plus QC authority, observability, and team visibility.
- Rules Admin — member base role. Autoverification rule lifecycle management without broad team or billing administration.
- QC Manager — supervisor base role. QC exclusions, reinstatement, PDF binders, delta checks, and result approval.
- Interface Engineer — member base role with all-source scope. Source setup, topology, mapping, interface builder, delivery configuration, and source commands.
- PHI Troubleshooter — member base role with all-source scope. Audited raw HL7/PHI viewing through the PhiReasonDialog for troubleshooting message failures.
- Migration / Validation — member base role with all-source scope. Shadow-mode DI migration, validation exports, cutover evidence, and source command support.
- Audit / Privacy — member base role. Audit log review, PHI-safe audit CSV exports, and patient data erasure workflows.
- Team Admin — member base role. Team membership, invitations, external identity mappings, bulk onboarding, and tenant settings.
Where It Fits
Team Administration lives in the Administration section of the dashboard sidebar, alongside Audit, Billing, and Patient. It requires team:view for read access and team:manage or team:invite for write operations. The Team Admin permission template bundles all team-management actions.
Team administration is tenant-scoped — each Vorian Connect tenant manages its own members independently. Platform-level user operations (modifying vorian_admin or super_admin rows) are restricted to platform administrators and cannot be performed through tenant Team APIs.
Technical Details
- Auth provider: Zitadel OIDC for identity. Vorian Connect owns application permissions.
- Roles: member, technologist, supervisor, admin, director. Set in
users.role. - Permission bundles: Additive. Stored in
user_permission_bundles. Bundles are stackable — a Supervisor with qc-management added gets both operator and QC capabilities. - Source scopes: Stored in
user_permission_scopes. API routes filter by authorized source IDs. Users without source scopes see all tenant data (subject to their role and bundles). - Invitation flow: POST to
/api/teamcreates an invitation with a 7-day expiry. The invite link at/invite/[token]guides the new user through Zitadel sign-up. Pending invitation grants (bundles and scopes) are stored ininvitation_permission_bundlesandinvitation_permission_scopesand applied on acceptance. - Bulk onboarding: CSV uploads support columns for email, first_name, last_name, display_name, permission_template, base_role, permission_bundles, source_scopes, and send_invite. Dry-run mode validates all rows before creating invitations.
- Directory sync providers: Entra ID (Azure AD), Okta, ADFS, and generic SCIM. Connections are configured with a SCIM base URL, external ID claim, group claim, cron schedule, and sync policy controls (invite missing, update pending, skip inactive, deactivate missing).
- External group mappings: Match IdP claim values to Vorian roles, permission bundles, and source scopes. Priority-ordered — higher priority mappings take precedence. Preview shows how a sample claim text would resolve.
- Account lifecycle: Users have
access_status—activefor normal access,disabledfor deactivated accounts (row preserved for audit and reactivation). Disabled users are blocked from product access bygetAuthenticatedUser(). Deactivation requires an audited reason and a required audit row write that fails closed. - Audit logging: Invitation creation, member updates, role changes, permission changes, and deactivation are all logged to the tenant audit trail.