Skip to main content
Settings hold both your personal preferences and (for admins) firm-wide configuration. Open Settings from your profile menu in the bottom-left of the sidebar, or press ⌘ ,. Both open Account → Profile. Choose how Metal looks under Appearance. Use Back to app to return, and Search settings to jump to a section.

​
How settings are organized

Account settings are available to everyone. Firm-wide settings (Firm Guidance, Firm Knowledge, most of Organization) require an admin role.

​
Appearance

Settings → Appearance controls how Metal looks for you. Metal saves your choices in your browser, so they apply only to you and the browser you set them in.
  • Mode. Choose Light, Dark, or System. System follows your operating system’s setting.
  • Color. Choose one option from either group. Choosing a palette or a theme replaces your previous color choice.
    • Palettes keep Metal’s default look and adjust the neutral tones of the app interface: Balanced, Slate, Sage, Stone, Zinc, Gray, Mauve, Olive, Mist, and Taupe.
    • Themes recast backgrounds, surfaces, accents, and chart colors in both light and dark mode: Neutral (the default), Linear, GitHub, Rose Pine, Nord, Catppuccin, Codex, Dracula, Gruvbox, Solarized, and Tokyo Night.
Each option shows a preview in your current mode.

​
Permissions

Settings → Account → Permissions controls when chat asks before running tools. These settings apply only to you.
  • Default mode. Choose Ask (the default), Auto, or Allow all. Every chat uses this mode unless the chat has its own override. See Control tool permissions in chat for what each mode does.
  • Saved approvals. Lists the standing approvals you granted by choosing Always allow on a tool request. They apply across all your chats. Delete an approval to remove it. Chat then asks again the next time it wants to use that tool.

​
Chat Preferences

Settings → Account → Chat Preferences controls which connections are pre-selected when you start a new chat. This setting applies only to you. Pick one of two options:
  • Use firm default. New chats start with the connections your firm set in Chat Defaults. If your firm hasn’t set any, new chats use Metal’s default. The page shows the connections your firm set; a connection you have not connected is skipped when a chat starts.
  • Choose my own. New chats start with the connections you pick. You use the same controls as the firm’s Chat Defaults page: turn on Enable all connections by default, or select specific connections. At least one connection must remain selected.
When you switch to Choose my own, the picker starts from your firm’s current selection. Click Save changes to apply your choice. After you save your own selection, later changes to the firm’s Chat Defaults no longer affect your new chats. Switch back to Use firm default to follow the firm again. New chats from Home and the sidebar chat use your own Chat Preferences first. If you haven’t set any, they use the firm’s Chat Defaults, then Metal’s default. You can still add or remove connections in any individual chat. To open this page from Home or a chat panel, open the Connections menu (or the context popover) and click View my defaults. The link appears on Home, the sidebar chat, and the standalone chat page; project chat and the workflow builder don’t show it.

​
Chat Defaults

Settings → Chat Defaults sets the firm default for which connections are pre-selected when a member starts a new chat. Members who choose Use firm default in Chat Preferences follow this setting. Members can override it for themselves by choosing Choose my own. Any connection your organization has configured can be picked as a default, including the Firm Knowledge connection, Web, and any external MCP server added under Integrations. Two controls live on this page:
  • Enable all connections by default. When this toggle is on, every new chat automatically uses every connection available to the member who starts it, including connections added to the organization after the setting was saved. The per-connection checkboxes are disabled while this toggle is on.
  • Per-connection checkboxes. When the toggle is off, pick the specific connections you want pre-selected for new chats. At least one connection must remain selected.
A default that a specific member cannot access (for example, an MCP server they haven’t connected under Settings → Connections) is silently skipped for that member’s chats rather than blocking the send. Members can still add or remove connections in any individual chat. Chat Defaults only sets the starting state. Each member can also set their own starting connections for the new chats they start. See Chat Preferences.

​
Email Domains

Settings → Email Domains controls where workflow emails can go and which branded addresses they can come from. This page requires an admin role. It has two sections:
  • Allowed recipient domains. The external domains that the Send email and Send calendar invite steps can deliver to.
  • Branded email domains. Verified custom domains and the addresses on them, used for ingestion, agents, and custom From addresses on workflow sends.

​
Allowed recipient domains

Workflow email steps always deliver to users in your organization. To let them reach people outside your organization, add those people’s email domains to this list. Metal skips any recipient who is neither an org user nor on an allowed domain, and lists the skipped addresses in the step result. To edit the list:
  1. Open Settings → Email Domains.
  2. Under Allowed recipient domains, enter domains in Recipient domains. Put one domain per line, or separate domains with commas.
  3. Click Save changes.
For example:
A few rules apply:
  • Each domain allows any address at that exact domain. Subdomains are not included, so add mail.example.com separately from example.com.
  • Enter bare domains only. Metal rejects email addresses, URLs, and wildcards such as *.example.com. A leading @ is removed, and domains are saved in lowercase with duplicates removed.
  • Leave the list empty to restrict workflow email to org users.
  • Metal checks the list when each step sends, not when you save the workflow. Changes apply to the next run of existing workflows.

​
Data retention

Settings → Organization → Data Retention sets how long your organization keeps conversations. Use it to preview how many conversations a retention window would cover. Retention runs in dry run only, so Metal doesn’t delete any conversations.
Only the Metal team can see and change this page. Org admins don’t see it in settings. To set or change your retention window, contact your Metal representative or support@metal.ai.

​
Choose a retention window

Under Keep conversations for, choose one of these windows and save:
  • Forever (the default). Metal keeps all conversations.
  • 1 year (365 days).
  • 6 months (180 days).
  • 30 days (the minimum).
The window applies to web chats, Slack threads, and Teams threads, along with everything Metal produced in them.

​
Dry run

Saving a window shorter than Forever starts a dry run. Nothing is deleted. The status card shows a Not deleting yet badge and how many web chats, Slack threads, and Teams threads are older than the window today. Each night, Metal records which conversations the window would cover. To stop the dry run, choose Forever and save.

​
Usage analytics

Organization → Usage shows what your firm does with Metal, live and over time. Only admins can open this page. The dashboard includes:
  • Live activity. A feed of the last 15 minutes, with actions, people active, and AI tokens, plus a per-minute chart.
  • Time range. Choose 24h, 7d, 30d, 90d, or 12m. The range applies to the KPIs, chart, leaderboard, and breakdown cards. The default is 30d.
  • KPIs. Active people, then one card for each live metric, such as AI tokens, Agent runs, Workflow runs, Tool calls, and MCP tool calls. Each metric card shows its change against the previous period and a sparkline; Active people is a count of the people who used Metal in the range and has no period comparison.
  • Usage over time. A chart of activity across the selected range.
  • Leaderboard. Your firm’s users ranked by actions. Actions are runs, calls, and skill uses. Work that runs without a user, such as automated workflow runs, appears as an Automations row in its ranked place. Usage by Metal staff working in your organization appears as a single Metal Team row. Neither row counts toward people active, but their usage is still included in every total.
  • Automations. What’s behind the leaderboard’s Automations row (usage with no acting person), broken down by agent, workflow, tool, skill, and direct AI task. Rank the top 10 by tokens (the default) or by actions. Hover a row to see exact counts and shares. Workflows, tools, and skills show no tokens of their own because their tokens count under the agent that ran them. A workflow row includes the runs and tokens of the agents it started. Click the row, or press Enter or Space, to expand it and see those agents listed under it; agents recorded before that link still list as separate rows. Agent tokens recorded before usage was linked to agents, or by a run with no agent name, show as one Unattributed agent tokens row. The card’s action total matches the leaderboard’s Automations row.
  • Breakdown cards. Surfaces shows actions by where they happened, such as Chat, Workflows, API, or MCP. Workflows, Agents, Skills, Tools, MCP tools, and Models break down each metric by workflow, agent, skill, tool, or model.
  • Activity calendar. A year of daily activity, with total actions and the number of active days.
  • Library. Total Files in your firm’s data room and Pages Processed for extraction and search. These counts come from a daily snapshot, and the card shows the snapshot date. If the snapshot is behind, the card shows Usage data may be outdated.
AI tokens replaces the old Agent Tokens card. Open the Models card to see token usage by model.

​
Common tasks

Members

Add teammates and manage teams.

Integrations

Connect CRM and file storage.

Taxonomy

Configure deal stages, statuses, and labels.

Custom Attributes

Add firm-defined fields on companies, deals, people, and activities.

Enrichment

Choose what Metal enriches automatically.

Financial Metrics

Define custom financial metrics for extraction.

Deal Profiles

See how Metal groups deal history for similar deals and benchmarking.

Dashboards

Edit dashboard layouts and add widgets from the gallery or library.

Skills

Create, share, import, and export playbooks for chat and agents.

​
Skills

Skills and Firm Skills are managed on their own settings pages. Both list the skills in scope with tabs for All, User, Firm, Shared, and System. Alongside creating and editing skills, you can move one between environments as a .skill bundle. A .skill bundle is a Claude-compatible zip archive containing the skill’s SKILL.md, any companion text files, and binary assets. Bundles are portable across Metal workspaces and other Claude-compatible tools.

​
Export a skill

Export writes the current skill to a .skill file you can share, back up, or move to another workspace.
  1. Open Skills (or Firm Skills for admins) in settings.
  2. Find the skill in the table.
  3. Click the download icon in the actions column.
The file downloads as <skill-name>.skill. System skills cannot be exported.

​
Import a skill

Import creates a new skill in the current scope from a .skill file.
  1. Open Skills (or Firm Skills) in settings.
  2. Click Import above the table.
  3. Choose a .skill file up to 10 MiB. See Size limits for the full breakdown.
Importing from Firm Skills creates a firm-wide skill and is limited to the Admin role. Importing from Skills creates a personal skill and is available to any user.

​
Overwrite on name conflict

If a skill with the same name already exists in scope, Metal opens an Overwrite confirmation dialog instead of creating a duplicate. Confirming Overwrite replaces the existing skill’s content, companion files, and assets with the imported bundle. Metal keeps the skill’s id, owners, visibility, and creation date, and clears any recommendation history tied to the previous content. Click Cancel to keep the existing skill unchanged and rename the bundle before importing again.