Commit b60d4a41 authored by mbenguig's avatar mbenguig
Browse files

Update citizen-ds and expert-ds groups descriptions

parent 7b15b0f1
......@@ -1224,8 +1224,8 @@ The following groups are defined by default in the `security.java.policy-server`
* `rmcoreadmins` : this group gives full interaction capability with the resource manager (create, edit, remove Node Sources, add nodes, etc)
* `admin` : this group gives full permission on every aspect, this group is [.underline]#deprecated# and is kept for backward compatibility purpose only (use the above `scheduleradmins` and `rmcoreadmins` instead).
* `watchers` : this group allows to receive notification events from the scheduler and resource manager, but cannot perform any action. It is mostly used internally.
* `citizen-ds` : this group gives enough permissions for moderate data analysis tasks.
* `expert-ds` : this group gives permissions to cover all data scientist activities.
* `citizen-ds` : this group gives enough permissions for moderate data analysis tasks (studio, catalog-portal, workflow-execution, job-analytics).
* `expert-ds` : this group gives permissions to cover all data scientist activities (studio, scheduler, catalog-portal, workflow-execution, service-automation, job-analytics, job-gantt, job-planner-calendar-def, job-planner-calendar-def-workflows, job-planner-execution-planning, job-planner-gantt-chart, notification-portal).
== Deploy ProActive Nodes
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment