Role Based Access

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

This feature allows administrators to restrict user access to a defined subset of PostgreSQL instances, providing precise and secure control over platform visibility.

How Roles Work

1

Define Instance tags

Ensure that your PostgreSQL clusters are tagged using existing tags or newly defined ones.

2

Create a role

Create a role by defining one or more tag-based conditions. These conditions determine which PostgreSQL clusters are included in the role’s access scope.

3

Assign the role to a user

Assign the role to one or more users. Once associated, users can access only the PostgreSQL clusters included in the role’s scope.

Access is updated dynamically as instance tags change or new instances are added.

Create a Role

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

Through API

Role

Through UI

Guide

Manage Users and Role-Based Access

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.