Team workspaces and permissions

Team workspaces give signed-in users access to shared product areas. Builder organizations, buyer groups, finance contacts, and internal users can all use teams, but each team type has different tools.

Most team access starts with an invitation. Some builder teams are set up by Forcir.

Before managing a team

Confirm:

1. The user is signed in.
2. The user is signed in with the expected email.
3. The team appears on the dashboard.
4. The team type is correct for the task.
5. The user's role includes the needed permission.

Team permissions are scoped to a single team. Being an admin in one team does not create admin access in another team.

Team dashboard

Open Teams from the avatar menu to reach the dashboard.

The dashboard shows non-personal teams available to the signed-in user. Each team card links to that team's overview page.

If no team cards appear, the user has no accepted non-personal team memberships for the signed-in account.

Team overview

A team overview can show:

• Team name.
• Team type badge.
• Member count.
• Settings button when the user can manage the team.
• Members card when the user can manage members.
• Billing card when the user can manage billing.
• Current member list.
• Manage shortcut to member management when allowed.

If the user can access the team but has limited permissions, the overview may show only basic team details and member information.

Team types

Some code paths can display a realtor label for existing or internal data, but current public team creation is centered on builder and buyer team types.

Roles

Solum uses team-scoped roles. A user's role applies inside a specific team and does not automatically grant access to other teams.

Role selection guidance

Use the narrowest role that matches the user's job. Avoid making a finance contact an Admin when Billing is enough.

Seat behavior

The billing role is designed for invoice and payment administration. Use it when someone needs billing access without builder profile, media, or team operations access.

Permission boundaries

Some permissions exist before every related page is complete. If an expected operational page is missing, confirm that the page is available, not only represented by a permission.

Permission vs page availability

A permission can exist before a complete page is available. For example, lead and analytics permissions may exist even when a full builder-facing lead inbox or analytics page is not available yet.

When a user asks for a missing page, verify both:

1. Their role includes the permission.
2. The page exists in the product for that audience.

Privilege administration

Privilege administration means changing what another user can do. It includes:

• Inviting someone as Admin or Billing.
• Changing a member's role.
• Granting direct permissions.
• Transferring ownership.

Only owners and platform administrators should perform privilege administration. A team admin can manage normal membership but should not be able to promote themselves or grant billing access.

Invite members

Open Members from the team overview when the card is available.

The invite form includes:

• Email.
• Role.
• Send invitation.

Visibility rules:

Pending invitations appear below current members. Authorized users can revoke pending invitations.

Remove members

Authorized users can remove non-owner members from the Members page.

Removing a member revokes their team access. The user can remain a Solum account holder, but they no longer have access to that team.

Owners cannot be removed directly. Transfer ownership before removing or replacing an owner.

Team settings

Open Settings when the team overview shows the settings button.

Team settings currently include:

• Team name.
• Builder logo and builder profile fields when the team is a linked builder team.
• Delete team action when the user is an owner or platform admin.

Team deletion is permanent and is not available for personal teams.

Billing

The Billing card appears only for users with Manage billing or platform admin access.

Owners receive billing access by default. Billing users receive billing access without operational product access. Admins do not receive billing access by default.

Builder teams

A builder team needs two things before builder-specific tools are useful:

1. Team type is Builder.
2. Team is linked to a builder profile by Forcir.

If a builder team is not linked, development management shows a "No builder linked" state and builder profile controls do not appear.

Linked builder troubleshooting

If a linked-builder task is missing, role changes are not always the fix.

Check:

1. Team type is Builder.
2. Linked builder profile exists.
3. Development belongs to that builder.
4. User has the required permission.
5. The task is available in the current builder tools.

Current builder console limits

The team workspace does not include every planned builder tool yet. In particular:

• Public self-serve builder claiming is not available yet.
• Builder teams cannot fully create new catalog records through team tools.
• Builder teams cannot fully edit every structured development or floorplan field through team tools.
• A complete builder-facing lead inbox is not available yet.
• Analytics may be represented in permissions before a page exists.

Ask Forcir for help with catalog changes that are not available in the team workspace.

Why a team action may be missing

Team troubleshooting

When a user reports missing access:

1. Confirm the user is signed in.
2. Confirm the account email matches the invitation or membership.
3. Confirm the user accepted the invitation.
4. Confirm the user is a member of the expected team.
5. Confirm the team type.
6. Confirm the role and required permission.
7. Confirm the feature is available in the product.
8. Refresh after any role or invitation change.

For action-level requirements, see Roles and permissions.