# Control follows every identity and action.

NelliaOS brings access policy, approval and operating evidence into the workflow itself. Security responsibilities remain explicit across the platform, integrations and deployment.

## Define who can work with each resource.

Organization membership and resource boundaries determine access before a workflow reaches a tool or connected account.

### Managed identities

SSO, MFA and SCIM connect the platform to the organization's identity lifecycle. Human and agent identities have distinct credentials, delegated scope and revocation paths.

### Roles and resource scope

Role permissions combine with account, queue and record access. Reading, preparing, approving, sending and administering are distinct permissions, evaluated against the current identity and resource.

### Data boundaries and encryption

Tenant separation extends to storage, retrieval and integration credentials. Encryption in transit and at rest supports the selected deployment, with defined key ownership and data-location responsibilities.

## Make the path to an outcome inspectable.

AI execution and human decisions leave an operating record that the responsible team can review.

### Approval and decision history

Policy identifies the actions that require review and the people authorized to approve them. The record connects the proposal, decision, execution and result, including refusals and failed attempts.

### Model and tool controls

Model routing follows the task and its data policy. Evaluations support capability releases, while tool scope and usage budgets constrain the work an agent can perform.

### Auditability and recovery

Operational logs support investigation and service ownership. Incident procedures, backup responsibilities and recovery exercises form part of the deployment's operating plan.


## Authority follows the work

Roles define the starting permissions. Account, queue and resource scope narrow access further. Sending follows the approved outbound policy; approval remains a separate action.

### Owner

Organization policy and explicitly granted resources

- Read: Allowed within scope

- Prepare: Allowed within scope

- Approve: Allowed within scope

- Send: Allowed within scope

- Administer: Allowed within scope

Owns the organization policy. Actions still follow resource scope, outbound rules and required separation of duties.

### Administrator

Granted organization, account and configuration scope

- Read: Allowed within scope

- Prepare: Allowed within scope

- Approve: Allowed within scope

- Send: Allowed within scope

- Administer: Allowed within scope

Manages the assigned configuration boundary. Approval authority and sending remain subject to the organization's policy.

### Supervisor

Assigned teams, accounts and queues

- Read: Allowed within scope

- Prepare: Allowed within scope

- Approve: Allowed within scope

- Send: Allowed within scope

- Administer: Restricted

Reviews and coordinates assigned work. Approval is limited to the actions and resources delegated to the supervisor.

### Agent

Assigned conversations, tasks and accessible records

- Read: Allowed within scope

- Prepare: Allowed within scope

- Approve: Restricted

- Send: Allowed within scope

- Administer: Restricted

Prepares and handles assigned work. Sending follows approved outbound policy; restricted actions require an authorized reviewer.

### Auditor

Explicitly granted evidence and review resources

- Read: Allowed within scope

- Prepare: Restricted

- Approve: Restricted

- Send: Restricted

- Administer: Restricted

Inspects permitted records and decision history with read-only access. Export is a separate scoped permission.

Nellia
https://nellia.co/en/