Permission matrix

See which roles can access scheduling, interpreters, billing, settings, and audit logs.

Roles: OwnersAdmins
Surfaces: Web app
3 min read Updated February 12, 2026

At a glance

  • Use this matrix to standardize access across your team.
  • Treat Admin/Owner access as high risk: grant only when required.
  • If your workspace uses custom permissions, use this as the baseline and document your deltas. [Confirm in product]

Overview

The permission matrix describes what each role can do in Fluent. Exact capabilities may vary by workspace configuration, but the structure below is a recommended default.

Permission matrix

Legend: ✅ = allowed, ⚠️ = limited/conditional, ❌ = not allowed
Notes: Anything marked [Confirm in product] should be verified against your current implementation.

Capability areaOwnerAdminSchedulerBillingComplianceViewer
View appointments & calendar⚠️ (view only)⚠️ (view only)
Create appointments
Edit/cancel appointments
Assign interpreters
Offer-based scheduling
View interpreter directory⚠️ (limited)
Add/edit interpreter profiles⚠️ (limited)
Manage credentials & compliance docs⚠️ (view)
Manage rates & pay settings⚠️ (view)
View invoices⚠️ (view only)
Create/send invoices
Billing rules (minimums/rounding)
Mileage/travel billing rules
Exports (billing/payroll/reports)⚠️ (limited)⚠️ (limited)⚠️ (limited)
Workspace settings (org info, branding)
Language list management⚠️ (limited)
Template settings⚠️ (limited)
User management (invite/remove users)
Assign roles / change permissions
View audit/access logs⚠️ (view only)⚠️ (view only)⚠️ (view only)
Manage integrations

Notes & common variations

  • Some workspaces allow Schedulers to edit interpreters (basic fields only).
  • Some workspaces restrict Billing from seeing interpreter personal data.
  • Some workspaces enable custom roles or per-user overrides. [Confirm in product]

Best practices

  • Keep exports restricted—exports are the easiest way to leak data accidentally.
  • Grant “edit” permissions only to roles that do that work daily.
  • Use audit logs to review changes after a role update or staff transition.
  • Roles overview
  • Inviting users
  • Removing users
  • Audit/access logs overview