Skip to main content

​
Security model

Trevi is organized around your account. Access is enforced at the account and resource level. Users inherit permissions through their role.

​
Credential handling

Credentials and connection data are stored encrypted at rest. Secrets are never returned in plaintext after creation.

​
Token safety

Use short-lived access tokens where possible. Do not store client secrets in browsers or client-side apps.

​
Auditability

Audit logs track important actions and help you trace configuration changes.

​
Best practices

Use least privilege. Keep tool lists small and scoped. Revoke connections when no longer needed.