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

​
Chat Defaults

Settings → Chat Defaults controls which connections are pre-selected when a member starts a new chat. 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.

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

​
Usage analytics

Organization → Usage shows how much of Metal your firm is using. Metal writes one snapshot per org each day (UTC), so numbers refresh once a day. If the last snapshot is behind, the card shows a Stale badge with the snapshot date. The page has three cards:
  • Total Files — the number of files indexed in your firm’s data room, out of the total ingested.
  • Pages Processed — the number of document pages Metal has processed for extraction and search.
  • Agent Tokens — provider-reported tokens used by Metal agent runs. The headline number is the total, with a second line breaking it down into input, output, and cached tokens (cache creation + cache read combined).
Agent Tokens counts tokens reported by the model provider for Metal agent runs only. It excludes provider-side estimates and reconciliations, and it does not include tokens spent on workflow runs or document ingestion.

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