Skip to content
Blog

Understanding module-action permissions in Jwalix

By Jwalix Team

Permissions in Jwalix are granular strings like jobs.edit or candidates.delete rather than one-size-fits-all roles. Here is how to think about assigning them.

Most tools give you a handful of roles: admin, manager, user. Jwalix works differently. Permissions are granular strings such as jobs.edit or candidates.delete, assigned per person. Here is how to think about using them.

The idea: module plus action

Every permission names a module (jobs, candidates, reports) and an action (view, edit, delete). Read-only access to one module and full control of another is a normal configuration, not a special case.

A practical way to assign them

  1. Start from the job, not the title. Ask what the person actually needs to do each week.
  2. Grant the smallest set that works. A hiring manager may need to view applications and add interview feedback, but not delete candidates.
  3. Keep destructive actions rare. Actions like delete are worth giving to very few people.
  4. Review when roles change. Because permissions are per user, a change of responsibility is a quick edit.

Why this is safer

Permission checks run on the API route as well as in the interface, so hiding a button is never the only thing stopping an action. The same checks apply to the AI Recruiter and to external agents connected over MCP: if you cannot do something, neither can they on your behalf.

More on how access and data separation work is on the Security page.

Back to all articles

See Jwalix on your own workflow

Jobs, candidates, applications, interviews, and reporting in one workspace.

Chat with our friendly team of experts