Trust & control

Helpful bees. Clear boundaries.

Useful AI needs more than access to tools. It needs clear ownership, reviewable actions, and a workspace configured for the job.

A little help. A whole lot of possibility.
01

Separate the spaces

Personal and shared spaces define where conversations and context belong. Personal connected-app accounts are not inherited by Shared Spaces.

Understand spaces
02

Review consequential actions

The app includes approval controls. Outside content can cause later risky actions to be held for review, and eligible allowances are scoped to a tool and target.

  • Connected-app actions may require approval each time
  • Editing a routine can pause its allowances
  • Controls depend on the configured protection mode
Understand approvals
03

Choose where the work runs

Team Computers share files and tools within a space; Private Computers separate a bee’s workspace. Human takeover supports steps that need you.

Compare computer modes
04

Know what is remembered

Review and manage your bees’ saved context. Shared memory and optional memory providers have distinct scopes; choose them deliberately.

Review memory scope
05

Keep access accountable

The app foundation includes administrative roles, activity views, and security-related records. Availability, retention, and forwarding depend on deployment settings.

06

Ask specific questions

Confirm your deployment’s identity settings, data handling, providers, isolation, and support responsibilities. No compliance certification or absolute security guarantee is claimed on this page.

One good place to start

What could your first bee help with?

Choose a role. Give it a clear job. Build from there.

A little planning. A lot of possibility.

Build your bee team.

Choose the roles you need and give your future hive a first task.

Your teammates

Planning preview · Your brief stays on your device. No account is created and nothing is submitted.