Configuration Scenarios

The scenarios on these pages show complete configurations for typical needs of organizations. Each one names its goal, the building blocks, a configuration plugin you can start from, what your colleagues see, how you check it, and its limits.

The examples show only the parts that matter for the scenario. The header of a configuration plugin is explained in Writing Configuration Plugins. Create your own IDs for every configuration and every object; the IDs in the examples are placeholders.

The scenarios

Scenario	For organizations that …	Main building blocks
[[Local Models Only	Scenario-Local-Models-Only]]	allow no cloud service at all
[[Confidential Content on Trusted Providers	Scenario-Confidential-Content-on-Trusted-Providers]]	use cloud models for everyday tasks, but keep internal knowledge on their own servers
[[Contracted Cloud Provider as Internal	Scenario-Contracted-Cloud-Provider-as-Internal]]	have a contract that lets a cloud service handle confidential content
[[Organization-Provided API Keys	Scenario-Organization-Provided-API-Keys]]	pay for the AI models of their colleagues
[[Users Bring Their Own Keys	Scenario-Users-Bring-Their-Own-Keys]]	prepare the providers, while each person uses a personal key
[[Internal AI Gateway	Scenario-Internal-AI-Gateway]]	send all requests through a gateway such as LiteLLM
[[Standardized Workplace	Scenario-Standardized-Workplace]]	want everybody to start with the same, prepared AI Studio
[[Your Own Web Search	Scenario-Own-Web-Search]]	let the AI search the web through their own search engine

Combining scenarios

The scenarios combine well, because a device can load several configurations, see How Central Configuration Works. A common setup is a base configuration for the whole organization with the trust settings and the providers, and one configuration per department with its templates and assistants. Keep in mind that lists such as DataApp.ProhibitedProviders or DataSourceSecuritySettings.TrustedProviderIds replace each other instead of adding up.

Before you roll out

• Test every configuration on a device first, see Testing and Exporting Configurations.
• Check which version your devices run. Settings that a version doesn't know yet are ignored there, see Managing Updates.