Braintrust support

Last updated date:

Connect, reconnect, and troubleshoot Braintrust without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the exact Braintrust organization and its US or EU data-plane URL.
  • Create a service token in a read-only group whenever organization policy supports one; otherwise use a deliberately scoped personal key.
  • Include ACL, user, group, and role reads so Seedling can diagnose access without claiming complete native projection.
  • Do not send Braintrust credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Braintrust access controlBraintrust's organization access-control guidance.

2. Connect Braintrust

  1. In Seedling, open Connections and choose Braintrust.
  2. Choose personal or workspace scope deliberately; Seedling never promotes an actor-owned connection into workspace access.
  3. Enter the API key or service token, the correct US or EU API base URL, and an optional organization label.
  4. Seedling verifies the organization and available projects, then stages bounded ACL, user, group, and role context without treating it as a complete per-object audience.
  5. Allow the first Braintrust synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Braintrust token rejected
Confirm the braintrust token is active, was entered without surrounding whitespace, and belongs to the intended Braintrust account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Braintrust population as empty.
Wrong account or scope
Disconnect before retrying with the intended Braintrust identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the project or object remains visible to the token's permission group in the selected organization.
  2. Check the US/EU API host, project ACL, archived state, and object-specific read capability.
  3. For a personal connection, confirm the requesting member owns the exact connection; for workspace access, check the restricted connection policy.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement braintrust token for the same Braintrust account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old braintrust token in Braintrust.