> ## 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.

# Authentication

> How account access, team access, sessions, and API keys work in Linquid

## Authentication Surfaces

Linquid has two authentication surfaces:

* **Dashboard account access** for people using the UI.
* **Workspace API keys** for automation and integrations.

## Account Access (UI)

Account flows include:

* email/password sign-up and sign-in
* social sign-in providers
* email verification and password reset
* optional security controls such as 2FA (when enabled)

## Team and Workspace Access

After sign-in, access is governed by workspace membership and role.

Role settings determine who can:

* manage billing and subscription settings
* manage links/campaigns/rules
* manage integrations and webhooks
* view and export analytics

## API Keys for Automation

Workspace API keys are created from Workspace Settings.

Best practices:

* create separate keys per integration or service
* use minimum required scopes
* rotate and disable unused keys
* never expose keys in client-side code

## Session and Security Practices

Recommended operational policy:

* require strong credential hygiene
* review active access regularly
* remove stale invites and inactive members
* audit owner/admin access monthly

## Related

* `/user-guides/manual/workspace/workspace-onboarding-and-governance-playbook`
* `/user-guides/manual/workspace/workspaces-and-access`
* `/user-guides/manual/workspace/security-and-compliance`
* `/api-reference/auth/overview`