Org Settings

Data Residency and Processing

Explains the preferred data residency and processing org setting, which lets an org choose the region where its AI requests are processed and stored when that region is available.

The Preferred Data Residency and Processing setting lets you choose where you would prefer your org's AI requests to be processed and stored. It applies to every template in the org.

This is a preference, not a guarantee. Stubber applies it only when the preferred region is available for that request. It is not available for every AI provider or request type, and whenever it is not available, the request uses the global setup instead.

# Regions

If the setting is not set, Global is used.

# Where it applies

The preferred region is currently available for OpenAI models used by these tasks:

• GPT Chat Task
• Summarize GPT Chat Task
• GPT Call
• Transcribe Task
• Generate Image

Requests to any other AI provider, and any other kind of AI request, use the global setup regardless of this setting.

# Choosing a region

Navigate to Org Settings and find the Preferred Data Residency and Processing section. Pick a region from the Preferred region dropdown, then Save Draft and Publish to Live.

The setting only takes effect once it is published. Saving a draft on its own changes nothing.

# Checking where a request was processed

AI tasks record which region handled each request in a data_residency object. For the GPT Chat Task, you can find it under _gpt_chat_details.data_residency in the task result.

# preferred_region

string

The region set in Org Settings: global, eu or us.

# applied_region

string

The region that actually processed the request. Empty when the global setup was used.

# fallback_reason

string

Why the preferred region was not used, when it was not. Empty when the preferred region was applied, or when no region was preferred.

# Editing in the _org template

Org Settings is the recommended place to manage this. If you need to hand-edit it, it lives under _org_settings.llm_settings.data_residency_and_processing in the _org system template, following the steps in Adding Org Settings.

preferred_region accepts global, eu or us. Any other value is treated as global.

After adding or changing the setting, publish the _org template for the change to take effect.

# Overriding for a single template

Because _org_settings is inherited, every template in the org picks this setting up. An individual template can set its own preferred_region in its own template data, for example to keep one template's AI requests in the EU while the rest of the org uses Global.