Personal, teams, and transfers

Keep your own instances in Personal, and create or join a team when you want to share a computer with other people. One Cloud account can belong to several teams: Personal, Acme Co, and a client’s team can all sit behind the same login.

Each instance belongs to one profile. Everyone on a team can open and manage that team’s instances, including their files and signed-in accounts. Joining a team doesn’t give its members access to your Personal instances.

Choose a profile

Open the profile menu at the top of Cloud and choose Personal or a team. Instances shows the machines in that profile, and New instance creates there. Check the profile name before launching. Switching profiles leaves your machines running.

You can keep different teams open in separate browser tabs. The profile in each tab’s address stays attached to that tab.

Your Personal profile is created with your account. It can stay empty, and it cannot be renamed, shared, or deleted. Leaving a team doesn’t affect it.

Create a team

1. Open the profile menu and choose Create team.
2. Give the team a name, such as Acme Co.
3. Choose Create team to open its settings. You’re its first owner.

You can rename the team from Team settings. A team is just a place to share instances; it doesn’t need to represent a registered company. Cloud limits the number of teams each person can create during beta.

Invite someone

Team owners can invite people who already have an Enso Cloud account. A team invitation doesn’t create an account or replace the private beta signup code. If someone is new, they need a beta signup invite first.

1. Switch to the team and open Team settings.
2. Under Invite someone, enter the email address they use to sign in.
3. Choose Send invitation.

The invitation appears in that person’s Cloud Notifications. No email is sent. Invitations expire after seven days, and an owner can revoke a pending invitation from Team settings. If it expires or is declined, send a new one when the person is ready. Cloud also limits a team’s pending invitations during beta.

Join a team

Open Notifications using the bell at the top of Cloud. Choose Accept invitation to join, or Decline to dismiss it. An invitation belongs to the account it was sent to; sign in with that account if it isn’t showing up.

Accepting adds the team to your profile menu. Choose it there, or use Open team in notification history. You join as a member, and your Personal profile stays yours. There’s no need to create another login.

History keeps accepted, declined, revoked, and expired invitations so you can see what happened. A previously accepted invitation can’t restore access after you leave or are removed; ask an owner for a new invitation.

Owners and members

A team can have more than one owner. Owners manage the team; members can work with its machines.

Owners can change roles or remove people in Team settings. The last owner must make someone else an owner before leaving or becoming a member. A team can only be deleted after its instances have been transferred or deleted; instances still being deleted or showing an error also count. Deleting the empty team revokes its outstanding invitations.

Transfer an instance

A transfer moves the existing computer to another profile. Its address, files, setup, and running apps stay with it; you don’t need to create a replacement.

You must own the source profile: either your Personal profile or a team where you’re an owner. You must also belong to the destination, and it must have room within its instance limit. You can move between teams, from Personal to a team, or from a team to your own Personal profile. Another person’s Personal profile isn’t a destination.

Cloud is free during beta. A receiving team doesn’t need billing set up to accept a transfer.

1. Open the instance in its current profile.
2. Open Instance actions and choose Transfer instance.
3. Select the destination profile.
4. Review who will gain access and confirm that you understand the change.
5. Choose Transfer instance. Cloud opens the instance in its new profile.

If the machine is busy provisioning, connecting chat, or completing another Cloud operation, let that operation finish and retry. You cannot transfer a machine while it’s being deleted or after deletion.

If a connection problem interrupts confirmation, use Check transfer or Retry transfer to check the same transfer. Cloud keeps the original request so a retry doesn’t move the machine a second time.

People who only belong to the source team lose Cloud access. Members of the destination gain access, and existing desktop and viewer connections are revoked. Open the desktop or viewer again from the destination profile.

Sharing the computer

Team access includes the whole instance. Files, conversation history, browser sessions, connected AI accounts, and other credentials remain on that computer. Transfer only after checking that those contents belong with the receiving profile.

Cloud membership doesn’t create separate user accounts inside the machine. Removing someone from a team stops their Cloud access, but doesn’t remove guest credentials or other access they set up inside the computer.

A transfer also keeps the existing Slack or Telegram connection and pairing. It doesn’t move Enso into the client’s chat automatically. Review those connections and any independently shared access when handing over an instance. Use Configuration for chat and provider settings, and Workspaces for conversation context and instructions.