Skip to main content

Flows on vault events

When OpenRegister is installed, an audited vault event can start a flow on the Flows page: a share that is granted, a link that is opened, an emergency access request, an application that waits for approval. Keepiq hands the flow the same metadata a SIEM sink gets: who did what to which item, and when. Never a secret value, an item name, a username or an address.

Without OpenRegister nothing is registered with a flow engine, nothing is fired and the Flows section is not shown.

Switching groups on​

Every group starts switched off, so a fresh install fires nothing. An administrator switches groups on in the Keepiq admin settings, under Audit, section Flows. The choice is stored in the app config value flow_trigger_groups (a JSON list) and is part of the audit area settings (GET / PUT /apps/keepiq/api/settings/admin/audit).

GroupKeyEvents
Itemsitemsitems, folders, attachments, leases, vault exports and backups, policies, compliance reports
Item readsitem_readsan item revealed or used, an attachment downloaded, a honey item touched (fires on every reveal)
Sharingsharingshares, team folders, federated shares and federation partners
Linkslinkslink shares
Requestsrequestssecret requests
Emergency accessemergency_accessemergency access and account recovery
Applicationsapplicationsapplications, MCP tools and SIEM sinks
Keyskeysencryption suites, key proofs, passkeys, certificates and device approvals

Triggers​

Each audit event type fires as keepiq. plus the type, for example keepiq.share.granted or keepiq.emergency_access.requested. The flow builder lists them under the group Vault with a plain label ("A share is granted") once OpenRegister offers its trigger catalog extension; until then a flow stored with a keepiq.* trigger still matches when the event fires.

Payload​

A flow is started with an empty subject and the SIEM payload as context.payload:

{
"eventType": "share.granted",
"category": "share",
"actorType": "user",
"actorId": "alice",
"objectType": "secret",
"objectId": "42",
"occurredAt": "2026-11-14T09:30:00+00:00",
"metadata": { "recipientType": "user", "recipientId": "bob" }
}

The metadata holds only the keys the SIEM export allows for that event type. A failure in the flow engine is written to the Nextcloud log and never blocks the vault action that caused it.