← Back to homeTrust and control

Give every AI teammate a role, an owner and visible limits.

The Command Centre brings approvals, workspace roles, connections, model choice, network rules and activity into one place so your team can see and govern the work.

Workspace data path

Review the region and services used by your workflow.

UseGlic operates its workspace in the EU region by default. Set your organisation's data region — Europe, United States or Asia Pacific — in workspace settings. Enterprise and white-label deployments can pin a specific region. We review the data path for each workflow before go-live. Where model inference and connected services process data depends on the regions and settings selected for your workspace, and some model routing can cross regions. See the current subprocessor list.

Role-based access control

The right people make the right changes.

Member

Request and use

Colleagues can request work and use AI teammates they are authorised to reach.

Reader

Inspect

Read-only roles can view permitted workspace records without changing sensitive settings.

Admin

Manage

Workspace admins handle agent setup and operational review within their tenant.

Super admin

Control access

Super admins can change sensitive settings, including an agent's network rules.

API operations also check tenant scope and the permissions required for that action. Connector credentials, knowledge access and agent behaviour have their own controls.

Each role's boundaries

Access follows the job.

Approved connectionsChoose the systems an AI teammate needs and govern who can use each one.
Human approvalsKeep a named person in decisions that need review before action.
Model and spend limitsChoose a model for the work, then watch usage and estimated cost.
Domain rulesA super admin can add allowed or blocked domain rules for an agent in the network firewall.
Current Command Centre network behaviour allows domains unless they are explicitly blocked. Domain rules should be reviewed as part of setup. A default-deny allowlist is a separate security configuration and is not claimed for this control.
Know what happened

Visible work and accountability.

Use activity records, approval history and model usage to understand an outcome. Pause or adjust an AI teammate when the work changes. We are also building governed employee and agent knowledge with source permissions carried into answers.

Explore knowledge ↗

Review your first workflow

Tell us which systems, people and data are involved, and we will map the access boundaries with you.

Talk to us ↗