The Wiki raises an event for each important operation: a page published, a comment added, a question asked, a space imported, a user created. Policies, automation and plugins react to these events: a policy or plugin can stop an operation before it happens, and automation or a plugin can act after it has happened.
1. Before and after
| Phase | When | What subscribers can do |
|---|---|---|
| Before | Before the operation runs | Stop it with a message (on events marked *blocking*), or adjust the few fields the event allows. They have a few seconds at most. |
| After | Once the operation has succeeded | React to it: send an alert, notify another system. They can't undo or slow down the operation. |
Passwords, keys and similar secrets are never included in an event. Some events leave out who acted: a vote (qna.vote) doesn't say who voted.
2. Delivery
- After-events are saved in the database together with the change that caused them, so they are never lost when a server restarts, and each is delivered once across all servers of a cluster.
- They usually arrive within a few seconds.
- A subscriber that fails is retried with increasing delays (up to 8 times by default, over several hours); after that the delivery is marked as failed and kept for 30 days. Administrators see deliveries under Settings → Advanced → Event deliveries (events:admin).
- The same event can occasionally be delivered twice (for example after a server restart mid-delivery). Plugins and integrations must handle repeats.
In the tables, yes · policies marks events that also accept organization policies; plain yes events accept only platform policies and plugins. Events marked no can't be stopped.
3. Wiki events
What happens in spaces, pages, Q&A and calendars.
4. Spaces and imports
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| space.create | before, after | yes · policies | A wiki space is created. Policies can, for example, forbid internal or public spaces. |
| space.delete | before, after | yes · policies | A wiki space is deleted, with its members' roles in it. |
| space.import.complete | after | no | An import into a wiki space ended: done, failed or cancelled, with how many pages it created, updated and left out. |
| space.import.start | before, after | yes · policies | An import of another wiki's export (Confluence) or of Markdown files into a wiki space is started. Policies can refuse imports, for example outside some spaces. |
| space.archive | before, after | yes · policies | A wiki space is archived: read-only for everyone until restored. Policies can, for example, keep certain spaces from being archived. |
| space.label.update | before, after | yes · policies | A wiki space's labels change (the same labels pages carry), with the labels added and removed. |
| space.restore | before, after | yes · policies | An archived wiki space is restored: its pages can be written again. |
| space.update | before, after | yes · policies | A wiki space's name, description, visibility, icon, category or status change (archiving and restoring also raise space.archive and space.restore). |
| space_categories.update | before, after | yes | The list of space categories (which group the space list) is saved. Removing a category leaves its spaces in none. |
5. Mirror spaces
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| mirror.convert | before, after | yes · policies | A mirror space is converted into a normal space: its mirrors are removed and its pages can be edited in the wiki. |
| mirror.create | before, after | yes · policies | A mirror is set up in a wiki space: the space's pages will follow a git repository's docs or uploaded archives. Policies can, for example, allow only some hosts or repositories. |
| mirror.delete | before, after | yes · policies | A mirror is removed from a wiki space. Its pages stay. |
| mirror.failed | after | no | A sync of a mirror failed or was cancelled, with the reason. |
| mirror.suggestion.create | after | no | A reader suggested an edit to a mirrored page: a pull or merge request was opened on the source. |
| mirror.synced | after | no | A sync of a mirror finished: how many pages it created, updated and removed. |
| mirror.update | before, after | yes · policies | A mirror's source, schedule or settings change. |
| mirror_settings.update | before, after | yes | The installation's mirror settings (mirrors allowed, who sets them up, the largest archive, internal git hosts) change. |
6. Pages
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| html_block.create | before, after | yes · policies | A space admin saves an HTML block for a wiki space's pages (new or changed: every save is a new block). Policies can, for example, refuse HTML that loads scripts. |
| page.attachment.create | before, after | yes · policies | A file (an image, a video or subtitles) is uploaded to a wiki page. Policies can, for example, refuse uploads in some spaces. |
| page.attachment.delete | before, after | yes · policies | A file (an image, a video or subtitles) is deleted from a wiki page, also from the published versions that showed it. |
| page.comment.create | before, after | yes · policies | Someone comments on a wiki page: a new thread on the page or on a stretch of its text (inline), or a reply in a thread. |
| page.comment.delete | before, after | yes · policies | A comment on a wiki page is deleted by its author or a space admin; deleting a thread's first comment deletes its replies. |
| page.comment.update | before, after | yes · policies | A comment on a wiki page is changed by its author (action edit), or a comment thread is resolved or reopened (resolve, reopen). |
| page.create | before, after | yes · policies | A wiki page is created (as a draft): blank, from one of its space's templates (template), or as a copy of another page (copied_from). A whiteboard is created the same way with kind board (live at once, no draft). |
| page.delete | before, after | yes · policies | A wiki page and the pages under it go to the space's trash. |
| page.label.update | before, after | yes · policies | Labels are added to a wiki page or removed from it. |
| page.lock.create | before, after | yes · policies | A wiki page is locked, with the pages under it: in mode view only the people and groups on the lock see them; in mode edit everyone who reads the space sees them and only those on the lock as Can edit change them. A lock only narrows what space roles allow. |
| page.lock.delete | before, after | yes · policies | A wiki page's lock is removed: by someone who may edit the page, or from the space's Locked pages settings by a space or super admin (from_settings, with their note). The pages fall back to the lock above them, if any. |
| page.lock.update | before, after | yes · policies | A wiki page's lock changes mode (previous_mode) or who is on it. |
| page.move | before, after | yes · policies | A wiki page moves to another parent in its space (a change of order among siblings raises nothing). |
| page.publish | before, after | yes · policies | A wiki page is published: its draft becomes its next version, which every reader of its space sees. Policies can, for example, require a review first. |
| page.purge | before, after | yes · policies | A deleted wiki page and the pages deleted with it are removed for good: by a space admin (before and after), or by the trash retention job (after only). |
| page.reaction | after | no | Someone likes or dislikes a published wiki page ("Was this page helpful?"), changes their answer or takes it back. |
| page.restore | before, after | yes · policies | A wiki page comes back from the trash with the pages deleted with it. |
| page.review.decide | before, after | yes · policies | A review request on a wiki page is answered by its reviewer (state approved or changes) or cancelled by the person who asked or a space admin (cancelled). |
| page.review.request | before, after | yes · policies | Someone who edits a wiki page asks another editor of the space to review its draft, optionally by a date (one event per reviewer). |
| page.review_by.set | before, after | yes · policies | Someone who edits a wiki page sets the date it should be reviewed by, or clears it. |
| page.schedule.cancel | before, after | yes · policies | Someone who edits a wiki page cancels its scheduled publish, or the scheduled publish is dropped without being made (its draft or title changed, its maker no longer edits the space, the publish was refused); a drop raises the after-event only. |
| page.schedule.set | before, after | yes · policies | Someone who edits a wiki page schedules its draft to be published at a time (or moves the time). The publish itself raises page.publish, as the person who scheduled it. |
| page.template.create | before, after | yes · policies | A wiki template is made, in a space or in the template library (scope): written in the template editor, from a page (from_page), with the pages under it when asked, as a customised copy of a library template, or of a whiteboard (kind board, from_board). |
| page.template.delete | before, after | yes · policies | A template of a wiki space or of the template library (scope) is deleted. Pages and whiteboards made from it keep their content. |
| page.template.switch | before, after | yes · policies | A wiki space turns a library template on or off for its new pages (enabled). |
| page.template.update | before, after | yes · policies | A template of a wiki space or of the template library (scope) is renamed, described, grouped, switched on or off for every space, saved in the template editor, given a page's or a whiteboard's content, or reset to the original (reset). |
| page.update | before, after | yes · policies | A wiki page's title or status changes. Publishing also raises page.publish. |
| page.version.restore | after | no | An older version of a wiki page is published again, as the page's newest version (after page.publish). |
| wiki.label.delete | before, after | yes | A site admin removes a wiki label from every page. |
| wiki.label.update | before, after | yes | A site admin renames a wiki label, or merges it into another label. |
7. Blogs
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| blog.follow | after | no | Someone starts or stops following a wiki space's blog (followers are told about new posts). |
| blog.feed.create | before, after | yes · fail closed | Someone makes a personal feed address for the wiki's blogs (the old one stops). A policy can refuse it. |
| blog.feed.delete | after | no | A personal feed address for the wiki's blogs is stopped: by its owner, or by signing out of their other sessions. |
| blog.post.feature | before, after | yes · policies | A space admin pins a post to the top of the space's blog, or unpins it. |
| blog.post.publish | before, after | yes · policies | A blog post is published for the first time (later publishes are page.publish only). After it, the blog's followers are told unless its authors turned that off. |
| blog.post.update | before, after | yes · policies | A blog post's summary, cover, co-authors, comment setting or whether followers are told changes. Its title and content are page events (page.update, page.publish with kind blog). |
| blog.settings.update | before, after | yes · policies | A wiki space's blog settings change: the blog is turned on or off, who may write posts, whether new posts take comments, whether posts show on the company Blogs page, review before publishing, the public feed. |
8. Whiteboards
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| board.reset | before, after | yes · policies | An editor resets a wiki whiteboard that stopped taking changes (over its item or image limit, or unreadable) to one of its versions: changes after that version are dropped, and everyone drawing on it reloads it. |
| board.update | after | no | People changed a wiki whiteboard and stopped for two minutes: one event per session of changes, with who changed it and how many items it holds. The board's watchers are told. |
| board.version.create | before, after | yes · policies | Someone names a version of a wiki whiteboard: the board as it is now, or one of its automatic versions (renaming one too). Named versions are kept. |
| board.version.delete | before, after | yes · policies | Someone deletes a named version of a wiki whiteboard. |
| board.version.restore | before, after | yes · policies | Someone restores a version of a wiki whiteboard: the board is first kept as an automatic version, then the version's items are put back as a new change everyone sees. |
9. Calendar
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| calendar.event.create | before, after | yes · policies | An event or someone's leave is added to a wiki space's calendar. Policies can refuse it; automation can, for example, copy events to another calendar. |
| calendar.event.delete | before, after | yes · policies | An event or leave is removed from a wiki space's calendar. |
| calendar.event.update | before, after | yes · policies | An event or leave in a wiki space's calendar is changed: its title, times, repeat or person. |
| calendar.feed.create | before, after | yes · policies | Someone makes a secret address that lets calendar apps read their wiki calendars without signing in (replacing any earlier one). Policies can refuse it. |
| calendar.feed.delete | after | no | Someone turns off their secret calendar address; calendar apps can't read it any more. |
10. Q&A
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| qna.answer.accept | before, after | yes · policies | The asker or a moderator accepts an answer as the one that solved the question, moves the accept to another answer or takes it back. |
| qna.answer.create | before, after | yes · policies | A question gets an answer. |
| qna.answer.delete | before, after | yes · policies | An answer is deleted, by its author or a moderator. |
| qna.answer.update | before, after | yes · policies | An answer is edited, by its author or a moderator. |
| qna.comment.create | before, after | yes · policies | Someone comments on a question or an answer. |
| qna.comment.delete | before, after | yes · policies | A comment on a question or an answer is deleted, by its author or a moderator. |
| qna.comment.update | before, after | yes · policies | A comment on a question or an answer is edited, by its author or a moderator. |
| qna.image.create | before, after | yes · policies | Someone uploads an image to show in a question or an answer. Policies can refuse it by type or dimensions. |
| qna.question.close | before, after | yes · policies | A moderator closes a question (no new answers), marks it a duplicate of another question (no new answers either) or opens it again. |
| qna.question.create | before, after | yes · policies | A question is asked in the wiki's Q&A. Policies can refuse questions; automation can, for example, post new questions to a chat channel. |
| qna.question.delete | before, after | yes · policies | A question is deleted with its answers, by the asker (while it has no answers) or a moderator. |
| qna.question.lock | before, after | yes · policies | A moderator locks a question's comments (only moderators comment then) or unlocks them. |
| qna.question.update | before, after | yes · policies | A question's title, text or tags are edited, by the asker or a moderator. |
| qna.settings.update | before, after | yes · policies | A moderator changes the organization's Q&A settings, such as allowing public questions (readable by anyone while anonymous access is on). Policies can keep public questions off. |
| qna.tag.merge | before, after | yes · policies | A moderator merges a tag into another: its questions and followers move to the other tag and the tag goes. |
| qna.vote | after | no | Someone votes a question or an answer up or down, or takes their vote back. The voter isn't in the event. |
11. Wiki settings
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| html_block_settings.update | before, after | yes | The HTML blocks setting changes: on or off, who may add blocks, and the sites blocks may reach. Taking a site off stops it in every block. |
| import_settings.update | before, after | yes | The installation's wiki import settings (imports allowed, largest export) change. |
| robots.update | before, after | yes | What the wiki's robots.txt tells search engines changes (block all, allow public spaces, or custom text). |
| video_sites.update | before, after | yes | The sites wiki pages may embed videos from change (YouTube, Vimeo, other hosts). Embeds from a site taken off stop playing in every page. |
12. Platform events
Sign-in, people, settings and the running of the installation. The Wiki shares these with every product built on its platform.
13. Sign-in, tokens and access
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| access.grant | before, after | yes · policies | A user or group is given a role on a resource, such as a space, or their role there changes. |
| access.revoke | before, after | yes · policies | A user's or group's role on a resource, such as a space, is removed. |
| ai_agents.mcp_keys.update | before, after | yes | The installation's switch for MCP keys changes. While off, no MCP key works and none can be made; turning it off keeps the keys. |
| apitoken.create | before, after | yes · policies | A user creates an API token. |
| apitoken.org_policy.update | before, after | yes · policies | An admin changes the organization's API token rules (maximum lifetime, count, blocked permissions). |
| apitoken.revoke | after | no | API tokens are revoked by their owner or an admin. |
| apitoken.rotate | before, after | yes · policies | A user replaces an API token's secret. |
| apitoken.update | before, after | yes · policies | A user renames an API token or changes its IP allowlist. |
| applink.connect | before, after | yes · policies | A person connects their own account on a linked installation: requests through the link then act as them there. |
| applink.create | before, after | yes | A link with another installation is created, from this side or accepted from the other one: the two then trust each other's applications. |
| applink.delete | before, after | yes | A link with another installation is removed, with the application made here for it and people's connections through it. |
| applink.update | before, after | yes | A link with another installation becomes active or gets new credentials. |
| auth.login | before, after | yes · policies | A user signs in, with a password or through single sign-on (method). |
| auth.login.failed | after | no | A sign-in is refused (wrong credentials, inactive or locked account). |
| auth.logout | after | no | A user signs out. |
| auth.session.revoke | after | no | Sessions are ended (by the user, an admin or the system). |
| mcp.key.create | before, after | yes · policies | A person makes an MCP key: a static key an AI agent without OAuth uses on one plugin's MCP server, acting as that person until it expires. |
| mcp.key.revoke | before, after | yes · policies | An MCP key is revoked by its owner or an administrator; it stops working at once on every server. |
| oauth.client.create | before, after | yes | An OAuth application is registered: it can then ask people to let it act for them. |
| oauth.client.delete | before, after | yes | An OAuth application is removed; every connection to it and its tokens stop working. |
| oauth.client.update | before, after | yes | An OAuth application is changed (scopes, redirect addresses, approval, lifetimes), enabled, disabled or gets a new secret. |
| oauth.consent.grant | before, after | yes · policies | A person allows an OAuth application to act for them (or it is pre-approved for them), or allows more scopes. |
| oauth.consent.revoke | after | no | A connection to an OAuth application is revoked by the person, an administrator, or because the application was removed. |
| oauth.federation.create | before, after | yes | An OAuth application starts trusting tokens from an outside issuer (a CI system) in place of its secret. |
| oauth.federation.delete | before, after | yes | A workload identity trust rule is removed. |
| oauth.federation.update | before, after | yes | A workload identity trust rule changes (issuer, audience, conditions) or is enabled or disabled. |
| oauth.workload_token.exchange | before, after | yes · policies | A CI system's identity token is exchanged for an access token acting as an application's service account (workload identity). |
| service_account.create | before, after | yes · policies | A service account is created: a non-human user OAuth applications can act as (client credentials). |
| service_account.delete | before, after | yes · policies | A service account is deleted; applications acting as it stop working. |
| service_account.update | before, after | yes · policies | A service account is renamed, gets another role, or is disabled or enabled. |
| sso.enforcement.update | before, after | yes | Requiring single sign-on is turned on or off, or the super-admin password exception changes. |
| sso.provider.create | before, after | yes | An identity provider for single sign-on is added. |
| sso.provider.delete | before, after | yes | An identity provider is removed; its users can no longer sign in through it. |
| sso.provider.update | before, after | yes | An identity provider is changed, enabled or disabled. |
14. Users, groups and directories
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| avatar.delete | after | no | A user removes their avatar. |
| avatar.update | before, after | yes · policies | A user sets their avatar to a preset or an uploaded image. |
| directory.create | before, after | yes | A directory is added; it starts last in the order. |
| directory.delete | before, after | yes | An empty directory is deleted. |
| directory.reorder | after | no | Directories are reordered; when a person has accounts in several, the highest wins. |
| directory.sync | after | no | A directory sync finished, failed or was blocked by a safety check. |
| directory.update | before, after | yes | A directory is renamed, enabled or disabled. Users in a disabled directory can't sign in. |
| group.create | before, after | yes · policies | An administrator creates a group. |
| group.delete | before, after | yes · policies | An administrator deletes a group. Groups are never deleted by directory sync. |
| group.member.add | before, after | yes · policies | An administrator adds users to a group. |
| group.member.remove | before, after | yes · policies | An administrator removes a user added by hand from a group. |
| group.update | before, after | yes · policies | A group is renamed or its description changes. |
| user.anonymize | before, after | yes · policies | A disabled user is anonymized (GDPR erasure): personal data is removed everywhere and the account can never sign in again. Subscribers should erase what they hold about user_id. |
| user.create | before, after | yes · policies | An administrator creates a user account. |
| user.disable | before, after | yes · policies | A user account is disabled: it can't sign in and its sessions end. |
| user.enable | before, after | yes · policies | A disabled user account is enabled again. |
| user.invitation.accept | after | no | An invited user chooses a password; the account becomes active. |
| user.password.change | after | no | A user changes their own password; their other sessions end. |
| user.password.recover | after | no | A user sets a new password from a password reset email; their sessions end. |
| user.password.reset | before, after | yes · policies | An administrator sets a new password for a user; the user's sessions end. |
| user.role.change | before, after | yes · policies | A user's role changes. |
| user.unlock | after | no | An administrator unlocks an account locked after failed sign-ins. |
| user.update | before, after | yes · policies | A user's email or name is changed. |
15. Security
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| auth.session_policy.update | before, after | yes | The session policy (idle timeout, maximum length, Remember me, sessions per person) changes. |
| security.captcha.update | before, after | yes | The CAPTCHA settings change: provider, keys, or which events ask for a CAPTCHA. |
16. Settings
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| banner.create | before, after | yes | An announcement banner is created. |
| banner.delete | before, after | yes | An announcement banner is deleted. |
| banner.update | before, after | yes | An announcement banner's title, text, level, audience, schedule or switch changes. |
| branding.update | before, after | yes | The installation's branding changes: app name, brand colors, logos or favicons. |
| log_alert_rule.create | before, after | yes | A log alert rule is added. |
| log_alert_rule.delete | before, after | yes | A log alert rule is removed. |
| log_alert_rule.update | before, after | yes | A log alert rule is changed, enabled or disabled. |
| logging.settings.update | before, after | yes | The logging settings change: levels, temporary levels, or the log file. |
| mail.settings.update | before, after | yes | The email settings change (SMTP server or Amazon SES API, sender, Wiki's address). |
| security.anonymous_access.update | before, after | yes | Anonymous access is turned on or off: whether people who aren't signed in can read public spaces. |
| security.rate_limit_override.create | before, after | yes | A rate limit override is added: a different request budget for a role, org, user, API token or AI app. |
| security.rate_limit_override.delete | before, after | yes | A rate limit override is removed; the scope gets the installation's limits again. |
| security.rate_limit_override.update | before, after | yes | A rate limit override's budget, exemption or dry run changes. |
| security.rate_limits.update | before, after | yes | The installation's request rate limits are saved (Settings → Security → Rate limits). |
| site.help.update | before, after | yes | The links in the Help menu (documentation, feedback, bug reports, support) change or are reset to the defaults. |
| site.settings.update | before, after | yes | The Wiki's address (used in email links and single sign-on) changes. |
| storage.settings.update | before, after | yes | The storage settings change: where files are kept, credentials, or upload limits. |
| system_check.settings.update | before, after | yes | Who is notified about system check changes, and how, changes. |
17. Alerts
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| alert.create | before, after | yes · policies | An alert is sent to users (by an admin, a plugin or a platform rule). |
| alert.incident.resolved | after | no | Everything a grouped alert (system health) reported is OK again. |
| alert.silence.create | before, after | yes | An administrator mutes notifications (a source, a check, an item or a server), for a while or until removed. |
| alert.silence.ended | after | no | A mute ended: removed by an administrator, ran out, or its check is OK again. |
| alert.silence.update | before, after | yes | An administrator changes how long a mute lasts, or its reason. |
| alert.tuning.update | before, after | yes | An administrator changes a check's thresholds or when it notifies (or resets them to the defaults). |
18. System health
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| cluster.health.changed | after | no | The cluster health status changed (ok, warn, fail) and held for two evaluations. |
| log.alert.fired | after | no | A log alert rule matched enough log lines and fired. |
| system.check.changed | after | no | A system check found something worse than the previous run, or recovered. |
| system.check.completed | after | no | A system check run finished (scheduled or on demand). |
19. Scheduled jobs
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| scheduler.job.recovered | after | no | A job that was failing ran successfully again. |
| scheduler.job.run | before, after | yes | A scheduled job runs. Blocking subscribers can skip the run. |
| scheduler.job.trigger | before, after | yes | An admin runs a job by hand. |
| scheduler.job.unhealthy | after | no | A job failed several times in a row (SCHEDULER_UNHEALTHY_THRESHOLD). |
| scheduler.job.update | before, after | yes | An admin enables or disables a job, or changes its schedule or parameters. |
20. Backups
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| backup.create | before, after | yes | A backup of the database and platform files is taken (by a person, an API token or the daily job). The after-event carries the archive's SHA-256. |
| backup.delete | before, after | yes | A backup is deleted by a person or by the cleanup job after its retention period. |
| backup.download | before, after | yes | A backup archive is downloaded. It holds the whole database, so a policy or plugin may refuse it. |
| backup.fail | after | no | A backup failed: it couldn't be written, or it failed its integrity check. |
| backup.restore | before, after | yes | A backup is restored over the whole installation: the database and platform files are replaced (a safety backup is taken first). The after-event says whether it worked or failed and was rolled back. |
| backup.settings.update | before, after | yes | The backup settings change: whether new backups are encrypted, to which public keys, that the passphrase changed (never the passphrase itself), or whether backups count rows for test restores. |
| backup.target.update | before, after | yes | The backup target changes: archives go to the installation's storage or to a storage location of their own (where, and whether its credentials changed; never the credentials). |
| backup.test_restore | before, after | yes | A backup is test-restored into a scratch database and its row counts compared with the backup's; the after-event says whether it passed. |
| backup.update | before, after | yes | A backup is marked to keep permanently (the cleanup job skips it) or no longer, or its note changes. |
| backup.upload | before, after | yes | A backup file is brought in from outside to restore from: uploaded in chunks, registered from the import folder, or given to the offline restore command. The after-event is the backup it became, with its SHA-256. |
| backup.verify | after | no | A backup's integrity check finished: the archive read back with its published SHA-256, its signature and entry checksums, and pg_restore reading the dump. |
21. Platform
| Event | Phases | Blocking | When it happens |
|---|---|---|---|
| ai_agents.settings.update | before, after | yes | The installation's settings for AI agents change: whether MCP tools that change something (write tools) may run at all. While off, no plugin setting or AI application can turn them on. |
| cluster.node.rename | before, after | yes | An admin changes a cluster node's display name. |
| license.apply | after | no | An admin applies a new license. |
| plugin.data.delete | before, after | yes | A plugin's stored data (its database schema, key-value keys and, unless it is reset, its secrets) is deleted: when it is uninstalled with its data, restarted with its data reset, or its leftover data is deleted. |
| plugin.settings.update | before, after | yes | A plugin's settings are changed on its page: the values of its own settings, its call limits (calls per second, each caller's share, per AI application), and for an MCP plugin whether its write tools are on (read-write) and which tools are switched off. |
22. Using events
- Stop something: write a policy on a blocking event's before phase, for example require a review before page.publish, or refuse space.import.start outside some spaces.
- Be told or tell another system: write an automation rule on the after phase, for example post every qna.question.create to a chat channel with a webhook.
- Anything else: a plugin can receive both phases with its own logic.