A workspace belongs to one organization. Sometimes it belongs in a different one: a team that started inside the company’s organization and now needs its own wall around it, or a workspace created in the wrong place on the day it was made.
Moving it does not mean starting again. The workspace keeps its name, its chats, everything it remembers, its files, its schedule and its plan. The AI is not told anything and does not need to be.
Who can do it
The person who pays for both organizations, and who is an admin of both. A workspace moving between two organizations on one person’s bill is the only move GBrain offers, because nothing about who pays should change in the middle of a billing period.
Before the move
Open the workspace’s Settings, then Move to another organization. The page lists the one thing that decides the rest: who can open the workspace afterwards. Who can open a workspace is decided by membership of the organization it lives in, so:
- Everyone in the new organization can open it afterwards.
- Someone in the old organization who is not in the new one loses it, with no message to explain it. A share of theirs stops working, and an AI they connected to it reaches nothing.
The page names each of those people, and refuses the move until they are members of the new organization. Add them in the new organization’s Members, then come back. Connected AIs keep working with nothing to reconnect: the membership was the only thing standing in the way.
Two things to settle first
A workspace answers in Slack, and it runs its AI calls on the organization’s own inference endpoint, both belong to the organization. Neither can follow the workspace:
- Slack. Disconnect Slack on the workspace’s Messaging page first, move it, then add it again from the new organization’s Slack.
- A custom endpoint. Switch the workspace to a model that is not a custom endpoint, move it, then add the endpoint in the new organization and pick it again.
The page says which of these applies, if either does, and stops until it is settled.
Pressing the button
Type the workspace’s name and confirm. Its files are copied into the new organization’s storage, and then it moves. The workspace keeps working while this runs: a file is readable from either place until the move lands.
Nothing is deleted. The copy in the old organization stays where it is, which is what makes a move safe to attempt and safe to stop.
If it takes longer than it should, the same page has Cancel the move. While the move has not landed, cancelling puts everything back exactly as it was.
Afterwards
The workspace is in the new organization, and everyone there can open it. Its plan, its allowance for the period and its billing are unchanged. Its old organization keeps its own wallet and its own history of what was spent there.
What a move does not do
- It does not move people. Membership of the old organization is untouched.
- It does not move an organization’s credit or spending history. Those belong to the organization that spent them.
- It does not delete anything, in either organization.
- It does not merge organizations. If two teams should share one wall, the answer is one organization, not two that can see each other.