Pending Approvals

It shows one total number for all pending items, then breaks that total into pending leave requests and other approval requests. The widget is designed for a dashboard, so it is a quick status view rather than a full workflow screen. The built-in link text says "View all," but the widget itself is non-functional and meant to point users to the full approvals area.

This template fits managers, team leads, HR coordinators, or operations staff who need a fast read on items awaiting approval. It is especially useful when approvals are spread across more than one record type and people need a single place to see what is waiting. If one person owns all approvals, the widget still helps them spot backlog at a glance.

The template is set to refresh every 600 seconds, so it updates on a regular dashboard interval without constant polling. That cadence works well for a summary widget where users need current counts, not second-by-second changes. If your approval volume changes quickly, you can shorten the interval during customization.

No. This is a summary widget, not the workflow itself. It surfaces pending counts from leave requests and approval requests, but users still need a list or detail screen to review, approve, reject, or comment on each item. It works best as a front door into the full approvals process.

The biggest mistake is treating the widget as the source of truth instead of the underlying record lists. Another common issue is not defining what counts as "pending," which can make the total misleading if statuses are inconsistent. Teams also forget to connect the widget to the right approval records, so the number looks useful but does not reflect actual work waiting.

Yes. The template uses warning coloring when the total is above 5 and danger coloring when it is above 10, but those thresholds are easy to adjust. Many teams tune the cutoffs to match their own SLA or manager workload. You can also change the labels if your organization uses different approval categories.

The widget reads from platform APIs, so it can sit on a dashboard alongside other operational widgets without duplicating data entry. It is a good companion to leave management, request intake, or back-office approval apps that already store pending records. If you later add notifications or escalation rules, the widget can stay as the visual summary while those automations handle follow-up.

It can be, as long as the underlying approval records are managed with the right permissions and audit trail. The widget itself only displays counts, so the compliance burden sits in the source records and approval workflow. For regulated environments, make sure the full approval history, role separation, and retention rules are handled in the connected app.