doc/html/user_permissions.shtml

<!--#include virtual="header.txt"-->

<h1>User Permissions</h1>

<p>Slurm supports several special user permissions as described below.</p>

<h2 id="operator">Operator<a class="slurm_link" href="#operator"></a></h2>

<p>These users can add, modify, and remove any database object
(user, account, etc), and add other operators.
On a SlurmDBD served cluster, these users can
<ul>
<li>View information that is blocked to regular uses by a PrivateData flag</li>
<li>Create/Alter/Delete Reservations</li>
</ul>

<p>Set using an <b>AdminLevel</b> option in the user's database record.
For configuration information, see
<a href="accounting.html">Accounting and Resource Limits</a>.</p>

<h2 id="admin">Admin<a class="slurm_link" href="#admin"></a></h2>

<p>These users have the same level of privileges as an operator in the database.
They can also alter anything on a served slurmctld as if they were the SlurmUser
or root.</p>

<p>An <b>AdminLevel</b> option in the user's database record.
For configuration information, see
<a href="accounting.html">Accounting and Resource Limits</a>.</p>

<h2 id="coord">Coordinator<a class="slurm_link" href="#coord"></a></h2>

<p>A special privileged user, usually an account manager, that can add
users or sub-accounts to the account they are coordinator over.
This should be a trusted person since they can change limits on account and
user associations, as well as cancel, requeue or reassign accounts of jobs
inside their realm. Note that a coordinator may not increase job limits above
the parent ones.</p>

<p>Set using a table in Slurm's database defining users and accounts for
which they can serve as coordinators.
For configuration information, see the
<a href="sacctmgr.html">sacctmgr</a> man page.</p>

<!--#include virtual="footer.txt"-->