SigSentrySigSentry
DashboardOrganization

Settings

Organization-wide configuration across General, Notifications, and Integrations tabs

The Settings page is a tabbed view for organization-wide configuration. Three tabs:

General tab

Read-only account info plus your subscription summary.

SectionNotes
Account InfoYour name, email, role
PlanCurrent plan badge with link to Plans

There's no editable configuration on this tab — it's a quick-reference for who you are and what plan the org is on.

Notifications tab

Two settings:

Org default severity threshold — the default severity threshold applied to newly created notification channels (and any existing channel that opts in to the tenant default). Set this to your preferred starting point — most teams pick high.

Personal preferences — a checkbox: Notify me when analyses I initiate complete. When on, you receive notifications for analyses you triggered regardless of channel thresholds. When off, you only see them via the standard channel routing.

Click Save on each section to persist changes.

Integrations tab

Manages chat workspace bindings — the inbound trigger integrations for Slack, Teams, Discord, and Google Chat.

For each platform, an Install button opens the OAuth flow if not yet connected. Once connected, the workspace appears in the Connected workspaces table:

ColumnNotes
PlatformSlack / Teams / Discord / Google Chat icon
WorkspaceThe connected workspace's identifier
Installed byUser who authorized the install
InstalledDate
ActionsDisconnect

Disconnect opens a confirmation modal — disconnecting removes SigSentry's access from that workspace.

A platform can have multiple workspaces (e.g. two Slack workspaces if you have separate ones for engineering and operations). Each is a separate row in the table.

Required role

ActionRequired permission
View SettingsAny role
Save General changes(no editable fields)
Save NotificationsAny role (per-user prefs) and team:manage for org defaults
Install / disconnect workspacesconfig:write

Project access lists

Note: the project access list that controls who can trigger chat analyses on a specific project lives on the per-project Channels page, not here. This Integrations tab covers workspace-level bindings only.