The problem

Confluence space requests are low-risk but high-frequency: a new project team needs a documentation space, IT must create it, and key collisions cause silent retries that waste cycles. Manual creation is 5-10 minutes per request and scales linearly with team count.

What AscendCore does

A team lead requests a new Confluence space in Slack or Teams with a key + name. AscendCore checks for key collisions BEFORE posting the approval card (so the admin doesn't approve into a guaranteed failure), proposes the creation with full context, and on approval creates the space via Atlassian's v2 REST API. The audit row captures the created space's ID + UI URL for compliance traceability.

Workflow

Trigger — /confluence-space <space-key> "<space-name>" [description] from Slack or confluence-space <space-key> "<space-name>" [description] from Teams
Pre-flight — query Confluence for an existing space with the same key. If a collision exists, the requester sees the conflict immediately (no admin approval is consumed).
Propose — admin approval card with key + name + description + the projected space URL
Approve — IT admin approval (Phase 2 default; auto-execute for low-risk policies arrives in Phase 3)
Create — space created via Confluence Cloud REST API v2
Notify — requester DM'd with the new space URL
Audit — confluence_space.created row written to the tamper-evident chain with the space ID, key, name, URL

Integrations

Atlassian Confluence — Space creation + duplicate detection via REST API v2
Slack + Microsoft Teams — Request trigger, approval, confirmation

Configuration

CONFLUENCE_SITE_URL    (optional — falls back to JIRA_SITE_URL)
CONFLUENCE_EMAIL       (optional — falls back to JIRA_EMAIL)
CONFLUENCE_API_TOKEN   (optional — falls back to JIRA_API_TOKEN)

The fallback chain matches the common deployment pattern: a single Atlassian Cloud tenant with a shared service account for Jira + Confluence.

Roadmap

Phase 3: Page-template application at create-time
Phase 3: Group → space-member provisioning (resolve a Jira project team or Entra group into Confluence members)
Phase 3: Per-space permission scaffolding (auto-grant space-admin to the requester or a designated team)
Phase 3: Auto-approve under auto_low_risk policy for routine team-space creation

Status

Live in production — admin-initiated approval flow on Slack + Teams with full audit-chain coverage. Phase 2 ships create + collision detection; templates and member-add are Phase 3.

Versioned, deterministic, auditable

Every runbook is defined as a versioned YAML manifest with explicit triggers, steps, and approval policies. The runbook itself is the audit-ready record of what AscendCore can and will do — chat is just the interface that triggers it.

name: confluence-space-provisioning trigger: channels: [slack, teams] intents: [confluence_space_create] steps: - check_space_key_availability # propose-time duplicate detection - admin_approval - create_space approval: required: true approvers: [it-admins] # Phase 3 enhancements (deferred): template application, group→member # provisioning, per-space permission scaffolding.

Confluence Space Provisioning