Shared and separated at the same time.
Memory needs to reach the right people and nobody else. The Apiary scopes everything across three nested levels, org, workspace, and project, so sharing is real without being reckless.
DownloadThree levels, one clear boundary each
Org is your company
The outer boundary. Two different companies never see each other's anything, enforced where the data is stored, not just in the app.
Workspace is a team
A team within your company keeps its own memory, separate from other teams, even inside the same org.
Project is the repository
Memory scopes to the specific repository or folder you are in, so a note from one repo does not surface while you work in another.
Private, shared, or group
Inside a workspace, an assistant sees only its own memories, the team's shared pool plus its own, or a named group's plus its own. You choose the lane.
The default leans private
When in doubt, The Apiary shows less, not more. You widen sharing on purpose, and it is always a deliberate, recorded action.
No manual switching
The Apiary follows the folder you have open, even across several projects and tools at once, so moving between repositories needs no extra step.
Why three levels instead of one
A flat "shared or not" toggle cannot represent how real teams work. A company has more than one team, a team works across more than one repository, and a person often has memories they are not ready to share with anyone yet. Org, workspace, and project map onto that reality directly, so a note stays exactly as wide as it should be, no wider.
Enforced at the storage layer, not just in the app
Isolation between orgs and workspaces happens where the rows physically sit, not only behind an interface. That matters because an app-level check can have a bug; a storage-layer boundary does not bend the same way. Two workspaces never share a row, a partition, or an index, no matter what screen you are looking at.
Following you without asking
Because scope resolves from the folder you have open, you never manage the project level by hand. Open a different repository in your assistant and The Apiary follows, instantly narrowing recall to that project's memory. What stays a deliberate choice is moving between the teams and companies you belong to, since that is a boundary worth crossing on purpose.
Common questions
What are the three scoping levels?
Org is your company, the outer boundary that two companies never cross. Workspace is a team within the company. Project is the specific repository or folder you are working in.
What is the difference between private, shared, and group lanes?
Private means an assistant sees only its own memories. Shared means it sees the team's shared memory plus its own. Group means it shares with a named subset of teammates, plus its own.
Why does the default lean private?
Because widening access should be a choice, never an accident. When in doubt, The Apiary shows less, not more.
Do I have to switch projects manually?
No. The Apiary reads the folder you have open and scopes to that project automatically, even with several projects open at once.
Is scoping enforced in the app or somewhere deeper?
Deeper. Org and workspace isolation is enforced at the storage layer itself, so a boundary cannot be crossed by a bug in the interface.
Keep memory in the right lane, automatically.
Install the stack and let scoping follow you between projects.
Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex
Download