🛡️ GuardFox Security Systems › Documentation
guardfoxsecurity.com ↗ Request Access ↗
Docs › Administration › User Settings

User Settings

Configure SSO, AI provider, notification channels, API keys, and platform preferences.

Route: /settings
settings screenshot

SSO Configuration

Setup

Setting Up SSO

GuardFox Security Systems supports Azure AD and Okta for Single Sign-On via OIDC.

Azure AD

  1. In Azure Portal: App registrations → New registration
  2. Name: GuardFox Security Systems, Supported account type: Single tenant
  3. Redirect URI: https://portal.guardfoxsecurity.com/api/auth/callback/azure-ad
  4. Copy: Tenant ID, Client ID
  5. Create a client secret under Certificates & secrets
  6. In GuardFox Security Systems Settings → SSO:
Provider: Azure AD
Tenant ID: <from Azure>
Client ID: <from Azure>
Client Secret: <from Azure>

Okta

  1. In Okta Admin: Applications → Create App Integration → OIDC
  2. Sign-in redirect URI: https://portal.guardfoxsecurity.com/api/auth/callback/okta
  3. Copy: Client ID, Client Secret, Okta Domain
  4. In GuardFox Security Systems Settings → SSO:
Provider: Okta
Domain: yourcompany.okta.com
Client ID: <from Okta>
Client Secret: <from Okta>

Notification channels

Setup

Notification Channels

Configure where GuardFox Security Systems sends alerts for P1 incidents, AI triage completions, and shift handovers.

Slack

  1. Create a Slack App at api.slack.com → Incoming Webhooks
  2. Enable and add to your #soc-alerts channel
  3. Copy the Webhook URL
  4. In Settings → Notifications → Slack: paste the URL
  5. Test with the Send Test button

Email (SMTP)

SMTP Host: smtp.yourprovider.com
Port: 587
Username: [email protected]
Password: <app password>
From: GuardFox Security Systems Alerts <[email protected]>

Microsoft Teams

  1. In Teams channel: Connectors → Incoming Webhook
  2. Copy the webhook URL
  3. In Settings → Notifications → Teams: paste the URL

PagerDuty

  1. In PagerDuty: Services → + New Service → API Integration
  2. Copy the Integration Key
  3. In Settings → Notifications → PagerDuty: paste the key

P1 alerts route to PagerDuty by default; P2/P3 go to Slack and email.

Note: the Teams and PagerDuty credentials above are for your personal notification routing. The org-wide outbound integrations (Jira, ServiceNow, PagerDuty, Opsgenie, Teams, Slack, Discord) used by SOAR playbook actions are configured separately on the Integrations page (ADMIN only), not here.