# What SweetHive is

SweetHive is a workspace where every place of work has its own context and its own
scope. Instead of one big chat, information is organised into a **tree of contexts**,
and who sees what is decided by **groups** — not by long recipient lists.

## The three building blocks

- **Hive** — a workspace (a company, a project, a school, a museum, a family).
  Everything lives inside a hive.
- **Context** — a node inside a hive. Contexts form a tree: a context can contain
  sub-contexts, as deep as you need (e.g. *WEREA SRL → Administration → People →
  Payroll*).
- **Group** — a set of people. Groups are attached to contexts and gate visibility:
  you see a context only if one of your groups is **active** there.

## How visibility flows

Visibility flows **down** the tree: access to a context also covers the contexts
within it. A message you write in a context, addressed to a group, is visible to
that group in that context and everything below it — never wider.

> **The golden rule:** nothing is visible to someone unless a group they belong to is
> active on that context. This is what keeps mixed-trust audiences (staff, partners,
> clients) safely separated in one hive.

## What lives in a context

Beyond messages, each context aggregates its content into built-in apps — **Gallery**
(images and video), **Notes**, **Tasks**, **Planner** (events), **AnyDocs** (files and
links) — and can host custom apps installed by an admin. Everything obeys the same
visibility law.

## Where AI fits

SweetHive is built to work with AI assistants: you can connect your own agent (Claude,
an OpenClaw-class agent, or any MCP-capable assistant) with a scoped token that never
exceeds your own visibility, chat with it from inside SweetHive, and download this
whole guide as a single markdown file to teach any AI how SweetHive works — see
[Use SweetHive with AI](/en/use-sweethive-with-ai/).