Back to Documentation

Role-Based Access Control

Granular permission management and access control for your database infrastructure

Overview

DB24x7's Role-Based Access Control (RBAC) system provides fine-grained control over who can access what resources and perform which actions. This ensures that users have the minimum necessary permissions to perform their tasks, following the principle of least privilege.

Hierarchical Roles

Pre-defined and custom role hierarchy

Granular Permissions

Control access at resource level

Team Management

Organize users into teams with shared access

Pre-defined Roles

DB24x7 comes with three built-in roles that cover most common use cases. These roles cannot be deleted but can be used as templates for custom roles.

Administrator

Full system access and control

Permissions

Create, read, update, delete all resources
Manage users and roles
Configure organization settings
Access billing and subscription
View and export audit logs
Manage integrations and API keys

Use with caution: This role has unrestricted access. Assign only to trusted users who need full control.

Analyst

Query and analyze data with limited modifications

Permissions

Read access to all databases
Execute queries and analyze data
Create and modify dashboards
Configure alerts and notifications
Export data and reports
View performance metrics

Restrictions

Cannot modify database schemas
Cannot manage users or roles
Cannot access billing settings
Limited write operations on production DBs

Viewer

Read-only access for monitoring and reporting

Permissions

View database metadata and schemas
View existing dashboards
View performance metrics
View alerts (cannot configure)
Export read-only reports
View logs (no sensitive data)

Restrictions

No query execution permissions
Cannot create or modify resources
Cannot access sensitive data fields
No administrative privileges

Custom Role Creation

Create custom roles tailored to your organization's specific needs. Custom roles allow you to combine permissions in ways that match your team structure and workflows.

Enterprise Feature

Custom role creation is available on Enterprise plans. Contact sales to upgrade your plan.

Creating a Custom Role

  1. Navigate to Settings Organization Roles & Permissions
  2. Click "Create Custom Role"
  3. Provide a name and description for the role
  4. Select base role to inherit permissions (optional)
  5. Configure specific permissions using the permission builder
  6. Set database-level access controls
  7. Review and save the custom role

Permission Categories

Database Operations

  • • Connect to databases
  • • Execute SELECT queries
  • • Execute INSERT/UPDATE/DELETE queries
  • • Modify schema (DDL operations)
  • • Manage indexes and constraints

Monitoring & Analytics

  • • View performance metrics
  • • Create and edit dashboards
  • • Configure alerts
  • • Access query analytics
  • • Export reports

Administrative

  • • Manage users and teams
  • • Configure roles and permissions
  • • Access audit logs
  • • Manage integrations
  • • Billing and subscription settings

API & Automation

  • • Generate API keys
  • • Configure webhooks
  • • Manage scheduled tasks
  • • Access API endpoints
  • • Execute automation scripts

Permission Levels

Permissions in DB24x7 operate on a granular level, allowing precise control over user capabilities.

None

No access to the resource or action. Users cannot view or interact with this resource.

Read

View-only access. Users can see the resource but cannot make any modifications. Ideal for monitoring and reporting roles.

Write

Create and modify resources. Includes read permissions. Cannot delete resources or change critical settings.

Admin

Full control over the resource including create, read, update, delete, and configuration changes. Use sparingly.

Database-Level Access Control

Control access to specific databases, schemas, or even individual tables. This allows you to restrict sensitive data while providing broader access to other resources.

Access Control Hierarchy

1

Organization Level

Global permissions that apply across all databases in the organization.

2

Database Instance Level

Permissions specific to a database instance. Overrides organization-level defaults.

3

Schema Level

Control access to specific schemas within a database. Useful for multi-tenant setups.

4

Table Level (Enterprise)

Fine-grained control over individual tables. Restrict access to sensitive tables.

Configuring Database Access

  1. Navigate to the database in your database list
  2. Click Settings Access Control
  3. Add users or roles to the access list
  4. Set permission level for each user/role (None, Read, Write, Admin)
  5. Save changes

Team Management

Organize users into teams for simplified permission management. Teams inherit role-based permissions and can have additional database-specific access.

Creating Teams

  1. Go to Settings Organization Teams
  2. Click "Create Team"
  3. Enter team name and description
  4. Assign a default role for team members
  5. Add members to the team
  6. Configure team-specific database access

Team Benefits

Simplified Management

Grant access to multiple users at once by adding them to a team

Consistency

Ensure all team members have consistent permissions and access

Onboarding

Quickly onboard new members by adding them to appropriate teams

Audit Trail

Track changes at the team level for better compliance

Permission Precedence

When a user is assigned both individual permissions and team permissions, the more permissive access level takes precedence. For example, if a user has Read access individually but their team has Write access, the user gets Write access.

Best Practices

1. Principle of Least Privilege

Grant users the minimum permissions necessary to perform their job functions. Start with restrictive permissions and add more as needed.

2. Regular Access Reviews

Periodically review user permissions and team memberships. Remove access for users who have changed roles or left the organization.

3. Use Teams for Groups

Leverage teams instead of managing individual user permissions when multiple users need the same access. This simplifies management and reduces errors.

4. Separate Production Access

Restrict write access to production databases. Consider requiring approval workflows for production changes.

5. Document Custom Roles

Maintain clear documentation of custom roles and their intended use cases. This helps with onboarding and troubleshooting.

Related Documentation