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

# Settings

**Account** at `/settings` shows your identity, workspace and member roster. Use **Sign out** to end the current session. A failed roster request is an error, not an empty workspace.

**Company** at `/settings/company` shows the company selected for the workspace and its research evidence. Workspace owners and admins can change the selected company. Review candidate identity and supporting sources before confirming a match. Unknown or conflicting claims stay visible. A missing research service does not make an inferred company fact verified.

**Go-to-market** at `/settings/gtm` shows the workspace's sales context. Workspace owners and admins can edit it; members have read-only access. Explicit company, vendor and competitor choices guide the available research views. Updating defaults does not silently rewrite existing Signals rules.

**API access** at `/settings/api` manages scoped keys for programmatic reads. Name each key for its client, select `read` and/or `export`, and copy the new key while its one-time secret is displayed. Existing secrets cannot be recovered; revoke an unused or exposed key and create a replacement. Keys remain bound to their creating workspace and current key owner's pro entitlement. `read` grants reads and `export` grants exports; neither grants writes. MCP requires `read`, including when a key also has `export`.

The workspace shares 10,000 API-key requests per UTC calendar month and 100 requests per 60-second workspace window across its keys. Revoking or creating a key does not reset those allowances. HTTP MCP protocol requests and the REST requests made by its tools consume the same monthly allowance. See [Authentication and errors](/docs/developers/authentication-and-errors) for counting rules and quota headers.

Manufact is selected for managed MCP hosting and is not activated yet. The MCP connection section currently describes the built-in implementation endpoint and required `X-Api-Key` header name; it is not the selected managed production connection. Add them to a client that supports Streamable HTTP with custom request headers, and use a saved `read` key as the header's secret value. Copying the endpoint or header name does not recover an existing key. There is no OAuth sign-in through this endpoint.

Connection status distinguishes a ready connection, missing pro entitlement, an operator pause, an unconfigured environment and a failed status request. The demo preview is not configured for real API-key MCP access. Settings shows runtime availability; it does not activate the application or change operator flags.

Company selection is an administrative permission. Reading the roster or account data does not grant administrative access. If a setting fails to save, keep the error's request ID and reload before retrying a stale revision.

The API tab shows workspace requests used against the monthly allowance and the next reset time in UTC. MCP requests also count the underlying API calls they make.