Reference¶
Use reference pages when you need terminology, access-control answers, or machine-readable documentation indexes.
How to use this section¶
Start with the Glossary when teams use different names for the same concept. Use the RBAC FAQ when a user can sign in but cannot see a page, export data, approve a workflow, or manage another user.
Reference pages¶
| Page | Use it for |
|---|---|
| Glossary | Review CloudVerse terminology. |
| RBAC FAQ | Answer common access-control questions. |
Common checks¶
| Question | Where to look |
|---|---|
| What does this product term mean? | Glossary |
| Why can a user not see a page? | RBAC FAQ, roles, and access scopes |
| Which docs should an AI assistant ingest? | /llms.txt for the index, /llms-full.txt for the full export |
When troubleshooting, capture the page name, active organization, date range, filters, and visible error text before opening an internal support request. Those details usually matter more than a screenshot and avoid exposing names or sensitive financial data.
AI-agent entry points¶
The GitHub Pages build generates:
/llms.txt, a compact index for agents./llms-full.txt, a complete plain-text export of the documentation.