HR Omni

Returns the details of one HR Omni company. Use after get_my_access_context has resolved the intended company to companyId and the user asks about that company's own record. This is company-level organisation data and requires access to the company plus relevant organisation permissions. It does not return departments, modules, employees, reporting relationships, or leave data. Do not use for the authenticated user's profile, product-wide information, or another company the user cannot access.

Returns the configured company holidays and non-working days for one company, optionally filtered by year. Use when checking which configured dates affect working-day or leave calculations. These are HR Omni company settings, not a legal determination of public holidays. Leave Management must be enabled and the user must have access to the company with relevant leave permissions. Year defaults to the current calendar year and must be from 2010 through 2040; convert relative periods such as "next year" to an explicit YYYY. Do not use for a user's leave balance, leave requests, working schedule, or product capability questions.

Returns the authenticated user's HR Omni profile, accessible companies, and access-control role identifiers for each company. Use first to identify the user, resolve a company name to companyId, or understand available company contexts before calling a company-scoped action. It takes no arguments and operates only on the authenticated user; roles are included because organisation access is granted. Company access and roles can differ by company, and role names must not be used to infer permission for another action because HR Omni checks every request. Do not use for detailed company, employment, module, organisation-chart, or leave data.

Returns the authenticated user's current employment record for one company, or null when no employment record exists. Use for questions about the user's own department, manager, employment type, role, dates, or working schedule. This is self-only and requires access to the company plus relevant organisation permissions. Organisational roles describe the employment relationship and must not be treated as access-control roles. Do not use for another employee, company-wide organisation structure, historical employment events, or leave information.

Returns the authenticated user's leave summary for one company and optional year. Use for questions such as "what is my leave balance?", "how much holiday do I have?", or "how many days have I booked?" The response reports annual allowance, booked leave, requested leave, and carry-over days taken as separate values; do not combine booked and requested leave. This is self-only and should be preferred over company-wide leave actions for personal questions. Leave Management must be enabled and the user must be enrolled with active employment and a working schedule. Year defaults to the current calendar year; convert relative periods such as "last year" to an explicit YYYY. Do not use for leave history, individual request details, other employees, or product capability questions.

Returns the current organisation chart for one company, optionally limited to a department. Use for questions about current manager and reporting relationships across the company or within a department. This is company-wide organisation data and requires access to the company plus relevant organisation permissions; resolve a human department name with list_company_departments before passing departmentId. The chart reflects current employment relationships, and people without a manager may appear at the company root. Do not use for historical structures, access-control permissions, employment details for only the authenticated user, or leave data.

Lists departments for one company and returns their IDs and names, collecting bounded paginated results. Use to resolve a human department name to departmentId before a department-filtered organisation-chart or company-leave request. This is company-wide organisation data and requires access to the company plus relevant organisation permissions. The optional search accepts keywords; add * to a keyword for prefix matching. Do not use as an employee directory, for reporting relationships, for access-control permissions, or to create or change departments.

Lists company-wide leave requests for one company, with optional year, month, status, and department filters. Use when the user asks about other employees, a department, or company-wide leave; prefer list_my_leave_requests for "show my leave". Leave Management must be enabled, and HR Omni enforces company permissions plus approver or administrator scope. Year defaults to the current calendar year, omitted month includes all months, and omitted status includes all statuses. Convert relative periods such as "this month" to explicit year and month values. Status accepts a comma-separated selection of SUBMITTED, AUTO_APPROVED, APPROVED, CANCELLED, and DECLINED. Resolve a human department name with list_company_departments before passing departmentId. Do not use for personal leave balances or to submit, approve, or reject requests. If access or company context is rejected, surface that result rather than retrying with broader data.

Lists HR Omni modules for one company and whether each is enabled. Use to answer whether a module, such as Leave Management, exists or is enabled before calling a module-dependent action. This is company-level configuration and requires access to the company plus relevant organisation permissions. An enabled module does not prove that the user has permission to use every action in it. Do not use for product-wide capability questions, personal enrolment or entitlement, module data, or changing module settings.

Lists the leave types configured for one company, returning each type's ID, name, and colour. Use to answer which leave types are available or to resolve a leaveTypeId before preparing a leave request. This is company configuration data, not a personal leave balance. Leave Management must be enabled and the user must have access to the company with relevant leave permissions. Do not use to determine whether Leave Management is enabled; use list_company_modules for that. Do not use to submit, approve, or reject a request.