{"query":"Workspace Integrations","corpusVersion":"local","generatedAt":"2026-11-02T05:38:18.610Z","results":[{"blockId":"admin-console.integrations#workspace-integrations","pageId":"admin-console.integrations","title":"Workspace Integrations","pageTitle":"Workspace Integrations","url":"https://teammately.ai/docs/admin-console/integrations.md","humanUrl":"https://teammately.ai/docs/admin-console/integrations#workspace-integrations","markdownUrl":"https://teammately.ai/docs/admin-console/integrations.md","sectionId":"workspace-integrations","kind":"reference","productArea":"admin_console","score":1038.7821945130986,"reasons":["search_match","title_match","display_title_match","term_match"],"markdown":"# Workspace Integrations"},{"blockId":"integrations.langsmith#connect-the-workspace","pageId":"integrations.langsmith","title":"Connect the Workspace","pageTitle":"Import Inputs from LangSmith","url":"https://teammately.ai/docs/integrations/langsmith.md","humanUrl":"https://teammately.ai/docs/integrations/langsmith#connect-the-workspace","markdownUrl":"https://teammately.ai/docs/integrations/langsmith.md","sectionId":"connect-the-workspace","kind":"quickstart","productArea":"data_integrations","score":410.33658877272967,"reasons":["search_match","term_match"],"markdown":"## Connect the Workspace\n\n1. In LangSmith, create the service key in **Settings → API Keys**.\n2. Copy the Workspace ID from **Settings → General**.\n3. Open **Admin → Integrations → LangSmith** in Teammately.\n4. Choose a descriptive **Display name**, enter the matching Workspace ID, key and endpoint in **Connection setup**, and add the connection.\n\nThe Teammately workspace uses one LangSmith Workspace connection. Rotate credentials on the existing connection instead of changing its intended scope accidentally."},{"blockId":"admin-console.integrations#fields-states-or-lifecycle-rules","pageId":"admin-console.integrations","title":"Fields, states, or lifecycle rules","pageTitle":"Workspace Integrations","url":"https://teammately.ai/docs/admin-console/integrations.md","humanUrl":"https://teammately.ai/docs/admin-console/integrations#fields-states-or-lifecycle-rules","markdownUrl":"https://teammately.ai/docs/admin-console/integrations.md","sectionId":"fields-states-or-lifecycle-rules","kind":"reference","productArea":"admin_console","score":361.21571822471395,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Fields, states, or lifecycle rules\n\n- Messaging connections support their configured notification and test operations.\n- Repository connections discover repositories accessible to the authorizing account.\n- Trace-store connections supply their supported capture/import workflow.\n- Training connections are selected separately by a Benchmark preparation.\n- Connection state, account authorization and a successful downstream operation remain distinct."},{"blockId":"admin-console.integrations#definition","pageId":"admin-console.integrations","title":"Definition","pageTitle":"Workspace Integrations","url":"https://teammately.ai/docs/admin-console/integrations.md","humanUrl":"https://teammately.ai/docs/admin-console/integrations#definition","markdownUrl":"https://teammately.ai/docs/admin-console/integrations.md","sectionId":"definition","kind":"reference","productArea":"admin_console","score":357.2818700066298,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Definition\n\nOpen **Admin → Integrations** to connect workspace services. Each connection supplies a specific workflow rather than a general permission to read or write every external resource."},{"blockId":"governance.workspace-administration#related-objects","pageId":"governance.workspace-administration","title":"Related objects","pageTitle":"Workspace Administration","url":"https://teammately.ai/docs/governance/workspace-administration.md","humanUrl":"https://teammately.ai/docs/governance/workspace-administration#related-objects","markdownUrl":"https://teammately.ai/docs/governance/workspace-administration.md","sectionId":"related-objects","kind":"reference","productArea":"governance","score":335.21536745647376,"reasons":["search_match","term_match"],"markdown":"## Related objects\n\nRelated objects may include workspace members, groups, workspace roles, permission keys, project permission assignments, domain controls, IP controls, API keys, notification integrations, and the project artifacts those people can access.\n\n{% example-demo title=\"Human approval boundary\" %}\nA Workspace administrator manages an organization group in the Admin Console. A Project owner then grants that group access under Project Settings. The group can inspect the Project according to the current Project membership surface, but this does not change organization security controls or create authority over every governed correctness artifact.\n{% /example-demo %}"},{"blockId":"admin-console.integrations#related-task-pages","pageId":"admin-console.integrations","title":"Related task pages","pageTitle":"Workspace Integrations","url":"https://teammately.ai/docs/admin-console/integrations.md","humanUrl":"https://teammately.ai/docs/admin-console/integrations#related-task-pages","markdownUrl":"https://teammately.ai/docs/admin-console/integrations.md","sectionId":"related-task-pages","kind":"reference","productArea":"admin_console","score":325.6739912094986,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Related task pages\n\n{% related-card-grid title=\"Related task pages\" %}\n- [Reference Materials](/docs/agent-setup/reference-materials)\n- [Export, Train, and Evaluate](/docs/weights-training/exports-and-training)\n- [Fieldloop](/docs/fieldloop)\n- [Admin Console](/docs/admin-console)\n{% /related-card-grid %}"},{"blockId":"governance.workspace-administration#fields-states-or-lifecycle-rules","pageId":"governance.workspace-administration","title":"Fields, states, or lifecycle rules","pageTitle":"Workspace Administration","url":"https://teammately.ai/docs/governance/workspace-administration.md","humanUrl":"https://teammately.ai/docs/governance/workspace-administration#fields-states-or-lifecycle-rules","markdownUrl":"https://teammately.ai/docs/governance/workspace-administration.md","sectionId":"fields-states-or-lifecycle-rules","kind":"reference","productArea":"governance","score":321.2987004675855,"reasons":["search_match","term_match"],"markdown":"## Fields, states, or lifecycle rules\n\n- Project permissions in the main product use user and group subjects with `ADMIN` or `MEMBER` project roles.\n- The Admin Console exposes additional organization-level controls such as roles, domain control, IP address control, integrations, and API keys.\n- Do not infer compliance status, retention rules, SSO behavior, billing behavior, rate limits, or deployment options from the existence of an admin screen.\n- Approval actions in correctness workflows require accountable ownership; AI suggestions do not approve themselves."},{"blockId":"admin-console.integrations#credentials-and-resource-boundaries","pageId":"admin-console.integrations","title":"Credentials and resource boundaries","pageTitle":"Workspace Integrations","url":"https://teammately.ai/docs/admin-console/integrations.md","humanUrl":"https://teammately.ai/docs/admin-console/integrations#credentials-and-resource-boundaries","markdownUrl":"https://teammately.ai/docs/admin-console/integrations.md","sectionId":"credentials-and-resource-boundaries","kind":"reference","productArea":"admin_console","score":315.8388784987633,"reasons":["search_match","page_title_match","term_match","prefix_or_fuzzy_match"],"markdown":"## Credentials and resource boundaries\n\nFor setup steps and provider-specific recovery, use the [integration guides](/docs/integrations#connection-setup-guides). Each guide distinguishes workspace connection, Project selection and a successful downstream operation.\n\nUse 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.\n\nA failed service operation should remain actionable in its owning workflow rather than being hidden by a substitute local service."}]}