Accounts and teams
Account registration, sign-in, invitations, team workspaces, roles, permissions, and common access issues.
Accounts and teams are the boundary between public browsing and restricted product work. Buyers can use most discovery features without an account, but document downloads, invitation acceptance, team workspaces, billing, and builder tools require authentication.
How access works
Solum access is scoped in layers:
- Account identity confirms who the user is.
- Team membership confirms which workspace the user can access.
- Team role and permissions determine what they can do inside that workspace.
- Team type determines which product areas make sense for that team.
- Linked builder profile enables builder-specific tools.
If a user signs in successfully but cannot see an expected page or control, one of those layers is usually missing.
Pages in this section
| Page | Use it when... |
|---|---|
| Accounts, settings, and invitations | A user is registering, signing in, updating settings, accepting an invitation, or troubleshooting account state. |
| Team workspaces and permissions | A user is managing team access, roles, billing visibility, builder team readiness, or missing team actions. |
Account-level features
| Feature | Requirement | Notes |
|---|---|---|
| Register | Name, email, password, password confirmation. | Password must be at least 8 characters. |
| Sign in | Email and password. | Password reset is not self-serve in the current product. |
| Settings | Signed-in user. | Name and phone are editable. Email is displayed but disabled. |
| Dashboard | Signed-in user. | Team cards appear only for accepted non-personal team memberships. |
| Invitation acceptance | Signed-in or newly registered user with matching email. | Wrong-email acceptance is blocked. |
Team-level features
| Feature | Requirement | Notes |
|---|---|---|
| Open team overview | Accepted team membership. | The team card must appear on the dashboard. |
| Edit team settings | Manage team or platform admin access. | Builder profile fields also require linked builder context. |
| Invite members | Manage members. | Admin and Billing role invitations require owner or platform admin access. |
| Open billing | Manage billing. | Owners and Billing users receive billing access by default. |
| Manage builder profile/media | Builder team, linked builder profile, owned entity, Manage team. | Builder tools cover selected profile and asset tasks. |
Common access pattern
When diagnosing a team issue, ask these questions in order:
- Is the user signed in?
- Is the user signed in with the same email that received the invitation?
- Has the invitation been accepted?
- Does the team card appear on the dashboard?
- Is the team type correct?
- Does the role include the needed permission?
- Is the feature available in the product?
This order avoids treating a missing page as a bug when the user is actually signed into the wrong account or has not accepted access yet.
Documents, sharing, and data accuracy
Understand signed-in document downloads, shareable URLs, preview email behavior, feedback reporting, and new-construction data caveats.
Accounts, settings, and invitations
Create an account, sign in, update personal settings, accept team invitations, and understand common account states.