JobNav Templates

"Template" means two different things in JobNav, and they don't share an owner, a purpose, or a location. If you're not sure which one you're looking at, this is the quickest way to tell.

Job Profile Templates

These live under Libraries → Template and define the content of a job profile: locked sections, required language, and embedded instructions that guide whoever's writing the profile. They're built to match your HRIS, following the fields and structure your organization already has in your HRIS, rather than introducing a separate schema.

Job Profile Templates are content-driven, not a set of structured fields with allowable values. They're something your organization owns and manages directly, not a one-time setup handled during implementation.

Who can do what: Editors can apply templates to drafts. Only Admins can create or publish them.

Approval Templates

These define the architecture of an approval flow: how many stages, how many approver slots, and the shape of the review process. An approval template doesn't contain any actual people, it's the blueprint, not the roster.

Users (typically hiring managers or recruiters) then create a live approval flow from a template and assign real approvers to its slots. The template's structure can't be changed once a flow built from it is running, but approvers can still be added to open slots as the flow moves forward.

Who can do what: Any user can start a flow from a published template. Only Admins can create or publish the templates themselves.

For the full walkthrough, see Approval Flows.

The short version