Leave Requests

#About Leave Requests

Manage employee leave requests. This is a working page: a list or workspace where you find and act on records in BSuit ERP (Human Resources). It is used by staff (internal users). What you can see and do depends on your role and permissions.

#How to open it

In BSuit ERP, open Human Resources and choose “Leave Requests”, or go directly to the address /hr/leave-requests.

#What you can do here

These controls are present in the page’s implementation. Whether you see a given one also depends on your permissions and on the data shown.

1. Add new records — a form opens for the details.
2. Change existing records.
3. Delete records (you are asked to confirm).
4. Bring records in from a file.
5. Submit, approve or reject through a workflow.
6. Search within the page.
7. Open dialogs or drawers for detail and confirmation.

#Who can do this

Super Admin and other superuser accounts can always see and do everything, regardless of this list. For everyone else, these are the standard roles that have been granted a permission here in this system’s current setup — an organisation can add, remove or customise roles and their permissions, so treat this as an example, not a guarantee.

#Data stored for each record

The form layout of this page could not be read from its source, so here is everything BSuit stores for a leaverequest (see also the LeaveRequest data reference). Which fields appear on screen depends on the page and your configuration.

#Observed on a running system

On 2026-09-21 this page was opened in a browser as a test administrator. This is what was visible on screen under the heading “Leave Requests”. Your own view can differ with your role, data and settings.

#If something is missing or fails

1. No data: confirm the company or context selected in the top bar, and any filters or date range in use.
2. An action is hidden or disabled: it usually needs a permission your role does not have. Ask an administrator to check your effective access.
3. An error message appears: note the message, the page address and what you were doing, and contact support with those details (never include passwords).

#About this guide

This guide was generated from the page’s implementation. It has not yet been reviewed by a person against a running system, so treat it as a reference for what the page contains rather than a complete procedure.