Skip to main content

Settings Overview

Settings controls workspace behavior, team access, channels, install snippets, security options, and operator workflows.

Settings Areas

Permission Model

Workspace settings writes are guarded by section-specific permissions. A user only needs write access to the sections that actually changed. Examples:
  • Editing macros requires macro permissions.
  • Editing automations requires automation permissions.
  • Changing company identity requires workspace write access.
  • Changing plans, add-ons, or subscription management requires workspace write access.
  • Customizing a user’s direct permissions requires user and role management access.
  • Reading settings requires authenticated workspace access.

Integrations Catalog

Settings -> Integrations shows the workspace integration catalog. It includes customer, context, CRM, and workflow connectors such as GitHub, Discord, Slack, Jira, Linear, Confluence, HubSpot, Notion, Zapier, and Sentry. It also includes Webhooks for sending signed support events to customer-owned HTTPS endpoints. Cards route to the relevant Woes page or connection dialog. Connector setup should explain what admins can configure and what operators can use after the connection is complete. Context-style integrations such as GitHub, Notion, Confluence, and synced HubSpot CRM records appear in the Context Library after import or sync. HubSpot CRM context is operator-only and is not exposed to customers.

Usage Visibility

Settings surfaces current plan usage so admins can watch the limits that affect support operations:
  • AI resolutions.
  • Operator seats.
  • AI agents.
  • API sources.
  • Indexed endpoints.
  • Public API calls by workspace API key.
  • Live API checks from guarded source tests.
Monthly public API and live API check meters reset at the start of each UTC month.

Billing And Subscription Management

Admins manage the active plan from Billing. Billing shows the selected plan, Stripe subscription status, projected monthly total, usage meters, public API calls by key, and active add-ons. When Stripe is configured:
  • Plan changes open Stripe Checkout.
  • The Manage subscription button opens Stripe Billing Portal.
  • Subscription updates sync back into Woes after Stripe confirms the billing state.
  • Stripe customer and subscription identifiers are stored server-side for the workspace.

Bring Your Own AI

Bring Your Own AI appears only for workspaces on the Bring Your Own AI plan. It lets admins connect a customer-owned provider key from the curated in-app list and choose a supported model. Provider keys are stored server-side and returned to the UI only as redacted status hints. They are never exposed to customers, docs pages, widget scripts, or REST API responses.

Safe Configuration Principles

  • Keep credentials in the correct secret settings, not in prompts or docs.
  • Use role-based permissions for changes that affect customers.
  • Use per-user permission overrides only when a user needs access that differs from their role.
  • Prefer a narrow role for operators who do not manage setup.
  • Review agent widget keys before installing widgets on public pages.
  • Manage personal notification preferences from the account/profile dialog.
  • Use the API Reference tab for REST API behavior, request examples, and generated endpoint schemas.
Last modified on July 4, 2026