From 763d1c647faf3514f576b0e8250752a606e232f2 Mon Sep 17 00:00:00 2001 From: Matthew Hilton Date: Thu, 8 Jan 2026 10:41:05 +1000 Subject: [PATCH] [docs] access: update meaning of contextlevel --- docs/apis/subsystems/access.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apis/subsystems/access.md b/docs/apis/subsystems/access.md index 28e85e6e54..9173d04e24 100644 --- a/docs/apis/subsystems/access.md +++ b/docs/apis/subsystems/access.md @@ -62,7 +62,7 @@ Where the meaning of array keys is: | --- | --- | | `riskbitmask` | associated risks. These are explained on [Hardening new Roles system](./roles.md). | | `captype` | _read_ or _write_ capability type, for security reasons system prevents all write capabilities for guest account and not-logged-in users | -| `contextlevel` | specified as context level constant. Declares the typical context level where this capability is checked. This capability can be checked with contexts that are at a lower level (e.g. `moodle/site:accessallgroups` could be checked with CONTEXT_MODULE). | +| `contextlevel` | specified as context level constant. Declares the typical context level where this capability is checked. This is used for grouping and does not affect where it can be assigned. | | `archetypes` | specifies defaults for roles with standard archetypes, this is used in installs, upgrades and when resetting roles (it is recommended to use only CAP_ALLOW here). Archetypes are defined in mdl_role table. See also [Role archetypes](https://docs.moodle.org/dev/Role_archetypes). | | `clonepermissionsfrom` | when you are adding a new capability, you can tell Moodle to copy the permissions for each role from the current settings for another capability. This may give better defaults than just using archetypes for administrators who have heavily customised their roles configuration. The full syntax is: `clonepermissionsfrom` => `moodle/quiz:attempt` |