Roles and permissions

Look up Solum roles, permissions, seats, billing access, builder access, and platform access.

Solum roles are team-scoped. A role controls what a user can do inside one team. It does not grant access to every team, every product area, or internal Forcir operator tools.

Use this reference when assigning roles, diagnosing missing controls, or deciding which user should receive a team invitation.

Access layers

Layer	Required for	Notes
Public visitor	Search, public pages, share, feedback, inquiries.	No account required.
Signed-in user	Account settings, authenticated document downloads, dashboard, invitation acceptance.	Sign-in alone does not grant team access.
Team member	Opening a team workspace.	Membership is team-specific.
Team role	Settings, members, billing, builder actions.	Role permissions vary by team.
Linked builder profile	Builder profile, media, development, and promotion context.	Builder teams need provisioning.
Platform role	Internal Forcir operator tools.	Not granted by team roles.

Team roles

Role	Default permissions	Typical use
Owner	All team permissions, including billing and privilege administration.	Accountable team lead.
Admin	Manage team, manage members, manage developments, manage floor plans, manage leads, view analytics.	Operational manager.
Member	Manage developments, manage floor plans, manage leads.	Day-to-day contributor.
Billing	Manage billing only.	Finance or accounting contact.

Seat behavior

Role	Counts as billable operational seat?	Reasoning
Owner	Yes	Full operational access.
Admin	Yes	Operational management access.
Member	Yes	Operational contributor access.
Billing	No	Billing-only access without builder operations.

Use Billing for payment and invoice contacts who should not consume an operational seat or manage content.

Permission meanings

Permission	What it means today
Manage team	Update team settings. Builder profile and asset changes also depend on this broader team update gate.
Manage members	Open member management, invite regular members, revoke invitations, and remove non-owner members.
Manage billing	Open billing portal, start featured promotion checkout, and cancel active promotions.
Manage developments	Role contract for development operations. A complete self-serve development editor is not available yet.
Manage floor plans	Role contract for floorplan operations. A complete self-serve floorplan editor is not available yet.
Manage leads	Role contract for lead operations. A complete builder-facing lead inbox is not available yet.
View analytics	Role contract for analytics. Analytics pages may not exist yet.

Some permissions exist before every related page is complete. Confirm that a page exists before describing the task as available.

Billing access

Billing access requires Manage billing or platform admin access.

User	Billing card	Stripe portal	Promotion checkout	Builder media access
Owner	Yes	Yes	Yes, when builder promotion requirements are met.	Yes, through full permissions.
Billing	Yes	Yes	Yes, when builder promotion requirements are met.	No by default.
Admin	No by default	No by default	No by default	Yes for current Manage team-gated tools.
Member	No	No	No	Limited by current operational pages and permissions.
Platform admin	Yes	Yes	Yes for support contexts.	Yes for support contexts.

Admin and Billing are intentionally separate. Do not give Admin when the user only needs invoices. Do not give Billing when the user needs to manage builder profile or media.

Privilege administration

Privilege administration means changing another user's level of access.

Examples:

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

Only owners and platform administrators should perform privilege administration.

Invite role visibility

User	Role options shown in member invitation form
Owner	Member, Admin, Billing.
Platform admin	Member, Admin, Billing.
Admin	Member only.
Member	Members page is usually hidden.
Billing	Members page is usually hidden.

This prevents ordinary admins from escalating another user into billing or admin-level access.

Action requirements

Action	Required condition
Open team overview	Accepted membership in that team.
Update team settings	Manage team or platform admin access.
Delete team	Owner or platform admin, and not a personal team.
Open member management	Manage members or platform admin access.
Invite a regular member	Manage members.
Invite Admin or Billing users	Owner or platform admin.
Revoke pending invitation	Manage members.
Remove member	Manage members, and target user is not owner.
Transfer ownership	Owner or platform admin.
Open billing portal	Manage billing or platform admin access.
Start featured promotion checkout	Manage billing, builder team, linked builder, owned development, eligible promotion state.
Cancel active promotion	Manage billing and active promotion owned by the team.
Update builder profile	Linked builder team and Manage team.
Upload builder logo	Linked builder team and Manage team.
Upload development media/documents	Linked builder team, owned development, Manage team, valid file, configured storage.
Download development document as buyer	Signed-in user and available document asset.
Submit inquiry	Public visitor or signed-in user on a valid development page.

Builder-specific requirements

Builder tools need more than a team role.

Requirement	Why it matters
Team type is Builder	Buyer teams do not own builder catalog tools.
Team is linked to builder profile	Solum needs the public builder identity for profile, media, developments, and promotions.
Target development belongs to builder	A team cannot manage another builder's development.
Manage team	Profile and media changes depend on team update access.
Manage billing	Promotion checkout and cancellation are billing actions.

If a builder team sees No builder linked, role changes alone will not fix the issue. The team must be linked to the correct builder profile.

Platform roles

Platform roles are Forcir operator roles. They are separate from team roles.

The Admin Panel link appears only for users with a platform role such as platform admin, platform staff, moderator, support, or analyst.

Team owners, admins, members, and billing users do not receive the Admin Panel link just because of their team role.

Missing pages and controls

Missing item	Most likely cause
Team card	User is not an accepted member of that team or is signed into the wrong email.
Team settings	User lacks Manage team.
Members card	User lacks Manage members.
Admin/Billing invite options	User is not owner or platform admin.
Remove owner button	Owners cannot be removed directly. Transfer ownership first.
Billing card	User lacks Manage billing.
Builder profile fields	Team is not a linked builder team or user lacks Manage team.
Upload controls	Team is not linked, user lacks Manage team, target does not belong to builder, or storage/file validation blocks the action.
Promotion checkout	User lacks Manage billing, development is not eligible, or team/development linkage is missing.
Admin Panel	User lacks a Forcir platform role.

Role selection examples

Scenario	Recommended role
Primary builder contact who manages team and billing	Owner.
Operations manager who updates profile/media but should not manage invoices	Admin.
Finance user who only needs invoices and payment methods	Billing.
Contributor who helps with development content when the page or task is available but should not manage members or billing	Member.
Forcir support operator	Platform role, not ordinary team role.

Use the narrowest role that supports the user's job.

Roles and permissions

On this page