A workspace used to be open to everyone in its organization. Anyone whose address joined it, including everyone whose company email signed up with the same domain, could open it and read its chats and its memory. That was right for a team’s shared memory and wrong for the small, private thing people kept asking us for.
Now a workspace says who can see it, and only those people can open it.
Three answers
When a workspace is made it asks who can see it:
- Everyone in your organization. Anyone in it today, and anyone who joins later. This is what every workspace made before today is.
- Just me. Only you.
- Certain people. Only the people you pick, from your organization.
A new workspace starts at Just me, and a workspace made before today keeps the answer it already had. Either way the answer is on the workspace’s Settings, under Who can see this, with the member list right there so the choice is a list of people rather than a word.
Changing it is a deliberate step: GBrain says who gains access, or who loses it, before anything moves. Whoever makes the change keeps access.
What a private workspace means
Someone in your organization who is not on the list is refused it the same way they are refused a workspace that does not exist. They do not see it in the workspace list, in search, or in what their own AI can reach. Membership still decides who is in the organization; this decides who among them can open one workspace.
An administrator of your organization can change a workspace’s answer only while they are on its list. Being an admin is not a way in: a workspace kept to certain people is not listed for an admin it does not name, and a link to it answers as a workspace that does not exist. Admins still run the organization, its members and its billing; they just cannot read a workspace that says it is somebody else’s. See A workspace for a sensitive team.
Where to find it
Open a workspace, then Settings, then Who can see this. Keeping a workspace to its people is also the first thing a new workspace’s chat offers.