mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-12 19:02:12 +00:00
doc: fix a link on the RBAC page
This commit fixes an external link on the Role Based Access Control page.
Fixes https://github.com/scylladb/scylladb/issues/20166
(cherry picked from commit c56c3ce469)
Closes scylladb/scylladb#20203
This commit is contained in:
committed by
Botond Dénes
parent
cdae15ced9
commit
b127b492cf
@@ -22,7 +22,7 @@ In the same manner, should someone leave the organization, all you would have to
|
||||
Should someone change positions at the company, just assign the new employee to the new role and revoke roles no longer required for the new position.
|
||||
|
||||
To build an RBAC environment, you need to create the roles and their associated permissions and then assign or grant the roles to the individual users. Roles inherit the permissions of any other roles that they are granted. The hierarchy of roles can be either simple or extremely complex. This gives great flexibility to database administrators, where they can create specific permission conditions without incurring a huge administrative burden.
|
||||
In addition to standard roles, `ScyllaDB Enterprise <https://enterprise.docs.scylladb.com/>`_ users can implement `Workload Prioritization <https://enterprise.docs.scylladb.com/stable/using-scylla/workload-prioritization.html>`, which allows you to attach roles to Service Levels, thus granting resources to roles as the role demands.
|
||||
In addition to standard roles, `ScyllaDB Enterprise <https://enterprise.docs.scylladb.com/>`_ users can implement `Workload Prioritization <https://enterprise.docs.scylladb.com/stable/using-scylla/workload-prioritization.html>`_, which allows you to attach roles to Service Levels, thus granting resources to roles as the role demands.
|
||||
|
||||
.. _rbac-usecase-grant-roles-and-permissions:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user