NelliaOS brings access policy, approval and operating evidence into the workflow itself. Security responsibilities remain explicit across the platform, integrations and deployment.
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.
Roles define the starting permissions. Account, queue and resource scope narrow access further. Sending follows the approved outbound policy; approval remains a separate action.
Organization policy and explicitly granted resources
| Read | |
|---|---|
| Prepare | |
| Approve | |
| Send | |
| Administer |
Owns the organization policy. Actions still follow resource scope, outbound rules and required separation of duties.
Inside NelliaOS
Explore an interactive product walkthrough. Choose a conversation, guide an agent through review or turn a customer signal into a useful next action.
Prepare a response to the site request and assign the next operating step.
The agent reads the request and the relevant operating sources within the assigned account boundary.
The site request and current task owner
The handoff and exception procedure
Assigned account scope and review rule
Organization membership and resource boundaries determine access before a workflow reaches a tool or connected account.
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.
Explore in practiceRole permissions combine with account, queue and record access. Reading, preparing, approving, sending and administering are distinct permissions, evaluated against the current identity and resource.
Explore in practiceTenant 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.
Explore in practiceAI execution and human decisions leave an operating record that the responsible team can review.
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.
Explore in practiceModel 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.
Explore in practiceOperational logs support investigation and service ownership. Incident procedures, backup responsibilities and recovery exercises form part of the deployment's operating plan.
Explore in practiceThe governance guide maps identity, data, AI execution and operational responsibility into questions your security and platform teams can use in an architecture review.
Discuss your operation