Skip to content
Verified

Workspaces for teams

Give your own team, or your customers, a dedicated sign-in portal into an app you built.

A project's own workspace, its six tabs of chats, apps, contacts, AI agents, and profiles, becomes a shared one the moment you add an Admin or Developer to it, see The workspace for that shell. A User Group deployment is a different, more deliberate kind of shared workspace: a portal you build and deploy specifically for other people, your own team or your customers, to sign in to and use one part of what you built, separate from your own account.

Deploy a User Group

Open Deploy

From your project, click Deploy, then choose Deployments, then select User Group.

Configure it

One step, several cards: choose an access mode (Invite only, Approval, or Open), turn sign-in methods on or off, seed the deployment with the email addresses of people who should already be in it, and set the interface behaviour members get by default. See below for each of these in detail.

Choose what it opens to

Pick the screen or program this deployment should open members to.

Choose a datacenter and a performance tier

Where it runs, and how much power it has.

Finalize and create

Name the deployment, review the price, and create it.

Everyone after creation is managed from Team

The email list in Configuration is only read once, when the deployment is created. Every member after that, invited, approved, or removed, is managed from the deployment's own Team tab.

Access mode

Where a signup shows up

A person who signs themselves up shows on the deployment's Team tab exactly like an invited member, with its own Waiting for approval status under Approval mode. See Members and invitations for the Approve and Deny actions.

Sign-in methods

Password, Google, GitHub, and a six-digit email code (valid ten minutes, no link, since the sign-in screen runs inside an embedded frame where a clicked link would open outside it) can each be turned on or off independently. Google and GitHub also need to be enabled for the app in Firebase before the button actually works, not only switched on here.

Interface behaviour, per member

Three preferences shape what a member sees once they are in, set as defaults when they are added and editable per person afterward:

  • Hide create button: members do not see the Create button in their sidebar.
  • Set as dashboard: members land here when they sign in, instead of on their own personal dashboard.
  • Sidebar style: open, collapsed, or hidden, for how the sidebar starts.

A profile is a shared identity too

A business profile can be shared with teammates the same way any item can, see Sharing projects and items for exactly what a profile's members may see and add. Where a User Group deployment gives people their own portal into an app, sharing a profile lets a team work together under one identity, the apps, contacts, and AI agents that belong to that profile, without a deployment of its own. See Profiles for what a profile is.