1. This video explains what an administrator controls in OAIZ, and why each control is there.
Administration

How OAIZ keeps your organisation safe

What an administrator controls, and why each control is there.

Where data is processed
Two-factor sign-in
API keys
Where models run
  1. For personal data in your work, you are the data controller. OAIZ processes it for you, under the Data Processing Agreement.
  2. OAIZ's main application and storage run in Belgium.
  3. Where else data goes depends on the models, features and connected services you use.
  4. An Administrator manages the organisation's members, invitations and settings.
  5. Sharing decides who can use each workflow, and the platform videos explain it.

You are the data controller

Main storage in Belgium

The rest depends on what you use

An Administrator runs the organisation

Sharing decides who can use what

Fjord Living
Your organisation
Data controller
Data Processing Agreement
OAIZ
Processes it for you
Data processor
Belgium
Main application and storage
Models
Features
Connected services
Organisation
General
Security
Models
People
Users
Teams
API
API keys
Service accounts
Administrator
Members and their roles
Invitations
Organisation settings
  1. Two-factor authentication adds a second check after the password, from an authenticator app, a passkey or a security key.
  2. Recovery codes are the backup. Each one works once.
  3. New organisations require it for Administrators, and an Administrator can require it for Everyone.
  4. An Administrator can also reset another person's factors.

A second check at sign-in

Recovery codes as a backup

Choose who must use it

Reset someone's factors

Recovery codes
k7p2-9xqm 4hd8-wz3r m2vq-8c5t r9xa-1kfe t3nb-6ygp w5ej-2sdl
Two-factor authentication
Required for Administrators Everyone
IL
Ines LarsenMember
Reset two-factor
Factors removed
  1. Scripts and other services use an API key instead of signing in.
  2. Each key belongs to a person or a service account, and uses that account's current access.
  3. A key never asks for a second factor, and its full value shows only once.
  4. Delete a key, and it stops working. Other keys and signed-in sessions carry on.

Programs use API keys

A key has its owner's access

Shown once

Delete it to stop it

Order sync
A script on your server
Request accepted Key refused
Authorization: Bearer YOUR_API_KEY
Uses its owner's accessChange the account's grants to change what the key reaches
No second factorThe full key shows only when you create it
••••••••••••••••••••
Other keys keep workingSigned-in sessions stay as they are
API keys Create API key Delete keys (1)
NameOwnerExpires
order-sync Order syncService Account Never
sam-reports Sam HolmHuman 31 Dec 2026
  1. Each LLM call sends your prompt to a model provider. Where it is processed depends on the model.
  2. Berget AI runs four models inside the European Economic Area, and Mistral Large 4 uses Mistral's European endpoint.
  3. Other providers can process data outside it.
  4. In Models, an Administrator chooses which models Chat and workflows offer. EU only models keeps just the ones marked for EU processing.
  5. Processing details lists the model behind each AI feature, as a dated report.

Each LLM call goes to a provider

Inside the European Economic Area

Others can be outside it

An Administrator chooses in Models

See what each feature uses

Draft a reply
LLM call
Write a reply to Maya Chen about the cracked lamp shade on order 4821.
Inside the European Economic Area
Berget AIEEA data centres GLM 5.3 FlashQwen 3.8 27BKimi K3Gemma 4 31B
MistralEuropean endpoint Mistral Large 4
Can be processed outside it
OpenAI Google Cloud Anthropic xAI Groq Cerebras OpenRouter
ModelsChoose which models are available in chat and workflows.
Enable Models Feature Model Mapping
Enable all EU only models
ModelRuns onChatWorkflows
Mistral Large 4MistralOAIZ
Kimi K3Berget AIOAIZ
GPT-5.4OpenAIOAIZ
Claude Sonnet 4.6AnthropicOAIZ
FeatureModel
Workflow draftingMistral Large 4Mistral
Job repairKimi K3Berget AI
Chat compactionKimi K3Berget AI
Processing details
AI feature processing
Providers in this organisation's current feature configuration.
Download dated report
  1. With bring your own key turned on, an Administrator adds your OpenAI or Anthropic key, and OAIZ checks it before saving.
  2. Its models appear as Your account, beside the same models on OAIZ.
  3. Your provider bills those requests, and OAIZ charges nothing for them.
  4. Spend limits still count them, so a workflow on your key stops at its limit.

Bring your own key

Models on Your account

Your provider bills it

Spend limits still count

Add a provider key
OAIZ tests the key before saving.
OpenAI
Fjord Living
••••••••••••••••••••••
EU
Save key Checking Working
Enable Models
ModelRuns onChatWorkflows
GPT-5.4OAIZBilled by OAIZ
GPT-5.4Your accountFjord Living
GPT-5.4 MiniOAIZBilled by OAIZ
GPT-5.4 MiniYour accountFjord Living
Usage cost
€0.00
On your keys
€0.0033
Spend limits
Customer requests
Includes spend on your keys€50 limit
Stops at its limit
  1. Now you know where OAIZ processes your data, how people and programs sign in, and where your models run.
  2. The next videos show API keys, two-factor sign-in, model regions and your own key in the app.
  3. To go deeper, read the Security page in the docs.

What an administrator controls

Where your data is processed
How people and programs sign in
Where your models run
In the app
API keys
Two-factor authentication
LLM hosting and regions
Bring your own key