What this is
This page answers common user questions that appear before or during regular ecosystem usage.
Why I built this
I built this ecosystem because most teams are forced to jump between disconnected tools, and that creates delays, confusion, and missed handoffs. In real work, people do not need ten dashboards. They need one clear path to choose the right app, finish the task, and move on with confidence. The result is a practical ecosystem where each app has a clear job, and the documentation helps people use that job without technical friction.
Who should use this
- New users entering the Cumulus ecosystem for the first time.
- Team leads who need a clear map of which app solves which job.
- Operators who want step-by-step guidance without technical language.
What you can do today
- Resolve common navigation, access, and role confusion quickly.
- Understand product boundaries before starting work.
- Find where to continue when you are stuck.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Ecosystem FAQ.
- Identify your question type: access, role, workflow, or status.
- Read the matching answer and use the linked product guide.
- If the answer does not resolve the issue, move to product troubleshooting.
Known limits and maturity
- FAQ answers are short by design and do not replace full guides.
- Questions that require role-specific detail point to dedicated pages.
- The FAQ focuses on daily usage, not technical implementation.
- Current maturity: active.