Turqoa Docs

User Management

Turqoa uses role-based access control (RBAC) to manage user permissions. Administrators can create, modify, and deactivate user accounts through the Admin panel or the CLI.

Creating Users

Via Admin Panel

  1. Navigate to Admin > User Management > Create User.
  2. Fill in the required fields:
    • Email (used as the unique identifier)
    • First name and Last name
    • Role (select from available roles)
    • Authentication method (SSO or local)
  3. Click Create. If using local authentication, a password reset link is sent to the user's email.

Via CLI

turqoa admin users create \
  --email operator@terminal.example.com \
  --first-name Jane \
  --last-name Smith \
  --role operator \
  --auth-method sso

Via API

curl -X POST https://turqoa.example.com/api/v1/admin/users \
  -H "Authorization: Bearer ${ADMIN_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "operator@terminal.example.com",
    "first_name": "Jane",
    "last_name": "Smith",
    "role": "operator",
    "auth_method": "sso"
  }'

Role Assignment

Each user is assigned exactly one primary role. Roles determine what the user can see and do in the Command Center and Admin panel.

Available Roles

RoleDescriptionKey Permissions
adminFull system accessUser management, system config, all operational features
operatorGate transaction processingView/review/approve/reject transactions, Command Center access
security_operatorSecurity monitoringSecurity feeds, incident management, drone dispatch
supervisorElevated operatorAll operator permissions + override review + shift management
viewerRead-onlyDashboard viewing, report access, no action capabilities
api_consumerMachine-to-machineAPI access only, no UI access

Changing a User's Role

turqoa admin users update \
  --email operator@terminal.example.com \
  --role supervisor

Role changes take effect immediately. The user's current session is updated without requiring re-login.

Permission Model (RBAC)

Turqoa's RBAC model is structured around resources and actions.

Permission Matrix

Resourceadminsupervisoroperatorsecurity_operatorviewer
Gate transactionsCRUDCRUDRURR
Security incidentsCRUDCRUDRCRUDR
Drone dispatchYesYesNoYesNo
User managementCRUDRNoNoNo
System configurationCRUDRNoNoNo
Audit logsCRUDRRRR
ReportsCRUDCRUDRRR
AI model managementCRUDNoNoNoNo

Legend: C = Create, R = Read, U = Update, D = Delete

Custom Permissions

For deployments requiring granular control beyond standard roles, administrators can create custom permission sets:

custom_roles:
  - name: gate_supervisor
    base_role: operator
    additional_permissions:
      - gate.override.review
      - gate.shift.manage
      - reports.gate.export
    restricted_permissions:
      - security.incidents.manage

Deactivating Users

Deactivated users cannot log in but their records are preserved for audit purposes.

Via Admin Panel

  1. Navigate to Admin > User Management.
  2. Search for the user by name or email.
  3. Click Deactivate. Confirm the action.
  4. The user is immediately logged out of all active sessions.

Via CLI

turqoa admin users deactivate --email former-operator@terminal.example.com

Reactivation

Deactivated users can be reactivated by an administrator:

turqoa admin users activate --email returning-operator@terminal.example.com

Note: Turqoa does not support permanent user deletion. This is by design --- all user records are retained indefinitely for audit trail integrity. Deactivated users do not count against license seat limits.

Audit of User Actions

Every user action is recorded in the audit log with the following attributes:

FieldDescription
timestampUTC timestamp of the action
user_emailEmail of the user who performed the action
user_roleRole at the time of the action
actionThe action performed (e.g., transaction.approve, user.create)
resource_typeThe type of resource acted upon
resource_idThe unique identifier of the resource
detailsAdditional context (e.g., override justification, changed fields)
ip_addressSource IP of the request
session_idThe user's session identifier

Administrators can query user activity from the Audit Logs section or via the API. See Audit Logs for details.