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

# Settings & Preferences

> Manage account settings and preferences.

The Settings area centralizes account configuration and application preferences. It includes identity and security context (read-only) plus controls for integrations, localization, appearance, and notifications.

Some sections are intentionally read-only to preserve auditability and reduce the risk of unauthorized profile manipulation. Levery’s access control model relies on explicit permissioning and institutional policy enforcement, so certain identity and security attributes are managed through controlled operational flows rather than self-service edits.

## Accessing Settings

Navigate to Settings from the platform menu, then select the relevant section to review context or update preferences where actions are enabled.

<CardGroup cols={2}>
  <Card title="Profile">
    Displays personal identity, address, and company details (if it exists) for transparency and operational review. This section is read-only to keep identity attributes consistent with verification and institutional controls.
  </Card>

  <Card title="Security Accounts">
    Shows sign-in details and linked Web3 accounts used for permissioned actions. This section is read-only to maintain a
    stable account binding for policy enforcement and audit trails.
  </Card>

  <Card title="Security Sessions">
    Lists active sessions with device context to support security monitoring and incident response. This section is
    read-only, and session controls depend on the deployment’s operator policy.
  </Card>

  <Card title="Devices">
    Surfaces devices associated with the account based on observed access patterns. This section is read-only and is
    intended for security visibility rather than self-managed enrollment.
  </Card>

  <Card title="Identity Verification">
    Reports KYC or KYB status and review outcomes as determined by the institution’s verification workflow. This section
    is read-only and can gate access to swaps or liquidity based on policy.
  </Card>

  <Card title="Integration">
    Creates, reviews, and renews API keys for programmatic access. This section is actionable and supports key lifecycle
    controls such as rotation and revocation within the institution’s policy boundaries.
  </Card>

  <Card title="Localization">
    Controls language and currency formatting across the app for consistent display and reporting. This section affects
    presentation only and does not alter on-chain amounts or settlement behavior.
  </Card>

  <Card title="Appearance">
    Customizes the app theme for day and night operation. This section changes visual preferences only and does not affect
    permissions, balances, or execution logic.
  </Card>
</CardGroup>

<Card title="Notifications">
  Configures notification preferences and provides a view of recent alerts. This section is designed for operational
  awareness, with security and activity signals depending on deployment configuration.
</Card>

## Support guidance

For read-only sections that require correction, the institution’s operator support channel is the source of truth for updates. Changes may require re-verification and can impact permissions for swaps or liquidity operations.