The AI Tools Portal is curated by org admins from Settings → AI Governance → Tool catalog (Documentation Index
Fetch the complete documentation index at: https://langwatch.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
/settings/governance/tool-catalog). Anything you publish here lands on
every matching user’s /me portal grid.
Pairs with: Portal overview for the user-side tile grid, and End-user tile interactions for what each tile expands into.
Permission required:
aiTools:manage (granted to ADMIN by default; delegable via the CustomRolePermissions JSON column).Starter pack
A fresh organization has an empty catalog. Your first visit shows an Import starter pack CTA, one click publishes a sensible default set:- Coding assistants: Claude Code, Copilot, Cursor, Codex
- Model providers: OpenAI, Anthropic, Bedrock, Gemini
- External tools: empty (admins fill these in per-org with internal links)
Adding a tile
Click + Add tile to open the upsert drawer. The drawer is shaped by the type picker:
Coding assistant
| Field | Description |
|---|---|
| Display name | What appears on the tile (e.g. “Claude Code”) |
| Icon | Tile icon, slug-derived by default, overridable |
| Scope | org-wide or team:<team-name> |
| Setup command | The langwatch <tool> command shown to the user (e.g. langwatch claude) |
| Setup docs URL | Optional /ai-governance/... link for “More” |
| Helper text | Optional one-liner shown above the command block |
Model provider
| Field | Description |
|---|---|
| Display name | What appears on the tile (e.g. “OpenAI”) |
| Icon, scope | Same as coding assistant |
providerKey | Provider slug (openai, anthropic, bedrock, …) |
| Suggested routing policy | Routing policy to bind new virtual keys to |
| Default label | Pre-fills the user’s “Name your key” input |
| Project-suggestion text | Override the “building an app? create a project” hint |
personalVirtualKeys.issuePersonal with the suggested
routing policy attached, so the admin’s routing policy chain (provider
order, fallback, per-model rules) applies automatically.
External tool
| Field | Description |
|---|---|
| Display name | What appears on the tile (e.g. “Copilot Studio”) |
| Icon, scope | Same as coding assistant |
| External link | Where the tile’s CTA points (vendor portal, internal wiki) |
| CTA label | Override default “Open guide ▸” if needed |
| Description (markdown) | Admin-authored body, supports headings, lists, links, code blocks |
<img> from third-party hosts, external links
get rel="noopener noreferrer").
Scope binding
Each tile is scoped either org-wide (visible to every user in the org) or team-scoped (visible only to that team’s members). Team scoping uses the existing org-team multi-select picker.
slug with an org-scoped tile, the
team entry overrides the org entry for users in that team. This is
the recommended pattern for “engineering gets Cursor, everyone else
gets Copilot”, publish Copilot at org scope, then publish a Cursor
entry with slug: copilot (or the same slug as the team’s preferred
override) at team scope.
Reordering
Tiles in the editor are drag-to-reorder within their type section. The order is per-section, you can’t move a coding-assistant tile under the model-providers section. Order is admin-curated; the portal respects it strictly.Archive vs disable
Two soft-delete shapes:- Disable (toggle the tile to disabled state), hides the tile from end users but keeps it in the admin list, ready to re-enable.
- Archive (
archivedAtset to now), hides from both end users and admin list. Archive is meant for “we no longer offer this tool”; disable is meant for “we’re rolling this out gradually” or “we’re taking it down for the day”.
Where to next
- End-user tile interactions — what your published tiles look like to users.
- Personal IDE keys: the underlying device-flow + virtual-key provisioning that coding-assistant tiles trigger.
- Routing policies: the policy chain bound by model-provider tile virtual keys.