Stop being the only person who knows
A JustOnce shared space is a separate vault you own and invite people into — a partner, your family, a team, or the crew on one client account. You choose exactly which memories and documents go in, and each person joins as an Editor or a Viewer. Your personal vault stays private and is never shared.
Four steps, about a minute
Create a space
Name it for what it is — "Smith Household", "Acme — Client", "Support team". You own it.
Invite the people
By email, as an Editor or a Viewer. They need a justonce.ai account already — members join free.
Put things in it
Share memories from your own vault — the documents attached to them go too — or ask your AI assistant to move a whole topic across.
Close it when it ends
Archiving a space revokes the access it granted. What you shared stays in your own vault.
The household's search engine shouldn't be a person
Illustrative examples of what a shared space carries between people who live a life together.
You and your partner
One of you is the household's search engine. You know which insurer, which policy number, when the rego is due, what the plumber said last time — and the other person has to ask you. Photograph the policy once and share it into the space, and their own assistant answers instead: the excess, the claims line, and the PDF itself if they want to read the exclusions.
What goes in: Insurance policies with the original attached, the mortgage details, utility accounts, the car service history, the rating plates off the appliances, who the good tradie was.
Your family, and your parents
Two siblings, one aging parent, and a medication list that lives in somebody's phone photos. When everyone can see the same record, the person who happens to be at the appointment isn't reconstructing it from memory.
What goes in: Specialists and clinics, current medications, appointment history, who holds power of attorney, the parent's own stated wishes.
The people who cover for you
House-sitter, dog-walker, the friend feeding the cat, the babysitter who needs the after-school routine. Everything they need, none of what they don't — and you close the space when they're done.
What goes in: Alarm and bin days, vet and emergency contacts, the feeding routine, which neighbour has the spare key.
You and whoever helps you run your life
A virtual assistant, a bookkeeper, a parent helping with a move. They need a slice of your context, not your whole vault — so give them a space with exactly that slice in it.
What goes in: Travel preferences and loyalty numbers, the suppliers you use, standing instructions, the documents relevant to one project.
One space per team, per client, per engagement
Illustrative examples. Separate spaces mean separate memberships — no cross-client bleed, no over-sharing.
A small team that keeps re-deciding things
Brand voice lives in one person's head, the pricing rationale in a thread nobody can find, and the reason you rejected that approach in March is gone. Put the decisions somewhere the whole team can read them — including why, not just what.
What goes in: Positioning and tone, pricing decisions and their rationale, approaches you tried and rejected, the standing conventions.
Separate teams, one business
Engineering, GTM and support don't need each other's context and shouldn't be wading through it. Each team gets its own space with its own membership. Someone who works across two simply belongs to two.
What goes in: One space per team, with only that team's decisions, conventions and history in it.
One space per client
The agency problem: you write for Client A, then Client B, and the model starts blending their terminology and positioning. A space per client keeps each brand's context clean, and only the people on that account are in it.
What goes in: The client's brand voice, their product and competitor names, past campaigns and what happened, the account's history.
A contractor, scoped to one project
A freelancer joins for six weeks. They need this project's context and nothing else. Add them to that one space as an Editor, and close it when the engagement ends — which revokes what the space shared.
What goes in: The brief and its constraints, decisions already made, the conventions they need to follow, project-specific documents.
The handover you can never do properly
Someone leaves, or a book of accounts changes hands, and what actually mattered — what was promised, who the real decision-maker is, why this account is delicate — leaves with them. Recorded once in a shared space, it stays with the business.
What goes in: Commitments made, stakeholder dynamics, the history behind the current arrangement, renewal context.
Onboarding someone new
Instead of a week of "ask whoever's free", the new person reads the space. And because memories are bitemporal, they can see what the process was in March, not just what it is now.
What goes in: How things are actually done here, the shape of each account, the vocabulary, the things everyone assumes you already know.
Exactly what sharing does today
When a memory is shared into a space, every member can read it in the web app — and their AI assistant recalls it too. Ask Claude a question and a note your teammate shared into a space comes back alongside your own memories, clearly attributed to the person who shared it, and read-only: only its owner can change or erase it.
The precise edges: it’s your assistant’s memory search that reaches shared spaces — topic-context briefings and your core profile still draw on your own vault only. And if your sharing footprint is bigger than one search can cover, the response says so instead of quietly skipping what it missed. Your assistant can also read a whole space directly, create spaces, move memories in and out, and fetch shared documents. A document travels with the memory it is attached to: share the memory, and any member can fetch the file through their assistant or open it in the web app.
We’d rather spell the edges out here than have you find them in week two.
Three roles, and nothing you have to configure
Owner
- Everything an Editor can
- Invite people and set their role
- Remove members and change roles
- Close the space, revoking what it shared
- Be removed from their own space
Editor
- Read everything in the space
- Add and edit shared memories
- Share their own memories in
- Invite, remove, or change anyone
- Close the space
Viewer
- Read everything in the space
- Share their own memories in
- Edit shared memories
- Invite, remove, or change anyone
Your personal vault is never shared — that’s enforced in the product, not a setting you could get wrong. A shared space holds only what someone deliberately put into it, and anything can be taken back out.
Set it all up by just asking
Paste any of these into Claude, ChatGPT, or any assistant you've connected to JustOnce. They work as written.
Create a space and invite someone
Creates the space and sends the invitation. They join as a Viewer, and you can promote them to Editor in the web app.
Create a shared space called "Smith Household" and invite sam@example.com to it.
See where you already share
Lists every space you belong to, personal and shared, with its status.
What shared spaces am I part of, and which ones are still active?
Put the household paperwork somewhere you both can reach it
Searches your own vault, then shares those memories into the space so the other member can read them.
Find everything you know about our home and contents insurance, the mortgage, and the car registration, and add it to the "Smith Household" space.
Share the policy, not just the policy number
Your assistant does the reading — JustOnce runs no OCR — then saves the facts and shares that memory into the space. For the original it gives you a one-time upload link (works once, 15 minutes); the file attaches to the memory and goes with it.
Read this photo of our home and contents insurance policy. Save the insurer, policy number, excess, claims line and renewal date to JustOnce as one memory, keep the photo attached to it, and share it into the "Smith Household" space.
Ask about something your partner shared
Recall reaches the shared space: the facts come back attributed to whoever shared them, and the original file is fetched over the authenticated connection — no download link, no shared folder.
A pipe has burst. What is our home insurance excess and who do I call? Tell me who saved it, and pull up the policy.
Set a client space up properly in one go
Creates the space, invites both people, and moves the account context in — one paste instead of twenty clicks.
Create a shared space called "Acme — Client" and invite jo@myagency.example and ravi@myagency.example. Then add everything you know about Acme: their brand voice, their competitors, and the campaigns we have run for them.
Scope a contractor to one project
Gives them exactly one project's context. Everything else in your vault stays where it is.
Create a space called "Website rebuild — contractor" and invite dev@contractor.example. Add only the memories about the website rebuild brief, the design decisions we have already made, and our code conventions. Do not add anything about other clients.
Ask about something a teammate shared
Recall reaches your shared spaces too: a note a teammate shared into "Acme — Client" comes back alongside your own memories, attributed to whoever shared it.
What do we know about Acme's brand voice?
Take something back out
Un-shares those memories. They stay in your own vault.
Remove the memories about our internal pricing from the "Acme — Client" space.
Close it when the work is done
Archives the space and revokes the access it granted. Only the owner can do this.
The website rebuild is finished — close the "Website rebuild — contractor" space.
Haven’t connected an assistant yet? It takes about a minute.
Questions about sharing
Can I share with someone outside my company?
Yes. There is no organisation boundary and no email-domain restriction — you can share with a partner, a family member, a client, or a contractor at another company. The one requirement is that they already have a justonce.ai account, because invitations are matched to an existing user.
Will my AI assistant search my shared spaces?
Yes. Your assistant's memory search recalls memories other members shared into your active spaces, alongside your own — each clearly attributed to the person who shared it, and read-only to you. Topic context and your core profile still draw on your own vault only, and if your sharing footprint is bigger than one search can cover, the response reports the gap instead of hiding it. Your assistant can also read a whole space directly, and fetch documents shared into it.
Can I share a document, not just a fact?
Yes, by sharing the memory it is attached to. A document always lands in your own vault first, attached to the memory your assistant wrote from it; share that memory into a space and every member can fetch the file through their assistant or open it from the space in the web app, with each fetch logged. One edge worth knowing: if your assistant split a long document into several memories, share all of them — a member sees exactly the memories shared, not the rest of the document’s set.
Does sharing a space expose my personal memories?
No. Your personal space is private and can never be shared — that is enforced in the product, not just a setting. A shared space only ever contains what you or another member explicitly put into it, and you can remove something at any time.
What is the difference between an Editor and a Viewer?
An Editor can read the space and add or change shared memories. A Viewer can read it. Both can share their own memories into the space. Only the Owner can invite people, change roles, remove members, or close the space. There is no separate Admin role.
Can I have separate spaces for different teams or clients?
Yes, and that is the intended shape. Each space has its own membership, so engineering and GTM, or Client A and Client B, never see each other. Someone who works across both simply belongs to both spaces.
Does the person I invite have to pay?
No. Members join a shared space free. Recall and search are free on every plan, so someone you invite can read the space without a paid subscription of their own.
What happens when someone leaves the team?
The Owner removes them from the space and their access ends. If a whole engagement is over, closing the space archives it and revokes everything that space had shared. Anything you shared into it stays in your own vault — closing a space doesn't delete your memories.
Can I see who added what?
Every membership change and document access is written to an append-only audit log, and the record of who shared what is stored. Your AI assistant sees it too: memories it reads from a space are attributed to the member who shared them. Being precise: the web app itself still shows no per-memory "added by" label, so this is not something you can see at a glance while reading a space there.
Put it somewhere the right people can reach it
Free to start, no card required. Members you invite join free.
Get started free