Docs
Accounts and teams

Accounts, settings, and invitations

Create an account, sign in, update personal settings, accept team invitations, and understand common account states.

Accounts are used for team workspaces, invitations, billing, authenticated document downloads, personal settings, and Forcir operator access.

Public search and inquiry submission do not require an account.

Account lifecycle

Most users enter account tasks through one of these paths:

PathWhat happens
Buyer signs in to download a documentThe account unlocks authenticated document downloads and personal settings.
User receives a team invitationThe account must match the invited email before team access can be accepted.
Builder or billing contact is invitedThe user signs in, accepts the invitation, then opens the team workspace.
Forcir operator signs inPlatform roles can expose internal operator links such as Admin Panel.

Sign-in confirms identity. It does not automatically create team access, billing access, builder access, or platform access.

Create an account

Open Sign in, then choose Create one from the login screen, or open an invitation link while signed out.

Registration requires:

FieldRequirement
NameRequired.
EmailRequired, valid email address, unique to one account.
PasswordRequired, minimum 8 characters.
Confirm passwordMust match the password.

If the registration URL includes an invitation token, Solum keeps that invitation context during registration.

Before registering from an invitation

Use the email address that received the invitation. Invitation acceptance is email-bound, and accepting with a different account is blocked.

If the invitation was sent to the wrong email, ask the team owner, authorized admin, or Forcir contact to issue a new invitation.

Invitation-based registration

When a signed-out user opens an invitation link, Solum redirects them to registration with the invitation token attached.

After registration, Solum attempts to continue the invitation flow. Use the email address that received the invitation. If the wrong email is used, team access may not be available and a new invitation may be needed.

Sign in

The login form requires:

  • Email.
  • Password.

After sign-in, Solum sends the user to the requested protected page or to the dashboard. Sessions can persist on trusted devices.

Password reset is not self-serve in the current product. If a user cannot sign in, use the appropriate support path.

After sign-in

After signing in, expected destinations include:

SituationExpected result
User opened a protected page firstSolum attempts to continue to the requested page.
User signed in from normal loginSolum sends the user to the dashboard.
User has no team membershipsDashboard shows a welcome or empty state.
User has pending invitation contextSolum continues the invitation flow when possible.

Sign out

Open the avatar menu and select Sign out. This ends the current session and returns the user to the login flow.

On mobile, Sign out appears at the bottom of the menu.

Account settings

Open the avatar menu and select Settings.

Account settings include:

FieldEditable?Notes
NameYesRequired.
EmailNoDisplayed but disabled. Email changes require support.
Phone numberYesOptional. Signed-in inquiry forms can use this as a default phone value.

Select Save changes to update settings.

Dashboard

The dashboard lists teams available to the signed-in user. Personal teams are filtered out of the primary team card list.

If the user has no visible teams, Solum shows a welcome state explaining that they can explore developments while waiting for an invitation.

Dashboard does not equal authorization

Seeing the dashboard means the user is signed in. It does not mean the user has access to a specific team.

The team card must be visible before the user can open that team. If the expected team card is missing, verify invitation acceptance and email matching before checking permissions.

When a signed-in user opens an invitation link, Solum shows:

  • Team name.
  • Inviter name.
  • Invited role.
  • Team type badge.
  • Accept invitation action when the invitation is pending.

To accept:

  1. Open the invitation link.
  2. Sign in or register if prompted.
  3. Confirm the invitation is for the expected team.
  4. Select Accept invitation.
  5. Solum redirects to the team workspace.

Pending invitations page

Signed-in users can open the invitations page to view pending invitations addressed to their account.

Each invitation can show:

  • Team name.
  • Inviter name.
  • Invited role.
  • Team type.
  • Accept action.

If there are no pending invitations, Solum shows an empty state.

Invitation statuses

StatusMeaning
PendingThe invitation can still be accepted.
AcceptedThe invitation was already used.
ExpiredThe invitation is no longer valid.
InvalidThe token does not exist, is no longer available, or cannot be loaded.

If an invitation is expired, invalid, or already accepted, ask a team owner or authorized team admin to send a new invitation.

Email matching

Invitation acceptance is tied to the invited email address. If a signed-in user tries to accept an invitation sent to a different email address, Solum blocks the action.

When troubleshooting:

  • Confirm the invitation email.
  • Confirm the signed-in user's account email.
  • Sign out and sign in with the correct account if needed.
  • Ask for a new invitation if the wrong email was used.

Why account pages or controls may not appear

Missing itemLikely reason
Sign in buttonThe user is already signed in and should use the avatar menu.
Avatar menuThe user is not signed in or the session expired.
Teams menu itemThe user is not signed in.
Team cards on dashboardNo accepted team memberships are available for the signed-in account.
Admin PanelThe signed-in user does not have a Forcir platform role.
Locked document downloadThe user is signed out. Sign in to download.
Invitation accept buttonInvitation is not pending or cannot be loaded.

Common account problems

ProblemWhat to do
"Team not found" after signing inConfirm the user belongs to the team and is using the correct email.
Invitation is expiredAsk an authorized team member to send a new invitation.
Invitation sent to wrong emailAsk for a new invitation to the correct email.
Email needs to changeEmail changes require support or an operator-assisted flow.
User sees dashboard but no teamThey may have only a personal account or have not accepted an invitation yet.

Feedback

Use Feedback to report account or invitation issues. Include:

  • The email address involved.
  • The team name, if known.
  • Whether the user is registering, signing in, or accepting an invitation.
  • The page URL.
  • The exact error or missing page/control.

Support notes

When troubleshooting accounts, avoid changing roles before confirming identity and invitation state.

Recommended order:

  1. Confirm signed-in email from account settings.
  2. Confirm invited email.
  3. Confirm invitation status.
  4. Confirm team membership.
  5. Confirm role and permissions.
  6. Confirm the page or control is available for that role.

On this page