1Password: what this connector can do

Member·4 minutes to read

What this page is for

docs/connectors/onepassword.md is the setup guide for whoever runs your organisation's Botseon deployment — creating the vendor application and entering its credentials. This page is the other half: what 1Password actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at 1Password.

Share chosen vault items with a bot: it can fill them and can never read them.

What a bot can do with it

Read — 1Password tells a bot things, nothing changes

Tool	What it does
`onepassword.list_vaults`	List the vaults this connection can see.
`onepassword.list_items`	List a vault’s items with their URLs and the names of their fields.
`onepassword.get_item`	Read one item’s title, category, URLs and field names. Never a field’s contents.

When you connect a bot from the desktop app, 1Password gets a vault of its own for that bot and a service account that can only read that one vault and expires. Put in it only the logins the bot may use. The bot sees their names and websites; a password is read only when you approve a sign-in, and goes straight into the bot's browser.

Write

This connector has no write tools yet. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

Share chosen vault items with a bot: it can fill them and can never read them. Nothing outside that list is possible through this connector, however a bot is asked to use it.

1Password is also only ever as wide as the scopes your organisation's connected app actually requests — the exact scopes are on the operator's own setup page, docs/connectors/onepassword.md, because narrowing or widening them is a decision for whoever runs your deployment, not for this page.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press the ✕ next to the account (its label is "Remove account" and the name of the account), then Revoke and remove to confirm — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At 1Password

Removing the account in Botseon also asks 1Password to revoke the token, when this deployment's connector is configured with a revoke URL. Confirm the grant is actually gone by opening 1Password's own account settings — the connected-apps, security or authorised-apps page covers it — and removing Botseon there too if it still shows up. That is also where you can revoke access without going through Botseon at all, which is worth knowing if you ever lose access to your Botseon account.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.