- Editors and roles per department How to let each department's editors work only on their own site in a shared Exponential installation: roles limited by subtree or section, one or several administration siteaccesses, shared media, and review of access.
- Environments for development, test and production For public-sector IT teams that keep separate development, test (acceptance) and production copies of an Exponential site. How EXP_ENV gives each machine its own settings, how to keep test copies from sending mail or…
- Extension updates Keeping the extensions of a public-sector Exponential site current - finding what runs and what is outdated, updating with a dry run through ezupdate or Composer, third-party extensions, and the checks after an update.
- Extranet launch checklist Everything to tick before the first partner, customer, dealer or supplier is invited to an Exponential extranet - address and HTTPS, separation tests, registration and approval, sign-in, files, ordering, mail…
- FAQ: support Answers to the support questions public bodies ask about Exponential - who supports it, free and paid support, response times, SLAs, partners, security reports, and how to ask so you get an answer.
- Governance of AI and agents The part of the AI, agents and agentic section for the people who set the rules - privacy and data leaving the site, cost control, the audit trail for AI, roles and least privilege for assistants and agents, and a…
- Hosting and data location requirements Requirement wording for where and how a public CMS is hosted - on premise or by a supplier, data location, databases, operating systems, outbound connections, backups and recovery - with what Exponential's documentation…
- Hosting cost drivers Which technical choices make hosting an Exponential site cheaper or dearer - hosting model, database, engine, number of sites and servers, storage, caching, optional services, backups and staff time - with the facts…
- Keeping a site current over a multi-year contract A yearly rhythm for a public body to keep an Exponential site current through a contract of several years - updates, platform, access, content checks, documentation and training - with the admin pages and commands that…
- Keeping services current How to keep service pages correct over time in Exponential - an owner per page, a required review date, a template list of overdue services, versions for what changed, and a monthly routine.
- Limit a translator to one language Task for administrators: create a role whose content policies are limited by Language, assign it to a translators' group, and test it with a test account.
- Multilingual approvals How to approve content in several official languages - one approval for all languages, or approvers per language with the Affected languages field and Language-limited roles - and how translators and approvers fit the…
- Multisite on one installation How one Exponential installation serves several sites through siteaccesses, matched by URL, host name or port; what that means for a host's isolation, logs, caches, billing and backups; and when separate installations…
- Newsletter checklist One checklist for a newsletter on Exponential with cjw_newsletter - decisions, setup, consent, rehearsal, the first real send, every send after it, and the monthly routine - each item linked to the page that explains it.
- Notifications instead of a newsletter When the kernel's notifications serve better than a newsletter: signed-in users follow a page or section and get an e-mail, at once or as a digest, when content changes; how it works, the cronjob, and its limits for…
- OpenDocument import and export How the ezodf extension imports OpenDocument Writer files as Exponential content and exports content back to Writer - what it needs (LibreOffice or OpenOffice as a converter), its settings, the views, and its documented…
- Orders day to day Handling orders in a running Exponential store - the path of one order, the screens the team uses, who may change what, customer questions, archiving, and the mistakes that cause most support calls.
- PostgreSQL for hosts PostgreSQL, the recommended database server for Exponential, from a host's point of view: versions, the database owner rule, the pgcrypto extension, settings, installing with exp:install, sequences, backups and the…
- Quarterly access review A quarterly checklist for reviewing who can do what in an Exponential site of a public body - accounts, unused accounts, roles and assignments, administrators, API keys, sessions and the audit trail - with the admin…
- Reset a staff password Step by step - help a colleague who cannot sign in, either through Forgot password or by setting a new password on their account page, after verifying who is asking, with what the system does for you afterwards.
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