Skip to content

Account – Settings

  • Path: /account/settings
  • Canonical tab URLs: /account/settings?tab=comment-responder|sms-requests|users|roles|permissions|integrations
  • Default tab: comment-responder when tab is missing or invalid
  • Parent: README.md
  • Children:
    • settings-organizations.md
    • settings-sms-requests.md
    • settings-users.md
    • settings-roles.md
    • settings-permissions.md
    • settings-integrations.md
    • settings-comment-responder.md
  • Page header: title “Settings” with standard topper padding (px-6 py-6, border-b #ebebeb).
  • Tab bar (pill style): Comment Responder, SMS requests, Users, Roles, Permissions, Integrations. Active tab is driven by the tab query parameter. Each tab content area is a placeholder until child settings pages are implemented.

Provide administrative configuration for enterprise governance: org/workspace structure, IAM, integrations, and application configuration.

  • Org Admin / Workspace Admin (varies per page)
  • Permissions: TBD (defined per child settings page)
  • Reference: Roles & Permissions Model
  • Settings navigation (left rail)
  • Settings content panels

TBD

  • Empty: TBD
  • Loading: load settings catalog + current org/workspace context
  • Error: permission denied
  • Complete: settings panels render

Settings changes must be applied through domain services and audited.

Domain refs:

  • Endpoints: TBD (varies by child settings page)
  • Auth: TBD
  • Rate limits: TBD
  • Webhooks/events: TBD
  • Changes may have org-wide impact; require strong auditing and least-privilege access.
  • Multi-workspace isolation must be preserved when viewing/editing settings.
  • User loses permissions mid-session; settings panels must degrade gracefully.
  • Concurrent admins update the same setting; conflict/last-write policy is TBD.
  • Audit all sensitive settings changes

Reference: Security & Compliance

TBD (see suggested global events)

Reference: Analytics Events (MVP)