Docs, Support & Knowledge
Sync decision logs, charters, and project docs in client-owned spaces.
Screenshot — illustrative
BotPM × Confluence workspace view
Product screenshot placeholder. Replace with the live integration view once enabled in your tenant.
What syncs in from Confluence
What BotPM writes back to Confluence
Connect credentials in workspace settings
A workspace admin authorises BotPM with credentials your organisation controls. Scope down to specific tenants, projects, or spaces as needed.
Map fields and project scope
During onboarding we map source fields, project identifiers, and ownership rules so signals route to the right BotPM project context.
Set autonomy and approval gates
Choose Assist, Operate, or Lead per integration. Define which actions require human approval and which can run inside policy.
Audit and review
Every read and write is logged. Workspace admins can review activity, narrow scope, or disable the integration at any time.
Availability depends on plan, enabled credentials, tenant permissions, and field mappings completed during onboarding. BotPM only acts inside the policies you approve.
Start free, or book a working session to map Confluence into your governance model.