Using Botseon

This section is organised by what you are doing, not by where it lives in the product. Pick the group below that matches your task, and the page you want is in it.

The page contract

Every task page in this section holds the same six parts, in the same order, so you know what is on a page before you open it: what it does for you, in one line; what to check before you start; the steps, each with a screenshot; a worked example you can paste; a table of what can go wrong; and a short list of what to read next.

Start here

• Your first ten minutes — Your first ten minutes: sign in, answer a few intro questions, and meet your first bot.
• Sign in — How sign-in works, the provider buttons, and what each error message means.
• Finding your way — The sidebar, its three footer controls and the account menu: where every page lives.
• The member security baseline — The handful of security choices worth making in your first session, in member terms.

Conversations

• Read a transcript — Reading a transcript: threads, reactions, the model chip and exporting the conversation.
• Send a message — Sending a message: attachments, the offline queue, and what happens when a quota is hit.
• Files your bot makes — Asking for changes to a file your bot made: versions, and the "updated below" row on an older card.
• How quickly your bot answers — Short messages get quick answers without you choosing anything; a message that needs more moves to the full tools by itself.

Bots

• Make a bot, and set it up — Making a bot and setting it up: the editor, duplicate behaviour and choosing a model.
• The bot panel — The panel beside a bot's chat: its header, and the Details, Library and Computer tabs.
• What your bot's avatar is telling you — Reading a bot's avatar: what each state looks like, what it can wear, and calm mode, sound and motion.
• Give a bot a voice — Giving a bot a voice: turning it on, choosing a voice and what changes in a call.
• Share a bot with the team — Sharing a bot with the team: who can edit it, who can only use it, and how to tell.
• See what your bots are doing — Seeing what your bots are doing: every run across your bots in one Activity view, with Stop and Open.
• See what your bot is doing — The status line while a bot works: its steps, the approval card when it waits for you, and Stop.
• Hand coding work to a cloud coding service — Handing coding work to a cloud coding service: pointing a bot at one, following and cancelling jobs.
• Models, tiers and what a bot costs — Models and tiers: how Auto picks a model, which model answered, and what each bot costs.
• What your bot remembers — What your bot remembers: reading its memory, editing or deleting a fact, exporting it, and making it forget.

Groups

• Group chats — Group chats: composing to more than one bot, the recipient picker and group settings.
• Reaching a bot by email and on WhatsApp — A bot's own email address: claiming it, who may write to it, what it sends, and reaching a bot on WhatsApp.
• Bringing a bot to Microsoft Teams — Bringing a bot to Microsoft Teams: the Teams admin's approval, adding it to a team, chats, channels and threads.
• Bringing a team bot to Slack — Bringing a team bot to Slack: Add to Slack, a Slack admin’s approval, checking, resubmitting and cancelling the request.

Approvals and safety

• Approve an action — Approving an action: the card, the always-allow choice, and what each button does.
• The automatic reviewer — The automatic reviewer: which actions it checks, and what it blocks outright.

Routines and skills

• Make a routine — Making a routine: the trigger, the steps, and a checklist for building one you trust.
• When a routine stops — When a routine stops: reading the notice text and the usual fixes for each one.
• Save a process as a skill — Saving a process as a skill: the steps it keeps, Check, Output, and what needs your approval.
• Make documents and new skills with the built-in skills — The built-in skills: documents made in the bot’s computer, their previews, the skill creator, and when scripts run.
• Teach a task — Teaching a task: the consent banner, the steps recorded, and what is never recorded.

The computer

• The bot's computer — The bot's computer: the security boundary, what it can reach and what it cannot.
• Recover a computer — Recovering a computer: the least-destructive order of steps, from restart to reset.
• Run your bots' computer on your own machine — Running your bots' computer on your own machine: the connect command, its status and how to disconnect.
• Sign your bot in with your Chrome cookies — Signing your bot in with your own Chrome cookies for one site: the card, the import and what to do when it fails.
• Reach a private network from the bot's computer — Reaching a private network from the bot's computer, with the network policy still deciding every destination.
• Let a bot use one of your apps — A bot using one app on your own computer in the background: what you see, saying yes, stopping it, and app accessibility on Linux.

Plugins

• Connectors you can add — Every connector you can give a bot, listed in one place with a link to its own page.
• Install a plugin — Installing a plugin: the scopes screen, the consent step and what a plugin can see.
• Share a plugin — Sharing a plugin: the one-click link Share copies, and what the person who opens it sees.
• Import a plugin for your team — Importing a plugin for the team: its guidance, the values members give, a group limit, its link and private repositories.
• Submit a connector to the marketplace — Submitting a remote MCP server your team runs to the public marketplace, and its review.

Templates

• Share a bot as a template — Sharing a bot as a template: the scan verdict and what gets removed before sharing.
• Install a template — Installing a template: one instance per role, ready to use without extra setup.

Notifications

• Notices — Notices: the two-gate rule for a push alert, and where every notice ends up.
• Email Botseon sends you — Every email Botseon sends you, what triggers it, and how to turn each one off.
• The daily digest — The daily digest: what it summarises, when it sends, and how to change its schedule.

Account and billing

• Your account and settings — Your account and settings: the full tree, with a screenshot for each section.
• The desktop app — The desktop app: the update track, and exactly what an update does not touch.
• The phone app — The phone app: what it can do today next to the desktop app, in one table.
• Plans and the trial — Plans and the trial: what each plan includes and how long the trial runs.
• Usage, the meter and spend caps — Usage, the meter and spend caps: worked arithmetic for a typical month.
• Your phone's calendar, read by your bot — Your phone's calendar, read by your bot through the phone app once you allow it.
• Your phone's reminders and contacts, read by your bot — Your phone's reminders and contacts, read by your bot through the phone app once you allow it.
• Let your bots pay for purchases — Bot payments: turn them on, approve purchases with a passkey, pay with Link.
• Buying a plan in the phone app — Buying a plan in the phone app: the App Store or Google Play, restore, refunds, and moving to web billing.

Getting help

• Ask for help — Asking for help: what to include, what never to include, and where to find a request id.
• Frequently asked questions — Frequently asked questions: short answers, each linking to the full troubleshooting row.
• Troubleshooting index — Troubleshooting index: one row per message Botseon can show, and what it means.

Administration

• Administration — An administrator's section: members, policies, residency and fleet management, in one place.
• The administrator security baseline — The eight settings an administrator reviews before the first member signs in, and where each one lives.
• Identity and device trust — How members sign in, the identity-provider rule a bot computer needs, and what a revocation ends.
• Team Setup manifests — Manifests of setup scripts that run on every team computer: the shape, the approval and the results.
• Reaching a private network — Reaching internal services from a bot computer through a mesh or tunnel client you operate.
• Reading the security-review documents — How to read the generated compliance documents and the audit export when answering a security review.
• Downloading and updating the desktop app for a fleet — The desktop artefacts, the signed update feed and the update track, for a fleet of managed machines.
• Deploying the desktop app across an organisation — Deploy a pinned desktop app version with Jamf Pro, Kandji, Intune or a Linux package hold, and what Update required means.
• Network allowlist for corporate gateways — The domains a corporate gateway allows, and which to exempt from TLS inspection and response buffering.
• Opening the network path — The hosts to allow and exempt from TLS inspection on a secure web gateway, and the checks to run from a member's device.
• Egress IP ranges — What address a bot computer is seen from on the open internet, and what you can allowlist today.
• Members and access requests — Members and access requests: the join domain, invitations and the request queue.
• Organisation policies — Organisation policies: every control listed with the audit row it writes.
• Data residency and rights — Data residency and rights: where data is stored, the retention schedule and the DPA.
• Customer-managed keys — Customer-managed keys: put an Enterprise team under its own EU key, and what revoking it does.
• Activity export of usage — Send model usage, run errors, billing corrections and token and cost metrics to your own OpenTelemetry collector.
• Stream the audit log to an Amazon S3 bucket — Write every new audit log entry to an S3 bucket as NDJSON, with a key that may only put objects.
• Stream the audit log to Splunk — Send every new audit log entry to a Splunk index through the HTTP Event Collector.
• Stream the audit log to Sumo Logic — Send every new audit log entry to a Sumo Logic HTTP source, one JSON message each.
• Stream the audit log to an HTTPS webhook — Post every new audit log entry to your own https endpoint, signed, and verify it there.