Skip to main content

Settings

Configure your Align organization.

Organization Settings​

General​

  • Organization Name - Your team or company name
  • Timezone - Default timezone for date displays
  • Logo - Custom logo for your organization

Members​

Manage who has access to your organization:

  1. Go to Settings → Members
  2. Click Invite Member
  3. Enter their email address
  4. Select their role

Team invites​

An org admin adds people from Settings → Team invites in the web app. The tab shows only to org admins.

  1. Enter the email the invite is for. Only that person can then use the link. To let anyone with the link join instead, tick Let anyone with the link join. Whoever opens the link first gets in, so send it to one person only.
  2. Click Create invite link.
  3. Send the link to one person. It works once and expires 7 days after you create it (the screen shows the date; the API accepts a later date, but not more than 30 days out). The person who joins is always a member. If they use the Align CLI, they can run the align join '<link>' command shown under it instead.

The same tab lists every invite as open, used, revoked or expired, and lets you revoke an open or used one. Invites are created only here: POST, GET and DELETE /admin/invites need an interactive org-admin login, and API tokens and service tokens are refused, so an agent's token cannot add team members. align invite in the CLI opens this tab rather than calling the API.

Revoking an invite that was already used also ends the CLI token minted from it. A member who joined with that link and connected the Align CLI through it is signed out of the CLI, and has to run align login again. Their web sign-in and their membership are not touched. Revoke an unused invite to stop it working; revoke a used one only when you mean to cut off that CLI.

Roles​

RolePermissions
AdminFull access, manage settings, invite members
MemberCreate/edit decisions, view all decisions
ViewerRead-only access

Integrations​

Connect and manage your tools:

  1. Go to Settings → Integrations
  2. Click Connect next to the integration
  3. Follow the authorization flow
  4. Configure access (channels, projects, etc.)

See Integrations for detailed setup guides.

LLM Settings​

Configure how Align uses AI for decision synthesis.

Provider Options​

ProviderDescription
Align ManagedDefault, no configuration needed
OpenAIUse your own OpenAI API key
AnthropicUse your own Anthropic API key
CustomSelf-hosted models (Ollama, vLLM)

Using Your Own API Key​

  1. Go to Settings → LLM Settings
  2. Select provider (OpenAI or Anthropic)
  3. Enter your API key
  4. Click Save

Your API key is encrypted at rest and never logged.

Custom/Self-Hosted Models​

For self-hosted deployments, you can use local models:

  1. Select Custom Endpoint
  2. Enter your model server URL (OpenAI-compatible)
  3. Enter the model name
  4. Optionally add API key if required

See Self-Hosted LLM for detailed setup.

Token Limits​

Set monthly token limits to control costs:

  1. Go to Settings → LLM Settings
  2. Set Monthly Token Limit
  3. Align will notify you when approaching the limit

Notification Settings​

Configure how you receive notifications:

Email Notifications​

  • Daily Digest - Summary of new decisions
  • Mentions - When you're mentioned in a decision
  • Weekly Report - Weekly activity summary

Slack/Teams Notifications​

  • Capture Confirmations - Posted to the source channel
  • Decision Updates - When decisions are edited

Data & Privacy​

Data Retention​

Configure how long data is retained:

  • Decision Snapshots - Retained indefinitely by default
  • Raw Messages - Cleared from the decision record after analysis. Some capture and import paths hold raw content for longer; see Data Retention for the exact tables and windows
  • Audit Logs - Retained for the life of the tenant (no purge job currently runs against them)

Export​

Export and erasure are admin API endpoints, not a self-serve UI button. GDPR Article 17 (erasure) and Article 20 (portability) have endpoints, and an erasure request against a record under legal hold is rejected with 409 legal_hold_active.

Corrected 2026-09-21

This page said Article 15 (access) was "served this way". There is no separate Article 15 access endpoint. It also implied both endpoints work; neither currently executes, because both query a decisions table that does not exist in the schema. Tracked as ALI-1127. See Trust for what is actually true today.

Ask your org admin, or see Trust & Security for the endpoints.

Delete Organization​

To delete your organization and all data:

  1. Go to Settings → Danger Zone
  2. Click Delete Organization
  3. Type your organization name to confirm
  4. All data is permanently deleted
warning

This action is irreversible. All decisions, integrations, and member data will be permanently deleted.

Security​

Single Sign-On (SSO)​

Enterprise plans support SSO over OIDC, which covers:

  • Microsoft Entra ID (Azure AD)
  • Google Workspace
  • Okta
  • Any other OIDC identity provider

SAML 2.0 is not currently available. The service provider is implemented, but its signing library is not bundled in the shipped image. If SAML specifically is a requirement, raise it before you plan around it.

SCIM 2.0 provisioning (/Users and /Groups, including PATCH and deprovisioning) and directory-group-to-role mapping are available.

Contact us to configure SSO for your organization.

Audit Logs​

The audit trail is available to org admins through a filterable API, not a settings screen:

GET /admin/audit-logs?actor=&resourceType=&from=&to=&limit=

limit accepts 1 to 1000 and defaults to 100. It records permission denials, connector enable/disable and credential access, decision deletion, role and activation changes, and GDPR events. See Audit Log for the full parameter list and what is deliberately not recorded.

API Keys​

Generate API keys for programmatic access:

  1. Go to Settings → API Keys
  2. Click Create API Key
  3. Set a name and expiration
  4. Copy the key (only shown once)

Self-Hosted Settings​

For self-hosted deployments, additional settings are configured via Helm values: