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

Permission Templates

Nine templates cover common lab roles. Each template sets a base role and bundles the right permission bundles:

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

Last updated: May 24, 2026