- Create a user group for a department 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.
- Customer accounts Looking after the customers of an Exponential store - guest and account checkout as configured, the customer list, account questions from customers, tidying old accounts, and who on the team may see customer data.
- FAQ: forms and newsletters Answers to the questions public bodies ask about forms and newsletters in Exponential - contact and feedback forms, where submissions go, spam protection, consent, newsletter subscriptions with double opt-in…
- Find an error by its reference Step by step - when a citizen or colleague reports an error page with a reference such as ERR-0123456789, find the log line and all lines of that request in the log viewer or with exp:logs, and hand it to developers.
- HTTPS and HSTS For public bodies serving their site only over HTTPS - the steps Exponential's installation guide gives (HTTPS on every name, redirects, Secure cookies, HSTS raised gradually, certificate monitoring), the settings for…
- Link from one department site to another Task for administrators: make links from one site to content of another site in the same installation point to the right host, with the ezurlmultisite settings, and check them.
- Long-term audit retention For public bodies whose records rules require keeping audit records for years - the audit guide's long-retention configuration (archives per channel, compression, write-once storage, signed checkpoints off the server)…
- Mail consent and bounces The e-mail preference system from a host's point of view - the mail gate, categories, the footer and site secret, the suppression list, the bounce mailbox reader and its settings, the consent log and data requests, and…
- Scheduled publication and embargoes How to publish transparency content at a set time with the Wait until date workflow event, how to hide content after a date with the hide cronjob, why the unpublish cronjob removes content and should not be used for…
- Sizing memory, CPU and disk The memory, CPU and disk figures the Exponential repository actually states (PHP memory limits, Velocity workers, OPcache, APCu, SQLite page cache, MongoDB, disk health thresholds, log rotation), what grows on disk, and…
- The right to erasure For public bodies answering erasure requests - what removing a user account in Exponential erases automatically (mail preferences, consent log anonymized, newsletter data through the erasure hooks), what has to be…
- Upgrades without surprises How a business plans, rehearses and runs an Exponential upgrade so that customers notice nothing but the improvements, with the phases, the roles, the tools that ship with the product and the decisions to make before…
- Verify the audit trail Step by step - check that no audit record was changed, removed or inserted with exp:audit verify or Verify now, add the check to monitoring by its exit code, and know what to do when a channel is broken.
- Automated updates with ezupdate What the ezupdate extension does for a host (checks for updates, dry runs, guarded Composer updates and installs from the administration or a shell), the switches that keep it safe, and how to automate the checking part…
- Content classes for websites Create and change content classes in the class editor - groups, attributes, required and translatable fields, name patterns, containers - and what is safe to change on a site with content.
- Copy a role for a new department 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.
- Data location Where an Exponential installation keeps data (database, storage files, caches, logs, audit records, backups, mail, search index) so a public body can state its data location, and which optional features send data…
- Designs in a multisite installation Patterns for several sites in one installation: one shared design with a small brand design per site, one design per site, per-language siteaccesses that share a design, and site extensions that carry their own settings.
- FAQ: many sites and many departments Answers to the questions public bodies ask about running many websites and departments on Exponential - several sites in one installation, separate designs and languages, shared content and users, permissions per…
- How do I see my customers and what sold best? Store > Customers lists everyone who ordered, with their number of orders and totals, and opens each customer's orders and purchased products; Store > Product statistics lists sold quantities and totals per product for…
Documentation license
This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.
Exponential Copyright © 1998-2026 Exponential Foundation and 7x