Skip to main content

Workspaces and team invitations

Open Workspaces to create or select a workspace. The selected workspace scopes dashboard users, clients, groups and other resources. The dashboard overview shows resource counts and recent users.

A workspace name must contain at least three characters. Its owner is the developer who creates it. Owners can edit/delete the workspace and manage invitations and members. Members can access the workspace, but ownership restrictions still apply to individual resources.

Create or select a workspace​

  1. Open Workspaces. If you already have a workspace for this test or application, select it.
  2. Otherwise, create one with a name such as Login test, save it, and check that it appears in your workspace list.
  3. Select that workspace before opening Applications, Users, Groups or Email templates. Check the selected name if a list looks empty or shows unexpected records.

Selecting a workspace changes the context of your dashboard work. It does not create application users or sign a test user in. Continue with application setup to prepare login.

To invite a teammate, open workspace members, search for their developer account, choose a role and send the invitation. The recipient signs in as the invited account and accepts it. An email invitation token does not authorize an unrelated account. Pending invitations can be cancelled; expired/rejected invitations cannot be accepted.

Check the invitation status after sending it. A pending invitation still needs the recipient's acceptance. After acceptance, confirm the teammate appears as a member and can open the intended workspace. If they cannot accept, check the invited account and invitation status before sending another invitation.

Adding a member directly through the API requires an accepted invitation. Workspace members are developer accounts, not the users who sign in to your application. Use user groups to organize application users.

If a teammate can open the workspace but receives 403 on a client or template, check that resource's owner rules. Membership does not grant identical edit/delete authority across every resource. See workspace and invitation operations.