Skip to content
Verified

Team & collaboration

The four ways people work together in Xuda, and where each one lives.

Xuda has one mechanism under the hood for letting another account into something of yours, a team_request document that moves through invited, joined, and removed, the same shape whether what is being shared is a whole project or a single chat. Four different screens put a face on it:

Sharing a project versus transferring it

Adding an Admin or a Developer to a project does not change who owns it: the owner keeps billing, keeps the Danger Zone, and can remove that person again at any time. Transferring ownership is the opposite move, it hands the whole project, server, website, or ad campaign to another account and removes it from yours.

The two shapes a share takes

Everything you share lands in one of two states. An item share, a chat, a mini app, an AI agent, a contact, a drive file or folder, or a profile, copies itself into the other account's workspace once they accept, so each side keeps its own copy going forward. A membership share, an Admin, a Developer, or a Team member on a project or deployment, gives the other account a seat inside your project instead of a copy of anything, and it disappears the moment you remove them.

Where each kind is described

Item shares are covered on Sharing projects and items. Membership shares are covered on Members and invitations and Roles and permissions.