Skip to content
Use cases

Your team’s context lives in one person’s account — and leaves when they do

Team AI plans often keep memory per account, so brand voice, client facts and decision rationale stay in one person’s chat history. JustOnce shared spaces help: each member’s own Claude recalls what was shared, credited to whoever shared it, with Owner, Editor and Viewer roles, one space per client, and access that ends when the space closes. Or members open the space in the web app.

Get started freePrompts to copy

Why doesn’t my team’s AI plan share memory?

Because in many of the plans teams buy, each person’s memory stays with their own account. Teams paying for seats discover this after the purchase. One customer on OpenAI’s community forum wrote: “This is actually so obvious that we signed up for a Team Account expecting this to be included.” Another described the workaround they landed on: because a Business subscription shares memory across an individual’s own chats but not across accounts, “we used the same account and experimented in that way”. Paying per seat and then sharing one login is not a workflow anyone chose.

At our July 2026 check, ChatGPT Business did not share memory across accounts.

What is actually shared today — and what isn’t?

Be clear on this before you buy. A shared space is real, and assistant recall reaches it: when your colleague asks Claude a question, a memory you shared into your common space comes back in their answer, clearly attributed to you. It is read-only to Viewers; Owners and Editors of the space can correct it, and only its owner can erase it. Members also read the space in the web app, open its documents there, and share their own memories in. The precise edges: it is assistant memory search that recalls across spaces, while topic context and the core profile draw on each member’s own vault. A correction by an Owner or Editor is what every member’s assistant recalls from then on.

An assistant reads a space with list_space_memories, which names who shared each memory, and get_memory carries the same credit. Context and profile tools resolve to the caller’s personal space. Document fetch honours shared-space access.

Can an agency give each client its own space?

Yes. You write for Client A, then Client B, and a single long chat starts blending their terminology, their positioning and sometimes their competitors’ names. A space per account keeps its membership separate — only the people on that account are in it. A freelancer who joins for six weeks gets that one space as an Editor, and nothing else. One edge to know: your own assistant’s memory search isn’t fenced by space, so if you are in two client spaces, name the client when you ask.

Spaces have independent membership with Owner, Editor and Viewer roles, validated server-side. There is no organisation boundary, so a client-side contact or an outside contractor can be a member — with or without a justonce.ai account: someone new is emailed a link to create a free one, then accepts.

What happens when someone leaves?

The Owner removes them and their access ends. What they shared — the commitments made, who the real decision-maker is, why this account is handled the way it is — stays readable to the rest of the space after they leave, until the space owner removes it or they forget it, because a shared memory lives in the vault of the person who shared it. To take a share back yourself, unshare it before you leave. Someone who joins later sees what was shared before they arrived, because access is worked out when they read, not frozen at the moment of sharing. And when an engagement ends, closing the space revokes the access it granted.

Late joiners see previously shared memories. Closing a space archives it and ends access; reopening does not restore it. Memories you shared in stay in your own vault either way. Space membership changes and document access are written to an append-only audit log.

Does it capture anything from our calls or CRM automatically?

No, and this is the honest limit of the product for a business buyer. There is no Gong connector, no CRM sync, no Slack integration and nothing that reads your mailbox. A memory exists because someone told their assistant to save it while they were already working in it, uploaded a file, or forwarded an email to their own private address. What JustOnce fixes is recall and continuity, not note-taking. If your problem is that nobody writes anything down, a memory layer will not solve it.

What does it cost for a team?

Team seats are US$19.99 per user per month, and founding-team pilots run at US$12.99 per user with a three-seat minimum. Members you invite into a shared space join free — there is no per-seat charge for someone who is only reading a space you own. Team seats have no checkout yet: talk to us. Today, shared spaces come with Plus (1) and Pro (3), and each extra shared space is US$4.99 a month on a paid plan, adding 40 memories and 60 pages a month to your allowance.

Prompts for this

Copy these into Claude once you've connected it to JustOnce. They work as written.

Set a client space up in one go

Creates the space, then asks you to approve the invitation and the shares in JustOnce; nothing is sent or shared until you do. Invitations created from an assistant join as Viewer; promote to Editor in the web app.

Create a shared space called "Acme — Client" and invite jo@myagency.example. Then add everything you know about Acme: their brand voice, their competitors, and the campaigns we have run for them.

Record a decision with the reasoning attached

Saves the decision and the reason behind it as a memory, then asks to share it into the space; once you approve it in JustOnce, the rest of the account team can read it.

Remember this and add it to the "Acme — Client" space: we set Acme's retainer at 6,500 a month from 1 August, agreed with their marketing director, because the previous scope kept expanding without a change order.

Brief yourself before a client call

Searches your own vault and what teammates shared into your common spaces, and reads the account back to you — shared facts attributed to whoever shared them.

I have a call with Acme in twenty minutes. What do I know about this account — who the decision-maker is, what we agreed on pricing, and anything we have promised 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 and the design decisions we have already made. Do not add anything about other clients.

Take something back out

Un-shares those memories. They stay in your own vault.

Remove the memories about our internal margins from the "Acme — Client" space.

Close the engagement properly

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.
The full prompt library

Questions

Something else? Ask us.

Will my team’s AI assistants search our shared space?

Yes. When you ask your connected assistant a question, memories teammates shared into your common spaces come back alongside your own — each clearly attributed to the person who shared it. Each search covers what up to eight teammates shared with you (those who shared most); beyond that your assistant is told, and can read a space directly. Shared memories are read-only to Viewers; Owners and Editors of the space can correct them, and only their owner can erase them. A correction by an Owner or Editor is what every member’s assistant recalls from then on. Topic context and the core profile draw on your own vault only. Documents in a space open in the web app for every member, and their assistants recall the facts.

Can I share with someone outside my company?

Yes. There is no organisation boundary and no email-domain restriction, so a client, a contractor or a partner at another company can be a member. If they do not have a justonce.ai account yet, the invitation email asks them to create a free one with that address, and the invitation is waiting for them to accept when they sign in.

What roles are there?

Owner, Editor and Viewer — there is no separate Admin role. The Owner can invite, remove, change roles and close the space. An Editor reads the space and adds or changes shared memories, while a Viewer reads it. Both Editors and Viewers can share their own memories in.

Can I run a separate space per client and per team?

Yes, and that is the intended shape. Each space has its own membership, so the people on Client A see only Client A’s space, and engineering and GTM do not wade through each other’s context. Someone who works across two simply belongs to two — and their own assistant’s memory search isn’t fenced by space, so they should name the client when they ask.

Can I see who added each shared memory?

Your AI assistant can: shared memories it reads from a space are attributed to the member who shared them. Space events are also written to an append-only audit log. Being precise: the web app itself still has no per-memory “added by” label, so it is not something you can see at a glance while reading a space there.

Do the people I invite need to pay?

No. Members join a shared space free, and recall and search are free on every plan, so someone you invite can read the space without a subscription of their own. Team seats are for full team workspaces, not for adding a reader to a space.

What happens to what we shared if we stop using JustOnce?

Memories you shared into a space stay in your own vault — closing a space revokes the access it granted, it does not delete your memories. Ask us for a copy of your data any time; one-click export isn’t built yet, and we will not claim it until it is.

Other things people use it for

Decisions, saved once

The decisions and preferences you re-explain every week, saved once and recalled in every later chat, dated.

Job search

Every application, resume version, salary quoted and recruiter conversation — recalled by your assistant before the call.

Documents & email

No per-tool file limit. Save documents through your assistant, or forward them to a private address that runs on your own model key — and each assistant you connect, such as Claude or Cursor, recalls them.