Dashboard orientation and basic navigation

Prerequisites and authority

Use an individual staff account with the action permission and required organization module/license. Viewing a menu does not establish permission to mutate records.

Use the dashboard as an entry point

Sign in using your individual staff account. Start with Dashboard, then choose the area related to the task: Customers, Services, Reporting & Analytics, Operations or System. The navigation inspected in the repository uses these groups; availability depends on permissions, organization modules and licensing.

Do not treat a missing menu as a failed deployment until you have checked those gates. Mobile Apps is outside this documentation edition even where the interface contains it.

For a customer incident, open the customer record and follow its subscriptions, payments, devices and sessions. For a background action, open System Operations and inspect the run. For access changes, use Administration rather than changing database rows.

Dashboard totals are a summary. Before acting on a number, inspect its time period, filters and source records. A running service indicator does not prove that a payment or router operation completed.

Complete a task deliberately

1. Locate the authoritative record and confirm its identity.
2. Check your role permits the intended action.
3. Review current status and related records.
4. Apply one supported action and retain its outcome.
5. Verify the result in the affected workflow.

If an action appears stuck, inspect Operations before repeating it. Capture the displayed error and record identifier. Repeated clicks can obscure whether a job is already running. Use System operations and task controls for task controls and Troubleshooting start here: observe, scope and collect evidence for triage.

Related guides

Related guides: Staff accounts, roles and permissions, Administrative session and audit investigation, System operations and task controls, Roles and permission matrix.