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

# Settings and Preferences

> Account settings, notifications, connected accounts, defaults, and feedback operations

# Settings and Preferences

This section covers user-level and workspace-level settings that influence day-to-day operations.

## Personal settings tab map

| Tab           | Primary purpose       | Typical actions                                                 |
| ------------- | --------------------- | --------------------------------------------------------------- |
| Profile       | Identity and defaults | Update name/avatar, request email change, set default workspace |
| Security      | Account hardening     | Change/set password, link social providers, configure 2FA       |
| Notifications | Communication routing | Enable/disable email notification categories                    |

## Who should review settings regularly

| Role                  | Recommended review cadence      |
| --------------------- | ------------------------------- |
| Workspace owner/admin | Monthly                         |
| Campaign operator     | Quarterly                       |
| Analyst/viewer        | Quarterly or after role changes |

## Profile behavior

Common profile actions:

* update display name
* review email verification state
* request email change with verification flow
* set default workspace for first post-login landing

Email-change flow is verification-based. The new email becomes active only after confirmation.

Profile hygiene checklist:

1. Ensure display name and avatar are current for team context.
2. Confirm verified email is active and monitored.
3. Confirm default workspace is the one used most often.
4. Re-check profile settings after changing role or team.

## Security behavior

Common controls:

* change password for credential accounts
* set password for social-only accounts
* link or unlink social providers (Google, Apple)
* enforce at least one valid login method before unlinking
* enable/disable 2FA and manage backup codes

2FA operations typically include:

* password verification before setup
* authenticator QR scan
* code verification
* backup code reveal/copy/regeneration

Account-auth lifecycle flows commonly include:

* verify-email after registration or email change
* forgot-password and reset-password recovery path
* two-factor challenge during login when enabled
* connected-account sign-in fallbacks where configured

Security hygiene checklist:

1. Keep at least one stable login method active at all times.
2. Regenerate backup codes after suspicious access.
3. Revoke unknown sessions after credential updates.
4. Review linked social providers for necessity.

## Notification behavior

Set notification preferences to control:

* operational alerts
* billing and usage notifications
* integration and webhook incident signals
* partner and workspace communication updates

Typical categories include:

* click milestones, weekly summary, monthly summary
* billing alerts and credit warnings
* workspace invites and member join events
* partner applications, commissions, payouts, fraud alerts, partner messages
* product updates and tips/guides

## Notification routing best practices

* route high-priority alerts to monitored team inboxes.
* avoid enabling noisy categories for users not responsible for operations.
* review notification settings after ownership or on-call changes.

## Default workspace behavior

For multi-workspace users:

* set personal default workspace
* verify correct landing context after sign-in
* validate switching behavior on mobile and desktop

## Settings troubleshooting

| Issue                                    | Likely cause                         | First fix                                |
| ---------------------------------------- | ------------------------------------ | ---------------------------------------- |
| User lands in wrong workspace            | Default workspace not set correctly  | Update default workspace in profile      |
| User locked out after unlinking provider | No alternative login method retained | Re-establish password or linked provider |
| Missing expected emails                  | Notification category disabled       | Re-enable relevant notification toggles  |
| 2FA setup fails                          | App time skew or invalid setup step  | Re-run setup and verify device time      |

## Feedback and support routing

Use built-in feedback/support channels for:

* bug reports
* feature requests
* onboarding/help requests

## Legal and policy surfaces

Operators should keep Terms of Service and Privacy Policy references visible for:

* workspace members and invited users
* partner/affiliate onboarding contexts
* customer-facing support or dispute workflows

## Operational best practices

* review account security monthly
* remove unused connected providers
* validate notification routing after role changes
* keep notification routing aligned with your on-call/team process
* verify brand and profile consistency for customer-facing workflows

Related:

* `/user-guides/manual/workspace/workspaces-and-access`
* `/user-guides/manual/workspace/security-and-compliance`