Knowledge base / Brillienta HRMS / Why this product
Why Brillienta-HRMS
Questions that decide cost, risk and adoption — and how this system answers each one.
| Question to ask any HR system | Brillienta-HRMS |
|---|---|
| Where is our HR data stored? | In SharePoint lists on your own HR site. No vendor database, no third-party service. |
| What infrastructure do we need? | None beyond SharePoint Online. No servers, jobs or connectors to run or pay for (one optional Power Automate flow for email). |
| Do people need another sign-in? | No. Employees use their Microsoft 365 identity, inside SharePoint, with self-service everywhere. |
| How do concurrent edits stay safe? | Record-level saves, version-checked reference numbers, and live refresh — a stale page can never delete others' records. |
| Who controls access, and how is it enforced? | Your SharePoint permissions plus app roles plus plan. Payroll, reviews, recruitment and licence keys closed in SharePoint; privacy enforced by SharePoint. |
| Can we prove who changed what? | Decision trails on records, setup/upgrade logs, sync activity, Outbox delivery states, SharePoint version history. |
| Is it more than forms? | Action centre with inline approvals, team calendar, pipeline board, scorecards, dashboards per app, report builder, org chart, kudos, reminders. |
| Can we make it ours? | Brand colour, logo, theme, landing app, leave/attendance/SLA/expense/payroll policies, custom columns, email wording and layout — all in Settings, no code. |
| How are upgrades handled? | Deploy the package; first list-manager visit upgrades additively. Validate/repair any time. |
| What happens to our data if we stop? | It stays where it always was: in your SharePoint lists, readable in views, Excel and Power BI. |
Still need help?Our team answers product questions by email, and we can walk you through it on a call.
Open in the full guideContact support