Guides
Invite your team
Bring people into one shared Brain and workspace — with clear ownership, permissions honesty, and a first win for each teammate.
HiveBase compounds when more than one person shares the same source-backed company memory. Invite teammates so answers, tasks, and squads run from one Brain — not five private chat histories.
What “shared” actually means
| Shared | Still individual |
|---|---|
| Company Brain claims, decisions, and provenance | Personal Google / Gmail OAuth connections when required |
| Workspace tasks, receipts, and approval history | Role-lensed FYI and personal focus |
| Integrations connected at the workspace level | Private redaction defaults on personal inbox content |
| Squads and spaces your company enables | Who can change billing, integrations, or autonomy dials |
Teams gate (honest)
Multiplayer is real — invites, shared Brain, shared tasks — but fine-grained enterprise RBAC, SSO-mandated roles, and per-folder ACL theater are not the product promise of this page. Access follows workspace membership, your connected integrations, and team settings. When sources disagree about who may see what, treat the integration’s authorization as authoritative.
Invite flow
Open Team settings
Go to Settings → Team (or the invite control in workspace settings).
Invite by email
Send invites to the people who should share this company Brain. They accept and join the workspace — not a separate “copy of” context.
Confirm who can change the world
Keep integration connect, billing, and high-impact autonomy settings with owners/admins. Everyone else should still get value from ask, FYI, and task review without needing every key.
Point them at a first win
Send Get your first win in 10 minutes and, for outbound safety, First governed run.
Onboarding each role (lightweight)
You do not need a formal RACI for a five-person startup. You do need a first path so invites do not become “I logged in and stared.”
| Role shape | First path |
|---|---|
| Founder / ops | Connect sources → first Brain question → first approval on an outbound draft |
| Builder / eng | Connect GitHub → coding task or verification path → MCP if they live in Cursor |
| Customer-facing | Connect Slack or Gmail → FYI lens → review held customer-facing drafts |
| Everyone else | Ask the Brain one real question; review one task; learn Stop + receipts |
Multiplayer habits that prevent thrash
- One Brain per company workspace — avoid parallel ‘shadow’ workspaces for the same team.
- Connect high-signal tools once at the workspace level; personal OAuth only where the product requires it (e.g. individual Gmail).
- Treat approval queues as shared work: outbound holds are company risk, not personal spam.
- Prefer sourced corrections over silent rewrites when two people disagree with a claim.
- Use Spaces / projects when relevance and ownership need sharper walls — see Spaces & projects.
Permissions & data (pointer)
Who can see what is governed by team settings and connected integrations. HiveBase only sees tools someone authorized; disconnect stops future reads.
Full matrix: Trust & safety → Permissions & data access.