4 min guideUpdated August 2026App review required

Use the dashboard to choose the next action

Read the workspace dashboard as an operating queue, then open the source record behind a priority, exception or due item.

Best forOwner / Admin · Sales / Estimator · Project Management / Production · Accounts
Before you beginUse a representative record and confirm you have the permissions required for this area.

Step by step

  1. Open the dashboard and identify the cards, counts and shortcuts intended for your role.
  2. Start with overdue, blocked or exception signals before general totals.
  3. Open a signal and confirm the underlying client, quote, job, task, purchase or invoice record.
  4. Make the operational update on that source record, including an owner or next action where required.
  5. Return to the dashboard and confirm the signal now reflects the current state.

Good practice

Treat the dashboard as a navigation and attention layer. If the signal is wrong, correct the source record rather than working around it in a separate list.

When you are finishedYou can explain what needs attention, who owns it and which source record should be updated.

Before you begin

  • Your role and workspace shortcuts have been configured.
  • The team is keeping job, quote, task and financial states current.

Complete workflow

How the workflow moves

  1. 01
    Scan

    Review role-relevant priorities, due work and exceptions.

  2. 02
    Open

    Follow a card or count to the underlying record.

  3. 03
    Act

    Update the source record instead of treating the dashboard as a second system.

  4. 04
    Recheck

    Return to the dashboard and confirm the signal has changed.

Screen reference

What you will see

SignBas3 dashboard in the synthetic BrightLine demonstration workspace
Use dashboard signals to reach the current source record; the cards shown depend on role, data and setup.

Screens show the synthetic BrightLine demonstration workspace. Your records, permissions and configuration will change the details you see.

If your workspace behaves differently, record the relevant job, client or record number and raise a support ticket so the team can investigate the exact context.