Loading
Module
Company profile, departments, team roles with permission presets, overtime policy, integrations, a custom domain for your careers page, and your own brand color carried across the app, the emails and the PDFs.
What this solves
The difference between software you tolerate and software you trust is usually in the settings. Can you say what your overtime rule is, once, and have it applied? Can you give the payroll person payroll access without also giving them the hiring pipeline? Does your company’s name and color appear on the document you send an employee, or does the vendor’s?
OneclickHR treats those as first-class settings rather than configuration you file a support ticket for.
What is included
Your organization’s own details, including the timezone every attendance and calendar date is computed in.
Structure the organization the way it is actually structured, so views and permissions can follow it.
Granular roles configured from presets, so a payroll person and a recruiter see different things without anyone assembling permissions one checkbox at a time.
Write the overtime rule down once. Payroll runs apply it to attendance and timesheet hours rather than relying on someone remembering it.
Connect Google Calendar and manage the integrations your workspace uses. Third-party tokens are encrypted with AES-256 before storage.
Point your own domain at your public job board so your careers page lives on your brand, and the search ranking it earns stays yours.
One color applied across the app, the transactional emails, and the generated PDFs — payslips, invoices and HR letters.
See how much document storage the workspace has used, so a limit is something you plan around rather than discover.
Permission systems fail in two directions. Too coarse, and the only way to let someone approve a timesheet is to make them an admin. Too fine, and every new hire needs a forty-checkbox configuration session that nobody gets right twice.
Permission presets sit in between: a role carries a coherent set of capabilities that matches a real job, and you assign the role. The underlying permissions are still granular — the preset is how you avoid having to think about them.
Whatever a role grants, the boundary is enforced in the database. A user’s organization and role travel in their signed auth token, and Row Level Security decides what rows they can read. That is why deactivating someone takes effect immediately: access is re-checked from the database on every request rather than trusted from a token issued an hour ago.
Workspace settings shares its records with the rest of the workspace, so these modules read the same data rather than a copy of it.
Sign your organization up, configure your timezone and brand color, and invite your team. You can be running the same day.