Epic 8: Administration, usage, integrations, and audit backlog

Administrators configure tiers and seats, connect V1 integration, users see usage vs limits, and sensitive actions are auditable.

backlogStory 8.1: Subscription tier and seat configuration

As an administrator, I want to configure tier limits and seats, So that billing matches the org.

Maps to: FR42.

Acceptance Criteria:

Given admin role
When settings saved
Then limits persist and enforce invite/usage rules per policy
And UI matches Settings density (UX-DR10)


backlogStory 8.2: V1 external integration connector

As an administrator, I want to connect Jira or Notion (V1 policy), So that enterprise onboarding isn’t manual-only.

Maps to: FR43, NFR-I2.

Acceptance Criteria:

Given OAuth or API key flow (document choice)
When connection succeeds
Then status badge shows Connected; errors show Degraded with retry
And webhook handlers idempotent where applicable


backlogStory 8.3: Usage vs subscription limits

As a user, I want to see usage against limits, So that I understand consumption.

Maps to: FR44, NFR-R3.

Acceptance Criteria:

Given metering data
When user opens usage panel
Then sessions/tokens (per product definition) display vs tier caps
And approaching limit shows non-alarming warning


backlogStory 8.4: Audit log for sensitive actions

As an administrator, I want append-only audit history for sensitive changes, So that we meet enterprise expectations.

Maps to: FR45, NFR-S6.

Acceptance Criteria:

Given security-sensitive events (integration, override, role, release waiver)
When they occur
Then audit entries capture actor, timestamp, workspace, payload summary
And entries cannot be edited by normal admins