Foundations
Current feature boundaries
See which Solum features are available, limited, planned, or internal.
Use this page to keep public docs accurate. Solum has foundations for many tasks, but not every task is available in the product yet.
Use this page when writing support responses, onboarding users, or deciding whether a guide should describe a feature as available.
Publication rule
Describe a feature as available only when the target user can complete the task in the product with the expected permissions.
If a model, permission, endpoint, or admin-only capability exists but the intended user cannot complete the task, describe it as limited, Forcir-assisted, or internal.
Feature matrix
| Area | Current state | Public docs stance |
|---|---|---|
| Buyer discovery | Implemented. | Document publicly. |
| Public detail pages | Implemented. | Document publicly with data accuracy caveats. |
| Map browsing | Implemented where regional data exists. | Document with coverage caveats. |
| Search sharing | Implemented through URL state. | Document publicly. |
| Email preview | Implemented for loaded search results. | Document as a convenience tool, not CRM/export. |
| Document downloads | Implemented for signed-in users. | Document gated downloads. |
| Inquiry submission | Implemented. | Document publicly, without overpromising response outcomes. |
| Account settings | Implemented. | Document name and phone editing; email is not self-serve. |
| Invitations | Implemented. | Document email matching, pending/accepted/expired states, and role effects. |
| Team dashboard | Implemented. | Document for signed-in team members. |
| Team roles | Implemented. | Document role behavior and seat behavior. |
| Builder profile updates | Partially implemented. | Document linked-team name, website, and logo controls. |
| Builder media uploads | Implemented for selected controls. | Document builder logo and development hero/gallery/documents. |
| Builder catalog editing | Limited. | Tell users to ask Forcir for help unless a specific product control exists. |
| Billing portal | Implemented. | Document for owners, billing users, and platform admins. |
| Featured promotions | Implemented with Stripe checkout. | Document steps and prerequisites, not fixed prices. |
| Saved homes | Placeholder/foundation only. | Document shareable URLs instead of saved homes. |
| Builder claiming | Not available publicly. | Explain that Forcir links builder teams to builder profiles. |
| Builder lead inbox | Planned/incomplete. | Say that a full builder-facing lead inbox is not available yet. |
| Analytics | Permission foundation exists. | Do not document full analytics tasks until a page exists. |
| Admin/import operations | Implemented internally. | Keep internal. |
Buyer-facing boundaries
Safe to document publicly
- Searching and filtering development inventory.
- Opening public detail pages.
- Comparing builder/community context.
- Sharing URLs.
- Submitting an inquiry.
- Signing in to download locked documents.
- Reporting inaccurate data through feedback.
Avoid overstating
- Do not imply Solum has complete market coverage everywhere.
- Do not imply pricing is guaranteed.
- Do not imply a submitted inquiry reserves availability.
- Do not imply signed-in buyers can save homes yet.
- Do not imply all documents are available for every development.
Builder-facing boundaries
Safe to document for provisioned teams
- Viewing the team workspace.
- Seeing the linked builder's developments.
- Updating builder name and website when authorized.
- Uploading builder logo.
- Uploading development hero images, gallery images, and documents.
- Opening billing portal when authorized.
- Starting and cancelling featured development promotions when authorized.
Keep limited or assisted
- Claiming a builder profile.
- Creating new developments.
- Editing every structured catalog field.
- Editing floorplans deeply.
- Managing a complete lead inbox.
- Running imports.
- Managing admin-only resources.
Support language
Use precise language:
| Instead of saying | Say |
|---|---|
| "Builders can claim their profile." | "Forcir links provisioned builder teams to builder profiles." |
| "Builders can manage listings." | "Provisioned builder teams can manage selected profile and media settings." |
| "Saved homes are available." | "Use shareable URLs while saved homes are still in development." |
| "Builders can manage leads." | "Buyer inquiries are captured; a full builder-facing lead inbox is not available yet." |
| "Prices are current." | "Confirm current pricing and availability with the builder." |
Documentation maintenance checklist
Before publishing or updating a page, confirm:
- Route names are correct.
- Navigation labels match the product.
- Permissions match current role behavior.
- Missing page and control explanations are accurate.
- Screenshots, when added, match production or the intended preview environment.
- Pricing and promotion wording avoids hard-coded prices unless verified.
- Planned features are not described as current.
- Internal admin/import instructions are not exposed in public docs.