Key Security Features
RBAC
Control who can access and modify your resources
Secrets Management
Securely store and inject sensitive data
Doppler Integration
Universal secrets manager integration
Audit Logs
Track all changes to your organization
Role-Based Access Control (RBAC)
Qovery implements a role-based access control system to manage member permissions across your organization, clusters, projects, and environments.Default Roles
Qovery provides 5 default roles with predefined permissions:| Action | Owner | Admin | DevOps | Billing Manager | Viewer |
|---|---|---|---|---|---|
| Read organization | yes | yes | yes | yes | yes |
| Edit organization | yes | yes | no | no | no |
| Delete organization | yes | no | no | no | no |
| Manage billing | yes | yes | no | yes | no |
| Manage members & roles | yes | yes | no | no | no |
| Manage cluster & container registry | yes | yes | yes | no | no |
| Manage organization setup | yes | yes | yes | no | no |
| Read ANY project | yes | yes | yes | no | yes |
| Edit/Delete ANY project | yes | yes | no | no | no |
| Create project | yes | yes | no | no | no |
| Read ANY environment | yes | yes | yes | no | yes |
| Edit/Delete ANY environment or service | yes | yes | no | no | no |
| Create environment or service | yes | yes | no | no | no |
| Add/Edit/Delete environment variables and secrets | yes | yes | yes | no | no |
| Deploy/Stop ANY environment or service | yes | yes | yes | no | no |
| Connect via shell to ANY application | yes | yes | yes | no | no |
| View audit logs | yes | yes | no | no | no |
| Manage API tokens | yes | yes | no | no | no |
Only one Owner per organization is allowed.
Custom Roles
Create tailored roles when default options are insufficient. Cluster-Level Access:- Read-Only: View cluster information
- Create Environment: Deploy new environments on specific clusters
- Full Access: Manage cluster settings and create environments
- No Access: Cannot see the project
- Read-Only: View without modification
- Deploy: Handle deployments and logs, manage variables
- Manage: Modify deployments and environment structure
- Full Access: Complete project administration
Users with custom roles cannot create clusters or manage organization-wide settings like webhooks or API tokens.
- Go to Organization Settings → Members
- Click Invite Member or edit existing member
- Select role (default or custom)
- Configure project/environment access if using custom role
- Send invitation
Secrets Management
Qovery provides secure environment variable and secrets management for your applications.Variable Types
Classic Variables: Standard key-value pairs accessible at build time and runtime. Secrets: Encrypted variables with values inaccessible through API or UI. Values are only available to applications during execution. File-Based Variables: Variables stored as files at a specified path. Your application accesses the file location via the variable name.Variable Scopes
Variables operate at three hierarchical levels:- Project: Shared across all environments and applications within the project
- Environment: Shared across all applications within one environment
- Application: Available to a single application only
Built-in Variables
Qovery automatically generates variables following the patternQOVERY_<SERVICE_TYPE>_<SERVICE_ID>_<SPEC>, enabling easy service interconnection.
Examples:
Creating Secrets
- Console
- Terraform
- Navigate to your Application → Variables
- Click Add Variable
- Enter variable key
- Select Secret type
- Enter secret value
- Choose scope (Application, Environment, or Project)
- Click Save
Secret values are encrypted and cannot be viewed after creation. Only the first and last 3 characters are shown.
Doppler Integration
Doppler is a universal secrets manager that integrates with Qovery, allowing you to store and manage your application secrets in a single place and access them from anywhere.What is Doppler?
Doppler provides:- Centralized secrets management
- Team collaboration on secrets
- Secret versioning and rollback
- Automatic secret rotation
- Compliance and audit trails
Setup Doppler Integration
To integrate Qovery with Doppler, follow the official Doppler documentation:Doppler Integration Guide
Complete setup instructions for connecting Qovery with Doppler
Benefits
- Centralized Management: Manage all secrets in one place
- Team Collaboration: Share secrets securely with team members
- Automatic Sync: Secrets automatically sync to Qovery
- Audit Trail: Track who accessed and modified secrets
- Secret Rotation: Easily rotate secrets across all environments
Audit Logs
Qovery’s audit logs enable organizations to track all actions and changes within their system.What Gets Tracked
Qovery monitors all API calls for your organization, including:- Application deployments
- Configuration changes
- Environment modifications
- Cluster updates
- User management actions
- RBAC changes
- Secret modifications
- API token usage
Event Details
Each logged event includes:- Timestamp: When the action occurred
- Event Type: CREATE, UPDATE, DELETE, TRIGGER_DEPLOYMENT, etc.
- Target Type: Environment, Cluster, Role, Application, Database, etc.
- Target: The specific object modified
- Change: High-level description of what was modified
- User: Who made the change (or API token name if via API)
- Tool: How the change was made (Console, Terraform, CLI, Git push)
Accessing Audit Logs
- Navigate to Organization Settings
- Click Audit Logs in the left sidebar
- View the list of all events
- Use filters to narrow down results:
- Time range
- Target type
- Target name
- Event type
- Click on an event to see full details including JSON response
Use Cases
- Security Monitoring: Track unauthorized access attempts
- Compliance: Maintain records for audits (SOC 2, GDPR, etc.)
- Troubleshooting: Identify what changed before an incident
- Team Accountability: Track who made specific changes
- Change Management: Review all infrastructure modifications
Retention
Audit logs retention period depends on your Qovery plan. Export logs regularly if you need longer retention for compliance purposes.Best Practices
Principle of Least Privilege
Grant minimum required permissions to users and services
Use Secrets for Sensitive Data
Never use plain variables for passwords, API keys, or tokens
Rotate Secrets Regularly
Change credentials and API keys quarterly or after team changes
Review Access Quarterly
Audit user permissions and remove inactive users
Monitor Audit Logs
Regularly review audit logs for suspicious activities
Use Custom Roles
Create project-specific roles for better access control