Skip to content
Fetching contributors…
Cannot retrieve contributors at this time
88 lines (72 sloc) 3.36 KB
<p align="center"><b>Permissions</b></p>
<p>
Permissions are the settings that you grant for specific capabilities.
</p>
<p>
For example, one capability is "Start new discussions" (in forums).
</p>
<p>
In each role, you can choose to set the permission for such a capability
to one of four values:
<dl>
<dt>INHERIT</dt>
<dd>This is the default setting, generally. It's a neutral setting that
means "use whatever setting the user already had". If a role
gets assigned to someone (eg in a course) that has this permission for
a capability, then the actual permission they'll have will just be
the same as they already had at higher-level contexts (eg categories
or site level). Ultimately, if permission is never allowed at any
level, then the user will have no permission for that capability.
</dd>
<dt>ALLOW</dt>
<dd>By choosing this you are granting permission for this capability
to people who are assigned this role. This permission applies
for the context that this role gets assigned plus all "lower"
contexts. For example, if this role is a student role assigned
to a course, then students will be able to "start new discussions"
in all forums in that course, UNLESS some forum contains an
override or a new assignment with a Prevent or Prohibit value
for this capability.</dd>
<dt>PREVENT</dt>
<dd>By choosing this you are removing permission for this capability,
even if the users with this role were allowed that permission in
a higher context.</dd>
<dt>PROHIBIT</dt>
<dd>This is rarely needed, but occasionally you might want to completely
deny permissions to a role in a way that can NOT be overridden at
any lower context. A good example of when you might need this is
when an admin wants to prohibit one person from starting new
discussions in any forum on the whole site. In this case they
can create a role with that capability set to "Prohibit" and then
assign it to that user in the site context.
</dd>
</dl>
</p>
<p align="center"><b>Conflict resolution of permissions</b></p>
<p> Permissions at a "lower" context will generally override
anything at a "higher" context (this applies to overrides
and assigned roles). The exception is PROHIBIT which can not
be overridden at lower levels.
</p>
<p> If two roles are assigned to a person in the same context, one with
ALLOW and one with PREVENT, which one wins? In this case, Moodle will
look up the context tree for a "decider". </p>
<p> For example, a student has two roles in a course, one that allows
them to start new discussions, one that prevents them. In this case,
we check the categories and the site contexts, looking for another
defined permission to help us decide. If we don't find one, then
permission is PREVENT by default (because the two settings cancelled
each other out, and thus you have no permission).
</p>
<p align="center"><b>Special exceptions</b></p>
<p> Note that the guest user account will generally be prevented from
posting content (eg forums, calendar entries, blogs) even if it
is given the capability to do so.
</p>
<p>
See also
<a href="help.php?file=roles.html">Roles</a>,
<a href="help.php?file=contexts.html">Contexts</a>,
<a href="help.php?file=assignroles.html">Assign Roles</a> and
<a href="help.php?file=overrides.html">Overrides</a>.
</p>
Something went wrong with that request. Please try again.