What this does
These three admin tools let you fit WorkRight to a more complex organisation. Legal entities let one company manage several registered entities (each with its own currency, financial-year start and tax ID) and switch between them. Custom fields add your own data points to the employee record. Custom roles grant a precise set of capabilities beyond the five standard roles.
Who can do it
- Entities: HR admins (
company_admin/hr_manager) manage legal entities; others see them read-only. - Custom fields & roles: managed by an HR admin or anyone holding the matching administration capability (
customfield.adminfor fields,role.adminfor roles). - Plan: custom fields and custom RBAC are enterprise-gated features. See pricing or our billing guide.
Steps
- Add a legal entity. Go to Settings → Entities and click Add entity. Set the name, a short code, the country and currency, an optional tax ID (GSTIN / PAN) and the financial-year start month. Mark one entity as primary — it's used whenever no specific entity is selected. You can edit or archive non-primary entities later.
- Add a custom field. Go to Settings → Custom fields and click New field. Pick a type (text, number, date, single- or multi-select, or yes/no), group it under a section, mark it required if needed, and set a view and edit capability so sensitive data stays restricted. The field then appears on the employee profile.
- Create a custom role. Go to Settings → Roles and click New role. Name it, then tick capabilities from the module × action matrix. Custom roles only addpermissions on top of a member's base role — they never remove access — and you can only grant capabilities you hold yourself. Assigning a high-risk capability prompts for a step-up 2FA code.
Tips
- Grant the least access that gets the job done — custom roles are for narrow, specific jobs (e.g. a payroll operator), layered on top of the standard role.
- Deleting a custom field hides it from profiles but keeps the stored values, so nothing is lost if you change your mind.
- You can't archive the primary entity. Set a different entity as primary first if you need to retire it.
Related
- Billing & plans — how enterprise-tier features are unlocked.
- Create an API token — capabilities also govern what an API token can do.
- Pricing — which tier includes multi-entity, custom fields and custom roles.