For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rewst Dashboard

The Rewst Dashboard is the home screen you'll see when you first log into the platform. Click the drop-down organization selector to choose which org's information will be displayed in the dashboard at any given time.

MSP level dashboard

The dashboard when selected to view for your parent, top-most MSP level organization will display information for your entire Rewst platform and all the child organizations stored within it. Use the dashboard to easily digest key metrics for every workflow executed within a selected timeframe and better understand how Rewst is bringing you value. Identify usage patterns, success rates, and estimated time savings.

Child organization dashboard

The child organization dashboard will show you information and insights about just one organization. Choose which organization to use to populate the data in the organization drop-down selector at the top of your screen.

The Rewst Dashboard screen when set to view a child organization

Dashboard content

By default, the dashboard displays data for the last 30 days. Click the date range selector in the top right corner to choose a different period of 7, 14, 30, 60, or 90 days. Click Refresh to manually repopulate the dashboard with up-to-date data.

The Overview section of the dashboard gives you four totals for the selected date range.

  • Customers: The number of customer organizations with automation configured

  • Workflows: The total number of workflows available across those organizations

  • Runs: The number of workflow runs that occurred in the selected period

  • Time Saved: The cumulative time saved by automation in the selected period

Automation activity

These modules track activity over the selected time period.

  • Workflow Executions: Plots the number of workflow runs by day, so you can spot spikes in activity or confirm that automations are running on schedule

  • Time Saved: Plots cumulative time saved over the same period - if no time savings have been recorded, this chart displays as flat

  • Run Outcomes: Breaks down runs by day and shows a success rate for the selected period, so you can see at a glance whether failures are clustered around a particular date

  • Customer Coverage: Lists each customer organization, its plan tier, and whether automation is currently enabled for that organization - click Manage to jump to the settings menu for the organization

Top time-saving workflows

This panel ranks the workflows that have saved the most time in the selected period. If no workflows have recorded time savings yet, the panel displays a message indicating that no data is available.

Time savings estimates in your dashboards are generated from the time saved number entered in your workflow's settings, as well as Rewst's baseline assumption of the manual effort required without automation for prebuilt automations like Crates. An estimate of zero means your estimate was never filled out when you set up your workflow. To resolve a zero estimate, navigate to the workflow and enter the time saved estimate there under Configure Workflow > Time Savings.

If you have a workflow that has been running without a time saving value, and you add that value later, your dashboard won't retroactively update to reflect that time savings. Calculation and tracking begins when you add a time savings value.

Quick actions

The quick actions row gives you shortcuts to the most common areas of the platform, also accessible via the left side menu in Rewst. Click Workflows to review your automations, Runs to investigate individual executions, Customers to manage customer organizations, Marketplace to access Rewst's Marketplace, and Settings to update your configuration.

Recent runs

Learn more about runs in Rewst here.

The recent runs list at the bottom of the dashboard shows the most recent workflow executions along with each run's status and how long ago it occurred. A run can show as Completed or Failed. Failed runs include a short error message, such as an HTTP status code or a note about why the run did not complete. Click View all to see the complete run history.

Last updated

Was this helpful?