Workspace Integrations
Definition
Open Admin → Integrations to connect workspace services. Each connection supplies a specific workflow rather than a general permission to read or write every external resource.
Fields, states, or lifecycle rules
- Messaging connections support their configured notification and test operations.
- Repository connections discover repositories accessible to the authorizing account.
- Trace-store connections supply their supported capture/import workflow.
- Training connections are selected separately by a Benchmark preparation.
- Connection state, account authorization and a successful downstream operation remain distinct.
Messaging
Slack and Microsoft Teams have provider-specific connection controls. For Teams, installation and a personal-message test are distinct operations. Workspace settings alone do not confirm installation or that automatic notifications are enabled.
Read provider errors as operational outcomes rather than treating a visible integration card as proof of delivery.
Repositories and trace stores
GitHub.com, GitLab.com and Bitbucket Cloud connections discover the repositories allowed by the account and installation. Bind the intended repository through Reference Materials and inspect its indexed content.
LangSmith and Langfuse have their own connection surfaces. Keep original record identity and scope when importing material; connected access does not approve the captured behavior.
Training and inference
Weights training selects an active service connection, supported model and compatible method. Connection checks do not certify quota, create-job permission, storage access or training quality.
Some evaluation paths require an existing callable inference deployment. A training job does not automatically allocate serving resources for every service. The deployment-to-output association can be user-reported where the adapter identifies it that way.
Credentials and resource boundaries
For setup steps and provider-specific recovery, use the integration guides. Each guide distinguishes workspace connection, Project selection and a successful downstream operation.
Use the provider's owning connection flow and approved secret mechanism. Keep access scoped to the authorized account, identity and resource. Existing Vertex and Baseten training adapters do not authorize Google platform storage, ambient developer credentials or a provider fallback.
A failed service operation should remain actionable in its owning workflow rather than being hidden by a substitute local service.