One shared brain for the whole company.

A 1Presence has always belonged to one person. Now it can belong to a company.

Everything a personal 1Presence does — remembering what matters, keeping a vault of your work, reaching into your connected tools, making the documents and dashboards you ask for — a team can now do together, on top of shared knowledge that grows as the company works. This is the self-service tier: you set it up yourself, in minutes, by chat, the same way you do everything else here. For a bespoke, done-for-you build — a branded assistant on your own website, or 1Presence woven into your own product — see 1Presence for Business.

Work and life should not bleed into each other. So a member of an organisation carries two spaces under one login — their own private 1Presence, and the company's — with a single, unmistakable switch between them. Every screen makes it obvious which one you are in: the whole app takes on the company's colour in org context and returns to your own when you switch back.

The line is real, not cosmetic. Your personal vault, memory and connections are never visible in the company's space, and the company's are never visible in yours. Nothing crosses the boundary by accident, in either direction.

Invite colleagues by email. They join with their own account, and each person has a role that decides what they can do:

Invitations are safe by design: a link is bound to the address it was sent to, so a forwarded invite cannot enrol the wrong person, and it quietly expires if unused. Change anyone's role, or remove them, whenever you like.

A company's shared knowledge should not be flat — Sales should not have to wade through Legal's files, and a confidential project should stay confidential. So an admin gathers people into teams, and each team is given its own corner of the shared vault and memory — the way you would give different departments different drawers of one filing cabinet. A person's access is simply the sum of the teams they are on; it is enforced whenever 1Presence reads or writes, not left as a polite suggestion.

Each team also chooses how it uses the company's shared memory — the living context the organisation builds up as it works. It comes down to two independent switches — what a team reads and what it writes — each either shared with the company or kept to the team. That gives four simple postures:

An isolated team is not a hidden slice of the company's memory — it keeps its own separate memory, walled off in both directions, for the work that must never commingle with the rest of the company.

The tools you connect for work — your email, calendar, drive, notes — live in the organisation's own space, separate from your personal connections and usable only by your own agents in the org. An admin never acts through your account or reads your inbox on your behalf; where a service has its own per-person permissions, 1Presence keeps to them, so you only ever reach what that service already lets you reach.

An admin can draw the company's edge explicitly: name your Google Workspace or Microsoft 365 domain once, and the organisation will only accept work accounts on that domain — a stray personal account cannot wander in. Point the org at your company's Notion workspace and members can connect that workspace here and no other, while each person still sees only the pages they are allowed to.

Anything you make inside the organisation — a dashboard, a workflow, an agent, a routine — starts private to you, so you can shape it in peace. When it is ready, one plain control hands it to the teams you choose or to the whole company, and a quiet label on every card tells you at a glance how far it reaches: just you, a team or two, or everyone.

Sharing only ever changes who can see something — it never hands anyone access to data they could not already reach. In a conversation, a shared agent stays within what each person is allowed to see. In a workflow you set up, it does the job you designed and shows people only the result — so a colleague can run your Monday brief without being able to open its agent in chat and read everything it touches.

And a shared document remembers the many hands on it: every file notes who created it and who changed it last, the original author is never overwritten by a later edit, and rolling back to an earlier version remembers the people exactly as they were. This is the same private, by-name sharing a personal 1Presence has — see Collaboration — extended across the whole company.

Billing is deliberately boring. The organisation pays per person, and every seat quietly drops a share of credit into one shared wallet the whole team draws from — a heavy week for one colleague is covered by a quiet week for another, with no stranded allowances and no per-person true-ups.

An admin can see exactly where the month is going — a day-by-day picture for the whole org and for any one member — and read one honest bill. A member's own private 1Presence stays entirely their own, billed separately and never mixed in.

Teams is available now and metered from day one; per-seat pricing is being finalised. To set your company up or talk through what a team would cost, see pricing or reach us at [email protected].