Datasentinel Docs
Visit our websiteBlogRelease Notes
  • 👋Welcome
  • 🆓Free Trial
  • 📣Release Notes
  • Getting started
    • Architecture
    • Installation
      • 🌐Platform
      • 🕶️Agent
    • PostgreSQL clusters
      • 🔌Extensions
        • 🔌pg_stat_statements
        • 🔌pg_store_plans
        • 🔌system_stats
        • 🔌pg_buffercache
      • 🕶️Monitoring User
      • ➕Adding Connection
    • FAQs
      • ❓Platform FAQ
      • ❓Agent FAQ
  • Features
    • Key Features
      • 📊Session History
      • 📊Top Queries
      • 📂Top Tables
      • 🔓Lock Explorer
      • 📈Cluster & System Metrics
      • ⌚Live360
      • 📰Reporting
      • 🔔Alerting
        • Settings
        • Templates
        • Silences
        • Manager
    • Other Features
      • 📡Agentless Monitoring
      • 🛡️Role Based Access
      • 🔂Changed Parameters
    • Tips & Hints
      • 🖥️User Interface
      • 🏷️Tags
      • 🔀Metric Correlation
      • 👁️‍🗨️Consolidated View
      • ❗Graphical Annotations
      • ☁️Predefined Providers
      • ❓Wait Event Description
      • ®️Read Replicas
      • 👁️‍🗨️Agentless & System Metrics
      • ☑️Simplified pg_instance Display
  • implementation
    • Platform Usage
      • ⚙️Configuration
        • 🔑License
        • 📓LDAP
        • ✉️SMTP
        • 📋Audit
        • 👨‍🏭Users & Roles
      • 🧩API
        • 🔗Access Token
        • 🧩Connection API
        • 🧩Role API
        • 🧩User API
        • 🧩Reporting API
        • 🧩Workload API
        • 🧩Alerting API
      • 🛠️Tooling
    • Agent Usage
      • 📣Release Notes
      • ⌨️CLI
      • 🧩API
      • 🗃️Collection Level
      • 🔬Internals
    • Upgrade
      • 🔄Platform
      • 🔄Agent
    • Troubleshooting
      • 🩺Error message: “502 Bad Gateway”
      • 🩺The UI is not displaying any metrics for my new instance.
      • 🩺UI dashboard is encountering loading errors
      • 🩺InfluxDB
  • Support
    • How to Contact Us
  • GitHub Toolkit
Powered by GitBook
On this page
  • How it Works
  • Blog Post
  • Create Role
  • Through API
  • Through UI
  • FAQ
  1. Features
  2. Other Features

Role Based Access

Datasentinel offers Role-Based Access Control, enabling precise restriction of designated users to specific perimeters among the total instances available.

PreviousAgentless MonitoringNextChanged Parameters

Last updated 1 year ago

This functionality grants users access to a restricted scope of PostgreSQL instances, offering enhanced control over platform security.

How it Works

  1. Utilize pre-existing tags or link novel tags to your PostgreSQL clusters. Refer to for more details.

  2. Establish a role featuring conditions based on one or more tags.

  3. Allocate the created role to a designated user.

Blog Post

Create Role

Role management can be performed both through the platform’s interface and its available API

You can associate multiple tags to the same role and combine AND/OR conditions

Through API

Through UI

FAQ

Can a user be assigned multiple roles?

No, a user can only be assigned one role in Datasentinel

What is the finest level of granularity for access control in Datasentinel?

The finest granularity for access control in Datasentinel is at the level of the PostgreSQL instance name

Can a role have multiple conditions based on the same tag?

Yes, a role in Datasentinel can indeed have several conditions based on the same tag.

Let's say you have a team member who needs access to two specific applications within your PostgreSQL environment – for instance, a crm and a sales application.

In Datasentinel, you can easily create a role that encompasses access to both these applications by setting up multiple conditions on the same tag.

In this example, you can define a role with the following conditions:

application=crm OR application=sales.

🛡️
🧩Role API
Tags section
LogoFind out how to secure, manage and automate access to Datasentinel platform