> ## Documentation Index > Fetch the complete documentation index at: https://docs.originhq.com/llms.txt > Use this file to discover all available pages before exploring further. # Origin Console Setup: Configure Your Tenant Settings > Work through the Origin Settings panel — fleet endpoint configuration, the OTLP collector port, AI provider integrations, account credentials, and local browser data. Settings is where you configure your Origin tenant: fleet-wide agent behaviour, the AI provider integrations, users and roles, provisioning tokens, and agent downloads. Sign in at [dashboard.originhq.com](https://dashboard.originhq.com/) and click **Settings** in the far-left rail. ## The Settings panel Settings is split into seven views, listed down the left of the panel. | View | Purpose | | -------------------------- | --------------------------------------------------------------------------------------- | | **Settings** | Rules and integrations — the page described below | | **Endpoint Inventory** | Per-endpoint detail. See [Endpoint Inventory](/product/registered-endpoints). | | **User Management** | Users and roles. See [User Management](/getting-started/user-management). | | **Directory Integrations** | Entra ID, Okta, Google. See [Identity Integration](/product/identity-integration). | | **Provisioning Tokens** | Endpoint registration. See [Provisioning Tokens](/getting-started/provisioning-tokens). | | **Installers** | Agent downloads. See below. | | **Send Feedback** | Report a bug or request a feature. See [Report Issues](/kb/report-issues). | The rest of this page covers the **Settings** view itself. *** ## Identity — Your access The first card reports the scope of your own access, for example *"Covers the whole tenant · 232 endpoints."* This card is informational. It describes your intended scope — it is not a filter on the data shown elsewhere in the console. *** ## Fleet — Endpoint Configuration Agent settings pushed to every endpoint in the tenant. Changes apply on the next agent heartbeat, so you never need to touch individual machines. | Setting | Default | Description | | ------------------------- | ------- | ----------------------------------------------------------------------------------------------------- | | **Hide system tray icon** | Off | Suppresses the tray process and removes the auto-start entry. | | **OTLP collector port** | 4318 | Loopback port the agent's AI-telemetry collector binds on each endpoint. Leave empty for the default. | ### OTLP collector port Set this if your endpoints already run a corporate OTel collector — Datadog, Alloy, Dynatrace — on 4318. The port applies the next time each endpoint's agent restarts. Changing an already-configured port can briefly pause capture on macOS endpoints until each agent reconnects. If the chosen port is already in use on a host, that host won't capture AI telemetry until the conflict is cleared — coordinate the port with whoever owns those endpoints. The card shows a **Last saved** timestamp, and **Discard** / **Save** buttons. Changes are not pushed until you save. Additional fleet configuration is available with the **AI Visibility** feature. If your tenant doesn't have it, the options above are the full set exposed in this card. *** ## Integrations — Anthropic Compliance API key Lets Origin pull your organization's `claude.ai` and Claude Desktop chats through Anthropic's Compliance API, so they appear alongside proxy-captured prompts. Paste a Compliance Access Key — it begins with `sk-ant-api01-` and is created in claude.ai under Compliance Access Keys. The key is stored encrypted and never shown again after saving. Once configured, the card reads **Configured — connected** and offers **Remove** and **Replace key**. For the full setup walkthrough, including the Claude-side steps and the scopes Origin needs, see [Claude Enterprise](/product/claude-enterprise). *** ## Integrations — Microsoft 365 Copilot capture Pulls Microsoft 365 Copilot prompts and responses (Word, Excel, Outlook, Teams, Copilot Chat) into AI activity, attributed to each person. Copilot capture is enabled **per connected Microsoft Entra ID directory** — each appears as its own card — and needs no extra credentials beyond the directory integration's admin consent. Each card carries a **Capture Copilot activity** toggle, a delivery mode, and a **Readiness** section with a **Check readiness** / **Re-check** button that makes live Microsoft API calls. Turning the toggle on is not sufficient on its own. Capture stays blocked until the Microsoft-side prerequisites pass, so run the readiness check after enabling. For prerequisites, the APIs involved, and troubleshooting, see [Microsoft 365 Copilot](/getting-started/microsoft-365-copilot). *** ## Account — Change Password Set a new password from the **Current password**, **New password**, and **Confirm new password** fields. New passwords must be at least 8 characters. This only applies to local password accounts. Users who sign in via SSO / WorkOS manage credentials at their identity provider. *** ## Local storage — Clear local data Wipes locally-cached data from the browser you're using, without signing you out. This affects that browser only; server-side state is unchanged. | Item | What it clears | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | **Chat history** | Conversations and prompts saved in this browser. Local kernels, canvases, pins, and pending cloud-recovery data are preserved. | | **Workflows** | Workflow definitions and run history saved in this browser. | | **MCP credentials** | OAuth tokens and API keys for Linear, Notion, Zapier, and other MCP servers. | *** ## Installers The **Installers** view lists the agent packages available for download. It shows the three latest builds by default, with a **Show all versions** toggle and a search box. | Column | Description | | ---------------- | ------------------------------------ | | **Platform** | macOS or Windows | | **Architecture** | Universal for macOS; x64 for Windows | | **Format** | PKG, MSI, or EXE | | **Version** | Agent version | | **Published** | When the build was published | | **Size** | Download size | | **SHA256** | Digest for verifying the download | Both an **MSI** and an **EXE** are published for Windows. The MSI is the right choice for MDM and software-distribution tooling; the EXE installs the Visual C++ redistributable automatically and suits ad-hoc installs. See [Windows Install](/getting-started/windows-installation) for the difference. Installers are downloaded here, but the **provisioning token** an agent needs to register is generated under **Provisioning Tokens** — a separate view. See [Provisioning Tokens](/getting-started/provisioning-tokens). ## Next steps Add users and assign one of Origin's eight built-in roles. Create the token each agent needs to register with your tenant. See which AI tools Origin captures and set up the API-based integrations. Install on macOS and Windows, manually or via MDM.