Skip to content

Profiles

A profile is a named snapshot of everything that defines a report view — filters, sort, view-mode, table-type, date preset. Profiles let you avoid rebuilding the same combination every time you open a report and let teams share standardised views.

Every report has its own profile list. Sales profiles don’t pollute the customer reports.

When you save a profile, the plugin captures:

  • The active filter values from the left sidebar
  • The current sort (column + direction)
  • The active view-mode (where the report has multiple)
  • The current table-type (where the report has multiple sub-tables, e.g. Margins)
  • The current date preset (or custom range)

Anything not in the list above — open / collapsed sidebars, scroll position — isn’t saved.

  1. On any report page, configure filters, sort and view-mode to taste.
  2. In the right-hand profile sidebar click Save profile.
  3. Give it a name and optionally tick Set as my default.
  4. Click Save.

The profile appears in the right-sidebar list. Clicking it any time reloads the saved state.

Two layers of “open this profile when I land on the report”:

  • My default — your personal default for this report. Other admin users are unaffected.
  • Global default — shared with everyone. Only set this for shop-wide standard views (e.g. “EU sales, last 30 days, paid orders only”).

If both exist, My default wins for you specifically.

If the report URL contains explicit filter / sort / view-mode parameters (typically because someone shared a link with you), the URL wins over both defaults. The plugin will still load the default profile in the background so its name shows as selected in the sidebar, but the URL parameters override the stored filters.

This makes shared links predictable — what the sender sees is what you see.

In the right-sidebar list, hover any profile to expose context actions:

  • Edit — change the name, toggle defaults
  • Delete — remove the profile

Deleting a profile that’s set as your default falls back to the global default; deleting the global default falls back to the plugin’s built-in defaults.