Control & govern
Decide who may do what, what agents may do on their own, where data may go and how it is protected.
Governance in Liyagent is enforced on the server, on every request. Roles say what a person may do in the console. Cedar policies say what any principal, person or agent, may do to any resource. Tenants keep customers or business units apart. Redaction and sensitivity labels keep data out of places it shouldn't reach. The audit log records all of it.
In this section
- Access
Manage users, roles, role bindings and Cedar policies, start from policy templates, and review access regularly.
- Agent permissions
See who may act on an agent and what the agent itself may do, and check a single decision before you rely on it.
- Data handling
Where Liyagent keeps data, how it is encrypted, how long it stays and how it leaves.
- Redaction
Keep personal data away from models with reversible tokens, and keep sensitive knowledge away from channels with sensitivity labels.
- Tenancy
Run several customers or business units on one instance with server-enforced separation, per-tenant settings and optional per-tenant keys.
- Identity and roles
How people, agents and clients sign in, how SSO and SCIM connect your directory, and how identities map to roles.
- GDPR and data protection
Who is controller and who is processor, how to answer a data-subject request with the console's tools, and the retention, residency, masking and audit evidence a DPIA asks for.