From one person to a whole company.

A company's 1Presence starts with a single tap.

1. 1

   Open the switcher and create

   From the context switcher — the little identity control on the rail — choose Create organisation. Give it a name and pick a colour; that colour becomes how everyone knows, at a glance, that they are working in the company's space and not their own.

2. 2

   Let it provision

   In a moment the organisation has its own shared vault and its own memory — a clean, empty brain for the whole team to build on. You are its first owner.

You now hold two spaces under one login: your own private 1Presence, and the company's. The switcher flips between them, and the app changes colour so you always know which one you are in.

Open Manage on the organisation to reach the admin console, and go to the Members tab. Invite people by email — one or many at once — and give each the role that fits:

• Owner — full control, including billing. Keep at least one; you can add more.
• Admin — can invite people and manage members and teams, but not billing.
• Member — works in the organisation against the shared knowledge.

Each person accepts from their own email and joins with their own account. An invitation is tied to the address it was sent to, so a forwarded link cannot enrol the wrong person, and it expires on its own if unused. You can resend or revoke a pending invite, and change or remove anyone later.

Teams are how you decide who reaches what. On the Teams tab, create a team, name it, give it a colour, and set its access — this is the heart of the whole setup:

1. 1

   Choose the folders it can reach

   Pick which parts of the shared vault this team can read and write, from your organisation's real folders. A team only ever sees the drawers you open for it.

2. 2

   Choose how it uses shared memory

   Pick a memory posture — Open (learns from and feeds the whole company), Private writes (reads everything, keeps its own notes), Contribute (publishes for everyone from a focused context), or Isolated (its own walled-off memory). A plain-English line under each option tells you exactly what it means.

3. 3

   Add people

   On the team's People view, add members. Someone can be on more than one team; their access is simply the sum of the teams they are on. Owners and admins always see the whole organisation.

You can pre-assign people to teams right from the invite panel, so they land with the right access the moment they join. The Access view shows, in plain words, exactly what each person can open — a quick way to check nobody can reach more than they should.

On the Connectors tab, connect the tools the organisation works with. These live in the company's space, entirely separate from anyone's personal connections — and where a service has its own per-person permissions, each member connects their own and reaches only what that service already lets them.

To draw the company's edge firmly, name your Google Workspace or Microsoft 365 domain, or point the org at your company's Notion workspace: members can then only connect accounts that belong to the company, never a stray personal one.

Now just work. In the company's space, 1Presence draws on the shared vault and memory — everyone adds to the same growing knowledge instead of starting cold. Anything you make starts private to you:

When you hand something to a team or the whole company, you are only changing who can see it — never giving anyone access to data they could not already reach. More on that in 1Presence for Teams.

The Billing tab is where the organisation's spending lives. Every seat funds one shared credit pool the whole team draws from, so a busy week for one colleague is covered by a quiet week for another. You can put a monthly ceiling on any member with a single number, open any one person's page for a day-by-day breakdown, and read one honest bill for the company. Nobody is ever charged personally for company work.