Reference
Reference
Lookup tables and diagnostic guides for Solum roles, permissions, missing controls, and support tasks.
Use reference pages when you already know the task but need the exact role, permission, visibility rule, or troubleshooting path.
Pages in this section
| Page | Use it when... |
|---|---|
| Roles and permissions | You need the role matrix, permission meanings, seat behavior, and action-level requirements. |
| Troubleshooting | You need a practical diagnostic path for missing pages, failed uploads, billing issues, inquiry failures, document downloads, or stale data. |
Fast lookup
| Question | Start here |
|---|---|
| "Why does this user not see the Billing card?" | Roles and permissions |
| "Why can an Admin not invite Billing users?" | Roles and permissions |
| "Why can a buyer see a PDF but not download it?" | Troubleshooting |
| "Why are upload controls missing?" | Troubleshooting |
| "Which features are not available yet?" | Current feature boundaries |
Support evidence to collect
Before escalating an issue, collect:
- User email.
- Team name, if a team page is involved.
- Role or expected role.
- Page URL.
- Exact missing button, section, or error state.
- Browser/device details for map, share, upload, or download issues.
- Development, builder, or community name when the issue concerns listing data.
Collecting these details first usually shows whether the issue is account state, permissions, an incomplete product area, data availability, or a product defect.