Recent changes
Wednesday November 04 2026
-
Rotate and prune logs Updated Markdown page
Step by step - see each log's archives and limits, rotate logs now, prune archives beyond the limits, compress them, and schedule it with the logs cronjob part, always with a dry run first.
-
Run a cronjob part by hand Updated Markdown page
Step by step - run one cronjob part or one script now, from Setup > Cronjobs with live output or from the shell, for example to publish approved content at once or after a restore.
-
Set up environment-specific settings Updated Markdown page
Step by step - name each machine's environment with EXP_ENV in config.env.php and keep the settings that differ (mail transport, debug output, the admin badge) in variant files, so a test copy never mails citizens and…
-
Sign out all sessions of a user Updated Markdown page
Step by step - end every browser session of one account (a lost laptop, a suspected compromise, a leaver), by disabling the account, changing its password, or removing its sessions on Setup > Sessions with the database…
-
Switch Velocity to Let's Encrypt Updated Markdown page
Step by step - move an Exponential Velocity site from a manually installed certificate to automatic Let's Encrypt certificates, trying the staging directory first, after checking your organization's certificate policy.
-
Take a backup before a change Updated Markdown page
Step by step - take a consistent backup of database and files right before a change, inside the maintenance window, with the right tool for your database engine, and check that the files are complete.
-
Take the site into maintenance for an upgrade Updated Markdown page
Step by step - switch a public website into maintenance mode for a planned upgrade with a clear message for citizens, an expected end, access for testers and the administration, and check that visitors get the 503 page.
-
Verify the audit trail Updated Markdown page
Step by step - check that the audit trail is complete and unchanged with exp:audit status and verify (live files and archives), or Verify now in the Audit tab, and what to do with the result.
-
Warm the caches after a deploy Updated Markdown page
Step by step - after a deploy or cache clear, request the important pages yourself (preload.php, warm.php or the Preload Sites view) so the first citizens do not wait for pages to be rendered.
-
People and permissions tasks Updated Markdown page
Index of step-by-step tasks for staff access on a public-sector Exponential site - roles for departments, approvers, auditors and contractors, joiners and leavers, passwords and two-step sign-in, sections, states and…
-
Add a new staff member Updated Markdown page
Step by step - create the account of a new member of staff in their department's user group, give them a first password safely, ask for two-step sign-in, and check their access.
-
Assign a role with a section limitation Updated Markdown page
Step by step - give a user group an existing role only for the content of one section (for example an internal or restricted section), with Assign with limitation, and check the result.
-
Assign a role with a subtree limitation Updated Markdown page
Step by step - give a user group an existing role only below one folder of the content tree, with Assign with limitation and Subtree, and check that the boundary holds.
-
Audit who has admin rights Updated Markdown page
Step by step - list every account with full access or the right to change roles, using the role list badges, the role pages, Check user accounts and the audit trail, and record the result for an access review.
-
Check what a role allows Updated Markdown page
Step by step - read a role's page to see every policy as a sentence, who it reaches and with which limitations, spot dangerous badges and dead limitations, and test it with a test account.
-
Close open registration Updated Markdown page
Step by step - stop visitors from creating accounts on a public-sector site where nobody should self-register, on a new installation (no policy) and on an upgraded one (PolicyOmitListExclude), and clean up unactivated…
-
Copy a role for a new department Updated Markdown page
Step by step - decide whether a new department needs a copy of a role or only a new limited assignment of the same role, and make the copy safely when its policies really differ.
-
Create a department editor role for a subtree Updated Markdown page
Step by step - create one "Department editor" role and assign it to a department's user group so its editors can create, edit and publish only below the department's own folder.
-
Create a section for restricted content Updated Markdown page
Step by step - create a section such as "Internal", put existing content into it with Assign content, and give only the right staff read access, so visitors never see it.
-
Create a user group for a department Updated Markdown page
Step by step - create a user group for a department or team in the Users tree, give it its roles with limitations, and add members, so access is managed per group instead of per person.