Job Library keeps your company’s job titles, roles, and levels in one place. Create reusable job profiles and assign them to employees to keep job information consistent across Humaans.
The Job library lives in Tables and is available to companies with the Tables add-on. To learn how to build your library, visit Set up the Job library.
How the Job library is structured
The Job library has three parts, levels, roles, and job profiles. You assign a job profile to a person. The person inherits the role, function, family, level, track, and grade from that profile:
Term | Meaning |
Function | A broad area of work, such as Engineering |
Family | A group of related roles within a function, such as Software Engineering |
Role | A type of job, such as Software Engineer, with its own code, function and family |
Track | A career path, such as Individual contributor or Management |
Level | A stage within a track, such as Senior, with a name, grade, and optional code |
Grade | A whole number used to compare seniority across tracks. |
Job profile | A combination of one role and one level, with a unique profile code and a job title. |
Understand levels, tracks, and grades
A track is a career path, such as Individual contributor or Management. Each level belongs to one track.
A grade is a number you set on each level. Levels on different tracks can share a grade to show they're equivalent in seniority. For example, a Senior Engineer and a Manager can both sit at grade 5.
A level's code is optional. Use it for short labels such as L5 or M3.
Understand roles, functions, and families
A role describes the work itself, independent of seniority. Each role has a function such as Engineering, and a family such as Software Engineering. A role requires a code, a name, a function, and a family.
Understand job profiles
A job profile pairs one role with one level. Each profile has:
A code
A job title, which is the title shown in the People directory and on profiles
An external job title (optional), for example a public or recruiting title
Each role and level combination can have only one job profile, and each profile code must be unique.
What happens when you assign a job profile
When you assign a job profile to a person, Humaans fills in their job title from that profile. If you later change the profile's job title, Humaans updates the job title of every person linked to that profile.
Note: Existing job titles aren't linked to job profiles automatically. People keep their current titles until you assign a profile. Existing job title filters continue to match on exact title names.
Control access to job information
Permissions control who can manage Job Library and which details people can see. For a more detailed overview of permissions and the job library, visit Manage Job library permissions.
Can view and manage the job library controls access to maintaining profiles, roles and levels.
Separate permissions control access to levels, tracks, grades, role names, role codes, functions, families, profile codes and external job titles. Level names and codes share a permission.
Can access everyone’s job level and track provides visibility of those details across the People directory.
Assigning a job profile to an employee also requires permission to create or edit that employee’s job role records. Sharing a table doesn’t override role permissions.
To learn more, visit Managing Permissions and Roles and Sharing Tables.
Where you can use Job library data
Employment details: The job profile appears in a person's Role card, depending on the viewer's permissions. To learn more, visit Assign a job profile to a person.
Requests: Use job profile, role, function, family, level, and track to decide who can submit a request and how approvals route.
Workflows: Use job profile details as email tags and as enrolment trigger filters.
Reports and exports: Include Job library details in reports.
API: Read and write levels, roles, and job profiles through the Humaans API using the jobLibrary:read and jobLibrary:write scopes.


