> ## Documentation Index
> Fetch the complete documentation index at: https://docs.casebender.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings

> Manage your CaseBender account, organization, security operations configuration, integrations, and platform preferences.

## Overview

Settings combines personal account controls with organization and platform administration. The navigation items you see depend on your role, organization, permissions, and enabled platform capabilities.

## Account settings

<CardGroup cols={2}>
  <Card title="Profile" icon="user" href="/settings/account/profile">
    Manage your name, avatar, password, and multi-factor authentication.
  </Card>

  <Card title="Organizations" icon="building" href="/settings/account/organizations">
    Configure organizational structure, governance, and administrators.
  </Card>

  <Card title="Teams" icon="users" href="/settings/account/teams">
    Manage teams, classification, membership, escalation, and shared notification channels.
  </Card>

  <Card title="Members" icon="user-group" href="/settings/account/members">
    Review users and administer invitations, roles, and team assignments.
  </Card>

  <Card title="Notifications" icon="bell" href="/settings/account/notifications">
    Review your inbox and configure personal notification preferences.
  </Card>

  <Card title="API Keys" icon="key" href="/settings/account/api-keys">
    Create scoped credentials and manage their operational lifecycle.
  </Card>
</CardGroup>

## Platform settings

<CardGroup cols={2}>
  <Card title="Integrations" icon="plug" href="/settings/integrations/introduction">
    Connect CaseBender with security, collaboration, and infrastructure services.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/settings/workflows/introduction">
    Build automated workflows for security operations.
  </Card>

  <Card title="AI" icon="robot" href="/settings/ai/introduction">
    Configure supported AI capabilities and providers.
  </Card>

  <Card title="Custom Fields" icon="rectangle-list" href="/settings/custom-fields/introduction">
    Define structured fields for supported entities.
  </Card>

  <Card title="Observable Types" icon="eye" href="/settings/observable-types/introduction">
    Manage the observable types used during investigations.
  </Card>

  <Card title="Attack Patterns" icon="shield" href="/settings/attack-patterns/introduction">
    Maintain MITRE ATT\&CK-aligned attack-pattern data.
  </Card>

  <Card title="Alert Statuses" icon="bell" href="/settings/alert-statuses/introduction">
    Configure the statuses used throughout the alert lifecycle.
  </Card>

  <Card title="Case Statuses" icon="folder" href="/settings/case-statuses/introduction">
    Configure the statuses used throughout the case lifecycle.
  </Card>

  <Card title="Templates" icon="file" href="/settings/templates/introduction">
    Create reusable structures for supported records.
  </Card>

  <Card title="Branding" icon="palette" href="/settings/branding/introduction">
    Customize the visual identity of your CaseBender instance.
  </Card>
</CardGroup>

## Access control

* Personal settings are available to authenticated users.
* Organization and team management require scoped administrative permissions.
* Sensitive operations can require step-up authentication.
* Read-only roles can inspect permitted settings without changing them.
* Server-side authorization remains authoritative even when the interface hides an action.

See [Access Control](/security/access-control) for the role and permission model.

## Change-management recommendations

1. **Use least privilege.** Grant only the permissions required for each administrator and integration.
2. **Test safely.** Validate workflow, integration, notification, and governance changes outside production when possible.
3. **Document ownership.** Record who owns each organization, team, integration, and API credential.
4. **Review regularly.** Audit memberships, elevated roles, credentials, notification destinations, and retention settings.
5. **Plan rollback.** Understand how to reverse a configuration change before applying it to production.

<Warning>
  Settings can affect access, data handling, automation, and incident delivery. Coordinate high-impact changes with the relevant security, privacy, legal, and platform owners.
</Warning>