Manage your workspace

Manage models and service connections

A model generates an AI response. A service connection lets an installed app use an external account or API. Your personal chat provider, the models apps may use and a sensor’s service connection are separate settings. This guide helps you change the relevant one and check that the intended work can still run.

Contents

Inspect your personal model connection

In your Mind’s Portal, open Settings and find Model connection. It shows the connected route and model. Change model takes you to Chat; Change provider starts the provider connection route. Follow the offered account consent or device connection in your own browser.

Connecting a provider for personal chat does not automatically authorise installed apps to use it. An AI tool connected from outside the Portal may also use its own provider rather than a model configured on the Mind. Ways to use your Mind explains that difference.

Choose which routes apps may use

The owner can open App model access in Settings. Inspect the route, enable Apps may use only for the intended route, and list its Allowed models. Use Save app access, then reload and check the saved choices. Disabling access prevents apps spending on that route; it does not migrate them to another provider.

The app still needs its own permissions, model request and budget. Control agent autonomy explains how the different limits fit together. A model appearing in a picker does not prove an installed job has permission to call it.

Inspect services separately

Open Settings → Connections for external services and keys. Use the named connection required by the app, test it, then inspect which apps have its grant. Bringing information in covers the Google consent and API-key routes.

A successful connection test establishes reachability. To check the whole setup, wait for an authorised normal run and inspect the app’s actual output. Keep the connection, run and saved-output results separate.

Change a route without losing track of work

Before disconnecting a provider or service, identify the installed jobs that depend on it. Pause affected recurring work when needed. Agree the replacement route, its model and spending boundary, then check a small allowed task before resuming the full schedule.

If a call is refused, read the actual reason. A route may be absent, a model disallowed, a budget exhausted or the service unavailable. Repeatedly adding credentials will not repair a missing app permission. Ask the owner or installer to correct that specific boundary.

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Manage models and service connections

Guides · Manage your workspace · [How it works](https://app.mensara.ai/how-it-works)

[Page as Markdown](https://app.mensara.ai/how-it-works/model-connections.md)

[Operating procedure](https://app.mensara.ai/how-it-works/model-controls-procedure)

## Inspect your personal model connection

In your Mind’s Portal, open **Settings** and find **Model connection**. It shows the connected route and model. **Change model** takes you to Chat; **Change provider** starts the provider connection route. Follow the offered account consent or device connection in your own browser.

## Choose which routes apps may use

The owner can open **App model access** in Settings. Inspect the route, enable **Apps may use** only for the intended route, and list its **Allowed models**. Use **Save app access**, then reload and check the saved choices. Disabling access prevents apps spending on that route; it does not migrate them to another provider.

The app still needs its own permissions, model request and budget. [Control agent autonomy](https://app.mensara.ai/how-it-works/control-agent-autonomy) explains how the different limits fit together. A model appearing in a picker does not prove an installed job has permission to call it.

## Inspect services separately

Open **Settings → Connections** for external services and keys. Use the named connection required by the app, test it, then inspect which apps have its grant. [Bringing information in](https://app.mensara.ai/how-it-works/connections-and-capture#connect-the-account-as-its-owner) covers the Google consent and API-key routes.

## Change a route without losing track of work

## Related

- [Understand settings](https://app.mensara.ai/how-it-works/mind-settings#models-and-spending)
- [Understand usage, budgets and costs](https://app.mensara.ai/how-it-works/usage-and-costs)
- [Bring email, calendar events and files into your Mind](https://app.mensara.ai/how-it-works/connections-and-capture)
- [Pause, upgrade or remove an installed agent](https://app.mensara.ai/how-it-works/manage-an-agent)

Previous page: [Control agent autonomy, budgets and access](https://app.mensara.ai/how-it-works/control-agent-autonomy)

Next page: [Understand usage, budgets and costs](https://app.mensara.ai/how-it-works/usage-and-costs)

Usage records what was consumed.

[Join the waitlist](https://app.mensara.ai/#waitlist)