Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one
Blog post from Tyk
Tyk AI Studio governs user access through two separate mechanisms: catalogs determine which LLM providers, data sources, and tools users can see, while privacy levels determine whether visible data can be combined with a particular model. The tutorial shows that new users are automatically added to the Default team, which may expose all default catalogs, so restricting access requires both creating a narrower team with selected catalogs and removing the user from Default because team permissions accumulate rather than subtract. It also notes that newly created data sources are added to the Default catalog by default and that catalog selections must be explicitly confirmed with the interface’s plus button. In the example, a developer is limited to a single support-focused provider and sensitive customer transcripts, but an attempt to create an application using both is rejected because the data has a privacy level of 80 while the provider is rated 0. Administrators must either use a provider with an adequate privacy rating or exclude the sensitive data, ensuring that visibility of resources does not automatically permit their use together.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| LLM | 8 | 747 | 162 | 79 | -85% |
| Vector Search | 1 | 265 | 57 | 33 | -89% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.