Models by Region
Give the members of each region the models they may use: for example, the EU team only on models hosted in the EU, with its own model for MINEO's helpers, while the rest of the organization keeps the usual ones. Everything is configured by organization administrators.
The Models → Regions tab is available while Only your own API keys (BYOK) is enabled in Models → General.
How it works
- Regions are off by default: turn them on with Enable regions in Models → Regions. Off, nobody's region applies.
- Each member may have one or several AI regions, in order. A region is any country (Mexico, India, the United States…), the European Union as a whole, or Global (provider direct): type to search it in the list. Members without one use the organization's settings.
- A country and its bloc can go together: a member in Germany with Germany, European Union may use the models hosted in either, and an assistant that has both prefers the one in Germany (see Members with several regions).
- Models → Regions sets, per member region, which regions' models its members may use.
- Models → Defaults has one column for the Organization — everyone — and one per member region. A region's column overrides only what you fill in: an empty cell inherits the organization's.
- Every model runs in one or several regions. Most MINEO models are Global (provider direct): served by the provider wherever it runs them. Your own models may run in several, each with its model ID, set in the Regions tab of the model's page: a member uses the one of their region (see One model in several regions).
Set it up
- Turn regions on in Models → Regions (Enable regions): they are off by default, and off nobody's region applies.
- Create the models of the region, with Only your own API keys on: under Models → Models, and set where each one runs in its page's Regions tab — for example, an Azure OpenAI deployment in the EU, on an EU credential. MINEO's models already say where they run.
- Assign the members' regions in Team → Members: the AI regions column, or select several members and use Assign AI regions. Filter the column to review who has which.
- Open Models → Regions again. The regions any member has already have a row under Member regions; + Region adds another one (search the country), and the × removes one — with members, it asks first and saving takes the region away from them. Click a row's member count to see who has it.
- In the region's row, May use models of: pick the regions of the models its members may use — for example, EU only; the regions the organization has models in come first. Empty: any region. Save. MINEO asks first when a region with members is left without any chat model: its members would get no answer.
- Open Models → Defaults (with Only your own API keys on). In the region's column:
- Pick the models that differ for them: MINEO's helpers, compaction, images, dictation and reading aloud. Each empty cell says what it inherits.
- Use the switch to turn a feature off for them — for example, image generation.
- Save.
Members with several regions
Give a member more than one region when they work across them — typically the administrators who set up assistants for everyone.
- Models they may use: the ones any of their regions allows. A region whose May use models of is empty allows any region, so it lifts the limit of the others. A member without a region has no limit: to keep someone to some regions, give them a region.
- Default models and switches: the ones of their first region. In Models → Defaults, a member counts in that column only, and the column's member count opens exactly those members in Team → Members; Models → Regions counts everyone who has the region, first or not.
- Assistants: an assistant runs on one of its models of the member's first region; if it has none, on one of the next region, and so on. The chat's model picker lists them in that order, and the member can still pick another.
Who configures an assistant
The assistant form lists only the models whoever edits it may use themselves — the ones of their regions and the ones assigned to them — so what they pick is what they then see in the chat. To set up an assistant for several regions, the editor needs those regions (or none).
A lock on a model in Available models means the assistant has it but you cannot use it: it is of another AI region, or assigned to other members. Someone else added it. You can neither remove it nor add it again, and saving the assistant keeps it for the members who can use it; hover the lock to read why. The Default model may be one of them too: it is shown by name and stays until you pick another.
What your members see
| With a model of their region | Without one | |
|---|---|---|
| Conversations and Work | Run on the assistant's models of their region | The composer says the assistant has no model available to them |
| MINEO's AI helpers | Use the region's helpers model | The wands are disabled and their tooltip says why |
| Images | The region's image model, or the assistant's if it is of their region | Not generated |
| Dictation and reading aloud | The region's voice models | The buttons are disabled and their tooltip says why |
A region's settings apply when its members use AI and when they pick the models of an assistant, never to what administrators configure for the organization. Administrators with a region are restricted like any other member. Activity → Events records who changed a member's region, and each save of Models → Regions or Models → Defaults with every column it changed, as it was and as it is.
Next steps
- Organization settings → AI — every AI setting of the organization.
- Use only your own API keys — no request on MINEO's keys.