> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/merge-workforce/settings/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Settings

> Build once. Connect to every API, tool, and LLM. Ship products and agents to production without owning the integration stack.

## Docs

- [Team and roles](https://docs.merge.dev/merge-workforce/settings/team-and-roles.md): How to invite dashboard members, what each built-in role grants, how to build a custom role, and which permission gates which surface.
- [Multi-factor authentication](https://docs.merge.dev/merge-workforce/settings/mfa.md): How MFA works for Workforce dashboard sign-in, why SSO organizations enforce the second factor at the identity provider instead, and what to do when someone loses their authenticator.
- [API keys](https://docs.merge.dev/merge-workforce/settings/api-keys.md): The Access Keys an admin creates in Workforce: production versus test, expiry and restrictions, rotation, and minting narrower keys through the API. Also how these differ from the keys employees get.
- [Billing and usage](https://docs.merge.dev/merge-workforce/settings/billing.md): How Workforce billing works: tool call metering, why provisioning employees does not change a Workforce organization's plan, and where tool usage and model spend are each reported.