Role-based access control
Role permissions that deny by default: anything not granted stays blocked. When a role changes, the new rule applies in under a minute.
SECURITY
Every AI query goes through a permission and is recorded.
For anyone who has to answer an audit or a data-protection request: who accessed what, when, and with which permission.
CONTROLS
The controls, one by one
Audit trail
Every tool call is recorded with user, role, parameters (with sensitive values removed) and time.
Encryption at rest
Connector credentials encrypted with AES-256. Database encrypted at rest in production.
Federated authentication
OAuth 2.1 with PKCE to connect the assistant. Corporate single sign-on (SSO) is not available yet.
Per-customer isolation
Each customer runs isolated. Access control between customers denies by default and is checked by tests.
Your systems stay where they are
integras runs in the cloud. Your systems stay in your environment and are queried over an encrypted channel, without replicating the database.
Documents with their own permissions
In the knowledge base, each folder has a category with separate read and write permissions. The filter is applied before the search, and the audit records which documents were consulted without storing their text.
LGPD
LGPD
A designated data protection officer (DPO), sub-processors and retention periods listed on the privacy page, and a channel for erasure requests. For technical details, talk to us.
Talk about security