Settings

Watch the workflow: Inspect organization setup and evaluation controls · Authored dummy data

This authored walkthrough uses an earlier Settings layout. Its live-eval and key-metadata examples remain illustrative; the section guide below describes the current navigation. The recorded Deployment stage panel is a historical view and is not a section in the current sidebar.

Read the walkthrough transcript

• 00:00 — This Tensile demo keeps live evaluations off. No model judging is running.
• 00:05 — Inspect an organization key label and prefix. The full key is hidden.
• 00:11 — Read the demo stage coverage. These authored events are tagged staging.

Open Settings from the sidebar. It replaces the application navigation with the Settings sections. Use Back to return to your previous page. Settings applies to the workspace shown at the top of the sidebar.

Owners and admins can manage workspace configuration. Other members can inspect the settings available to their role.

PreferencesCopy Anchor Link

Choose Light or Dark under Theme. The choice is saved in this browser. If the browser cannot save it, retry from the error message.

GeneralCopy Anchor Link

• Change Workspace name, then select Save. Revert restores the saved name.
• Copy the Workspace ID with its copy button.
• Select Manage customer names to open the separate Customer names page. Names help people identify customers; filters, links and exports still use the customer ID.
• Use Live evals to control judging of completed conversations. Each judgment uses model calls. Check your workspace's operating plan before changing this switch.

MembersCopy Anchor Link

Select Invite member, enter an email address, choose an available role, and select Invite. Owners can invite owners, admins, and members; admins can invite members. The list distinguishes invited, active and suspended members. Only active owners can change roles with the inline menu. Tensile preserves an active owner.

Use the member's action buttons to suspend access, activate a suspended member, or delete their workspace membership. Each action requires confirmation. Owners can manage other members; admins can use these actions for members. You cannot use these actions on yourself. Deleting a membership does not delete the person's sign-in account or memberships in other workspaces.

Search the list by email. Sorting applies to the complete filtered list before pagination.

API keysCopy Anchor Link

These keys authenticate trace-ingestion API requests; they are separate from model-provider credentials.

1. Select Create API key.
2. Enter a Key name, such as the service or environment.
3. Select Create API key, then copy the full key. It is shown once.
4. Select Done.

Use the key in the x-api-key request header. See Authentication. The list shows safe key metadata. Select the revoke command beside a key and confirm to stop its use. If a creation result is uncertain, inspect the list before creating another key.

IntegrationsCopy Anchor Link

The overview shows Linear, Braintrust, Langfuse and GitHub. Data-source configuration is included here; older Data sources links open Integrations.

Open a source card to inspect its saved connection, projects and advanced collection settings. The breadcrumb returns to Integrations; the separate Settings Back command returns to the page that opened Settings. Select Connect for a new setup. For a saved connection, use the pencil Edit connection icon beside its name and status:

• Langfuse: host, public key, secret key, customer-ID metadata key, and optional backfill date. See Langfuse.
• Braintrust: host, API key, project IDs, project-to-environment mapping, customer/session metadata keys, and optional backfill date. See Braintrust.

Use Related configuration to open Work identity or Tensile API keys.

Select Connect or Update in the open editor. Leave an existing secret field blank to keep its saved value. The destructive Disconnect icon sits beside Edit connection and opens a confirmation dialog; Cancel leaves the connection in place. A Connected badge means the connection is stored; it does not certify current provider access or complete data coverage.

For a saved Braintrust connection, select View logs for a configured project. The project-scoped page uses /settings/integrations/logs?provider=braintrust&project=ID, where ID is that project's stored ID. Langfuse uses /settings/integrations/logs?provider=langfuse because its saved keys identify the project; there is no separate project picker. These views show bounded stored rows, not proof that the provider is accessible now or that all history arrived. Existing direct Raw Logs links and drilldowns remain available.

The Linear detail shows the saved workspace, workspace ID, teams and connection date. Connected means a saved connection; current access is not tested on page load. Owners and admins can connect through OAuth or disconnect the saved connection. Linear actions let you find and link an issue or confirm creation from a finding. Connecting does not import issue history in the background.

In workspaces with Evaluations, Evaluator analysis opens Analysis sources (/settings/integrations/analysis-sources). It lists each analysis source with its status, revision, last scan and eligible development cases, and the ten most recent analysis runs with any error and excluded counts. The same people as before can configure a source or retry a failed run. Unknown means the count was not recorded or the last scan failed; it is not zero. The Evaluations overview shows the same information.

GitHub provides staff-assisted, read-only code snapshots. Its detail shows the current limits: the workspace connection is not verified, and self-service connection and customer PR automation are not available. Braintrust and Langfuse cards open their connection forms within Integrations.

Work identityCopy Anchor Link

Choose the source and enter its exact keys for customer, related entity, workflow, role, actor, and completion time. Only authorized source administrators can save a mapping.

Select Edit work roles and actors to classify exact role and actor values from that source in the inline editor. For example, map the source value bot to Agent. Apply values updates the draft. Values that you do not map stay Unknown; a metadata key alone does not classify work.

Select Save mapping, check the bounded source window, and confirm. Tensile verifies that population before saving. A failed preview retains your input and does not save a mapping. A newer stored version requires reload before retry. Revert restores the saved mapping.

Saving requests index processing; it does not judge work or certify complete source coverage. Unknown source values remain unknown.

NotificationsCopy Anchor Link

Create a notification rule for an available stored critical check, recipient, and channel. The selected stored failure determines the critical condition. Pause or resume an existing rule from the list. Send test is available only for your own active configured destination and sends a real message. Open Delivery history for recorded outcomes, then select a rule name to inspect the exact full-page receipt and its guarded recovery actions; the breadcrumb provides a return to Notifications. A saved rule alone does not prove delivery. Existing scheduled rules retain their condition, schedule, lookback and last-triggered details. Historical replay is off by default; enabling it is an explicit notification action. Old Alerts links remain compatible.

Analysis profilesCopy Anchor Link

Open an exact profile from the list or select New profile. Set its engine, required role models, and run limits. Evaluation profiles also require their target and safety rubrics. Save a complete configuration with Save new revision.

Saved revisions are immutable. Older direct links keep their exact configuration; running work keeps its saved revision. A profile does not start an investigation or prove that a proposed change is safe. See Investigations.

Model connectionsCopy Anchor Link

Each client workspace owns its named model connections. Owners and admins can add a provider, permitted model IDs, and a credential. Saved secrets are not displayed. Leave the replacement credential blank to retain it; provide a new value to rotate it. Revoked connections cannot be reused. Access: Unknown means provider access has not been tested.

Demo API execution uses a separate route from scheduled jobs and local FDE investigations. Scheduled EC2 work does not use these workspace keys. Actual FDE investigations use local Tensile and the local Claude Code harness. Anthropic API execution is unavailable through this connection route.

Client spendingCopy Anchor Link

This section appears only for explicitly authorized operators in the Tensile control workspace. Select a client workspace to set its API-run and UTC-day limits. Set an Ask ID to configure an individual ask limit.

Defaults are USD 3 per run/ask and USD 10 per client per UTC day. Pending calls reserve budget; uncertain results keep that reservation. An ask limit cannot bypass the client's daily limit. These controls apply to the demo API admission route, not existing scheduled or local jobs.

Failed or unavailable settingsCopy Anchor Link

Use Retry when a section fails to load. Failed saves retain entered values. A workspace or role change can require reload before a write. Search can produce an empty list even when other records exist; clear the search to inspect the complete list.

Follow the Quickstart to send your first events.