Access reviews
This page is for owners and managers who must confirm, at least once a year, that only the right people can reach the right parts of the site, and for the administrator who prepares the review. An access review catches the editor who left last spring, the temporary administrator who was never downgraded, and the role that quietly grew.
Note
Basics, not legal advice. Some regulations and contracts require access reviews at set intervals; follow them where they apply.
Contents
- How access works in Exponential
- Before the review
- Step by step
- Sensitive permissions to look at first
- Between reviews
- A review record to keep
How access works in Exponential
- A role is a set of policies; each policy allows one module or function, possibly limited to sections, classes, subtrees, languages or siteaccesses.
- A role does nothing until it is assigned to users or user groups. A user has every policy of every role assigned to them or to their groups.
- A role with a policy over every module is full access, marked red in the role list; a policy over the role module lets its users give themselves any access, marked amber.
Source: Roles and policies. PreventPrivilegeEscalation is enabled
by default (settings/site.ini), so nobody can grant more than they hold
(Accessibility, security and compliance checklists).
Before the review
- To do: Get a current list of staff, contractors and partners from HR or the contract owner.
- To do: Agree who signs the review (the site owner) and who prepares it (an administrator).
- To do: Note the date of the last review; the audit trail can show what changed since then.
Step by step
- List the roles. Open Users > Roles. Note every role marked red (full access) or amber (can change roles). For each, ask: does this role still need that?
- Read each role. Open it and read its policies. Remove policies nobody needs; prefer limits to sections or subtrees over whole modules (Roles and policies).
- Check the assignments. For each role, list the users and groups it is assigned to. Compare with the staff list. Pay most attention to administrators.
- Find unused accounts. Open Users > Check user accounts and use the filters Never signed in and Not seen for N days (180 by default) (Check user accounts).
- Find shared and broken accounts. Use the filters Shared login, Shared e-mail address and Orphaned.
- Act. Disable accounts that are not needed (the page asks for confirmation and shows the count). Removing a user object is final, so disable first; the optional Deactivate and move setting gathers disabled accounts in one hidden group without roles.
- Check two-step sign-in for administrators and editors, if your policy requires it (User accounts and passwords).
- Look at the record. In the audit trail, filter the
accesschannel for role assignments since the last review and confirm each was intended (Compliance evidence from the audit trail). - Export the evidence. Export the account list as CSV from Check user accounts, and the audit filter as CSV.
- Sign the record below and set the next review date.
Sensitive permissions to look at first
| Permission | Why it matters | Source |
|---|---|---|
| Any role with full access | can do everything | Roles and policies |
role module | can grant itself any access | same |
infocollector/read | reads every form submission | Collected information |
mailpreferences/export | exports people's mail data | Compliance and GDPR |
audit/read, audit/manage | reads or manages the audit trail; only Administrator holds them on a new installation | The audit trail |
user/register | who may register at all | Roles and policies |
| OAuth client authorization | who may connect apps | Roles and policies |
| Shop administration | sees customers and orders | Store dashboard |
Seeing e-mail addresses in Check user accounts itself needs the right role/assign
(Check user accounts).
Between reviews
- Disable accounts on a person's last working day; do not wait for the yearly review.
- Let the audit trail's alert rules watch for an administrator role being granted; check who receives the alert mail
with
./console exp:audit alerts recipients(The audit trail). - Give temporary access an end date in your notes, and remove it on that date.
- For extranets with partner accounts, see Extranet permissions review.
A review record to keep
ACCESS REVIEW RECORD
Site: ____________________ Review date: __________ Previous review: __________
Prepared by: ______________ Approved by (site owner): ______________
Roles with full access: ______________________ Still needed? yes / no Action: ________
Roles that can change roles: _________________ Still needed? yes / no Action: ________
Administrators (named): ______________________ All current staff? yes / no
Accounts never signed in: ___ disabled: ___
Accounts not seen for 180 days: ___ disabled: ___
Shared logins or e-mail addresses: ___ resolved: ___
Two-step sign-in on for all administrators? yes / no
Role assignments since last review checked in the audit trail? yes / no
Evidence files (CSV exports) stored at: ______________________
Next review date: __________
Signature: ______________Related pages
- Security basics for businesses
- Restricting the administration
- Departments, roles and sections
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.