Settings

Where settings live

Open Settings from the left navigation. Settings are organized into tabs across the top. Changes are workspace-scoped and take effect immediately.

---

Account

Your personal profile: display name, email, and password. Update your name or email, or change your password (you'll re-enter your current password to do so). This is *you* — not the workspace.

---

Workspace

The workspace itself: its display name, ID, and a quick summary of members and alert status. Rename the workspace here. Everything in opSentry — alerts, partners, boards, credentials — belongs to one workspace.

---

Team

Manage who has access and what they can do. Three roles: Owner (full access, can't be removed), Admin (can manage members and settings), and Member (standard access). Invite an existing opSentry user by email and pick a role — e.g. invite jordan@yourcompany.com as an Admin — change roles from the dropdown, or remove a member (which revokes workspace access without deleting their account).

---

Billing

A read-only snapshot of your current plan, seat count, and AI-call usage for the month, plus a Manage subscription button that opens the Stripe Customer Portal to update your card, change plan, or cancel. Founding members see their discount flagged here. If you don't have a paid plan yet, it routes you to pricing.

---

Partner Map

Configuration for the partner system:

• Partner statuses — the lifecycle labels available in the partner map (default: Active, Onboarding, At Risk, Triaging, Inactive). Partners marked Inactive are excluded from alert auto-matching.
• Partner Onboarding stages — the columns on the shared onboarding board (default: Outreach → Discovery → Integration → Testing → Live). Reorder or edit (admin/owner only).
• Stuck-in-stage threshold — how many days before a partner is flagged as stuck (default: 21).
• Personal board stages — default columns for personal boards (Planning → In Progress → Review → Done).

---

Notifications

Where you connect integrations and decide where new-alert notifications go. Each has its own connect/configure panel:

• GitHub — paste a webhook URL into your repo so pushes/releases ingest as alerts. Choose AI mode (analyze each commit) or Simple mode (keyword matching, no AI cost).
• Jira — connect via OAuth; opSentry auto-registers a webhook and ingests issue transitions, sprints, and version releases.
• HubSpot — connect via OAuth to correlate support tickets with your active alerts and surface them on the dashboard.
• Slack — connect via OAuth to post alert notifications to a channel (e.g. #partner-alerts). Send a test message to confirm.
• Email alerts — add subscriber emails (e.g. oncall@yourcompany.com) to receive a message on every new alert.
• Postman — connect your Postman API key to power the From-Postman path in API Testing.

---

Credentials

Your workspace API credentials — the client ID and secret used for programmatic access (e.g. the /ingest/changelog endpoint). The secret is shown once at creation, so store it somewhere safe.

---

API Testing

Register and verify the domain your team is allowed to run Partner Tests against — your own product's domain, matched to your business email, one per workspace (e.g. api.yourcompany.com). This is the guardrail that keeps every test scoped to infrastructure you own. See API Testing (Partner Tests) for how the tester itself works.

---

Dashboard

Choose which modules appear on your dashboard and in what order — drag to reorder, toggle visibility, and restore defaults. Tailor the dashboard to what your team looks at most.