Set up Copilot

At the end of this guide, Copilot answers questions with the AI service you chose. You can add more than one service: users then choose which one answers.

Before you start

• An administrator account, or a role with full access to Copilot settings and usage (the built-in IT Administrator; the Auditor may only read). See Users and roles.
• An account with one of these services:

• For a cloud service, the hub needs outbound HTTPS access to that service.

A Claude.ai or ChatGPT subscription cannot be used: Copilot signs in with an API key or with your company's cloud account. API use is billed separately from those subscriptions; add credit in the service's billing settings before you test.

Choose a sign-in

With Cloud Identity, the hub uses the identity it runs as:

With Service Credential, enter the identity and its secret:

Add a service

1. Open Platform > Copilot Settings and select New.

2. Enter a Name that users will recognise, for example Claude or Local model.

3. Choose the Service. Each service shows its logo. Sign-in and Model are filled in with the usual choice:

   Service	Suggested model
   Anthropic Claude	claude-opus-5-5
   OpenAI	gpt-5
   Azure OpenAI	none: enter your deployment name
   Claude on Amazon Bedrock	anthropic.claude-opus-5-5
   Claude on Google Vertex AI	claude-opus-5-5
   Ollama (local)	llama3.2

   You can pick another model after the connection test below loads the service's list.

4. Fill in the fields the screen shows for that service: Endpoint for Azure OpenAI (and for Ollama when the server is not at http://localhost:11434; in Docker, use the address of the machine that runs Ollama), Region for Amazon Bedrock (for example eu-central-1) and Google Vertex AI (for example europe-west1), Project ID for Google Vertex AI.

5. Choose the Sign-in and enter what it needs (see the tables above).

6. Select Test Connection (see below) and pick the Model from the list.

7. Tick Default if this service should answer new conversations. Only one service is the default.

8. Select Save.

API Key Status shows where the sign-in comes from: Stored (encrypted), the environment variable it uses, or Uses the hub's cloud identity.

Test the connection and choose a model

Test Connection signs in with the settings on screen, even before you save. It then:

1. loads the models the service offers to this account into the Model list;
2. asks the chosen model a one-word question, which costs a few tokens.

Connection shows the result. It turns green when the model answered, and red with what to fix when something failed:

The key checks run before anything is sent, so a wrong key costs nothing.

Claude, OpenAI, Azure OpenAI, Ollama and Amazon Bedrock list their models. Google Vertex AI does not, so the list shows the Claude models it usually serves. Before the test, the list offers the usual models of the service (Claude Opus, Sonnet and Haiku 5.5 for the Claude services). Azure OpenAI lists the models of the resource. Its Model is the name of your deployment, which you can type.

You can still type any model name the service accepts. Changing the service, the sign-in, the key or the model clears the result, so test again before you save.

How keys and secrets are kept

• A key or secret is encrypted with the platform key as soon as you save it, the same key that protects the stored certificates (see Certificates). A copy of the database alone does not reveal it.
• It is never shown again. The field shows dots, and API Key Status shows its last four characters so you can tell keys apart. To replace it, paste a new one and save. Leaving the field as it is keeps the stored one.
• With API Key sign-in and no key stored, the hub uses the service's environment variable: ANTHROPIC_API_KEY, OPENAI_API_KEY, AZURE_OPENAI_API_KEY or AWS_BEARER_TOKEN_BEDROCK.

Decide who may use the Copilot

Each role has a Copilot tab in Security > Roles:

A user with several roles gets the most generous access and the highest limit among them. Administrators have every right and no limit. Users whose roles have no access do not see the Copilot button or the Copilot page.

To keep a service for some roles only, add them under Allowed Roles on the service. A service with no role listed is open to every Copilot user.

Prices and budget

On each service, Input Price (per 1M tokens) and Output Price (per 1M tokens) take the prices of the service's price list, in Currency (USD unless you change it). Copilot then estimates what each answer cost.

Monthly Budget caps what the service may cost in a calendar month (UTC):

• At 80 percent, a Copilot budget insight appears in Monitor > Copilot > Insights for administrators and the roles that may read Copilot settings and usage. At 100 percent it turns critical.
• At 100 percent, the service stops answering until the next month. Users can switch to another service they are allowed to use.

Leave the budget at 0 for no budget. The estimates come from the prices you entered; the service's own bill is what counts.

Usage

Platform > Copilot Usage shows, for this month, the last 30 days or the last 7 days:

• the number of answers, the tokens and the estimated cost;
• the tokens per day;
• the split by AI service, with each service's budget for the month;
• the split by user.

The records stay when a conversation is deleted. When a service does not report its token counts (some local models), they are estimated from the text and the page says so. Only administrators see this page.

Turn a service off

Clear Enabled and save. Users can no longer choose it, and conversations that used it are answered by the default service. Deleting a service has the same effect.

What reaches the AI service

For each question, the hub sends the question, the earlier questions and answers of the conversation, and the plant data that Copilot reads to answer it: device names and states, latest tag values, alarms and configuration findings. Only data the asking user may read is sent. With Ollama (local), nothing leaves the site; with Amazon Bedrock, Google Vertex AI and Azure OpenAI, the data stays in your own cloud account.

Changes that Copilot proposes are made only when the user approves them, with that user's permissions. See Changes you approve.

Conversations are stored in the hub's database. Administrators can read every conversation in Monitor > Copilot with Show everyone's conversations.

What's next

• Copilot: what Copilot can answer and do, and how changes are approved.
• Users and roles: who may use Copilot.