Background

The approvals gadget is fully configurable, but most users want a ready answer rather than a configuration wizard. The catalogue of predefined templates lets a user add a gadget in a single choice: the user picks a preset in the gadget edit view, and the type, dimensions, measure and display options are set upfront. A preset is nothing more than a ready configuration of the generic gadget: once added, it behaves exactly like a manually configured gadget and can be freely modified. The default views (personal and admin) are composed from this catalogue.

Placement in the gadget wizard

In the gadget edit view, before manual configuration, the user sees a template selection step: a list of presets grouped into Personal defaults and Admin defaults, each with a short description, plus an option to start from an empty configuration. Selecting a preset fills in the configuration and shows the preview; everything remains editable.

Roles and sharing

A preset does not define the data scope. The scope follows from the gadget visibility model, computed server side for each viewing user: a global admin sees all approvals in the instance, a regular user sees only their own. The catalogue is shared: both groups are visible to everyone, and the grouping is a hint, not a permission. On a shared dashboard every viewer sees the same gadgets with data computed for themselves; a regular user sees the admin presets narrowed to their own approvals.

Preset catalogue

Personal defaults, answering "what needs my attention":

• Approvals awaiting my decision: a table of approvals awaiting the current user's decision, based on the dynamic "current user" filter, sorted by decision deadline ascending. The primary work queue with voting directly from the gadget.

• Awaiting your decision, by approval: a 2D table in Items mode, one row per approval name, with chips for the work items or pages awaiting the viewer's decision.

• My approvals by status: a pie chart of the viewer's approvals split into awaiting their decision, approved and rejected, with a total.

• My decisions this month: a KPI tile with the number of decisions made by the viewer in the current period.

• Created vs Resolved: a line chart of approvals created and resolved over time, to judge whether the queue is growing. Shared by both roles.

Admin defaults, answering "is the process healthy":

• Open approvals: a KPI tile with the number of open approvals in the viewer's scope.

• Approvals by definition: a bar chart of approval volume per definition, to point at the busiest processes.

• Approval outcomes by definition: a stacked bar chart of outcomes (approved, rejected) per definition, to point at processes with a high rejection share.

• Load by approver: a bar chart of approvals currently awaiting each approver, to point at bottlenecks.

• Cycle time by definition: a bar chart of the median time from creation to resolution per definition, to point at the slowest processes.

• Created vs Resolved: the same preset as in the personal group, in the scope following from the viewer's permissions.

Acceptance Criteria

Catalogue and wizard:

• The gadget edit view offers a preset selection step with the Personal defaults and Admin defaults groups and an option to start from an empty configuration.

• Both groups are visible to all users; each preset has a name and a short description visible before selection.

• Selecting a preset fills the full gadget configuration (type, source, dimensions, measure, display options) and shows the preview.

Behaviour after adding:

• A gadget added from a preset does not differ from a manually configured one and remains fully editable.

• The Approvals awaiting my decision preset uses the dynamic "current user" filter, so every viewer sees their own queue regardless of who added the gadget.

• Presets respect the visibility model: a global admin sees the whole instance, a regular user their own approvals; no preset exposes data beyond the viewer's entitlement.

Out of scope

• Creating and saving custom presets by users.