Enable the Job library, then add levels, roles, and job profiles in the Job library table. You can add rows one at a time or import them in bulk from a spreadsheet.
Build the parts in order: levels and roles first, then job profiles, because each profile references one role and one level.
To learn what each part of the Job library does, visit Job library overview.
Before you begin
For access to Job library, you need the Tables add-on.
To enable or disable Job library, you need Owner or Admin permission.
To manage levels, roles, and job profiles, you need the Edit permission for Job library details. To learn more, visit Manage Job library permissions.
To create the Job library table, you need permission to create tables.
Step 1 - Enable Job library
Go to Settings.
Click Job library.
Click Edit next to Job library.
Select Enabled.
Click Save.
Humaans shows the message "Job library has been enabled" and lists existing job profiles.
Step 2 - Open the Job library table
Go to Settings.
Click Job library.
Click Edit next to the job profiles count.
The Job library table opens in Tables with three default views: Job library profiles, Job library roles, and Job library levels.
Step 3 - Add levels
Levels need a track, a name, and a grade. Add levels before job profiles.
Open the Job library levels view.
Add a row.
Enter a Code, for example L5.
Enter the Name, for example Senior.
Enter the Track, for example Individual contributor.
Enter the Grade as a number.
Enter the status, Active or Archived.
Click Apply changes.
Step 4 - Add roles
Roles need a code, a name, a function, and a family.
Open the Job library roles view.
Add a row.
Enter the Code, for example SWE.
Enter the Name, for example Software Engineer.
Enter the Function, for example Engineering.
Enter the Family, for example Software Engineering.
Click Save.
Note: Each role code and each role name must be unique.
Step 5 - Add job profiles
A job profile combines one role and one level.
Open the Job library profiles view.
Add a row.
Enter the Code, for example SSE.
Enter the Job title, for example Senior Software Engineer.
Select the Role.
Select the Level.
Enter an External job title if necessary.
Click Save.
Each profile code must be unique, and each role and level combination can have only one profile.
When you change the job title of a profile that people use, Humaans updates the job title of each linked person.
Import levels, roles, and job profiles in bulk
You can import into each tab from a spreadsheet. Humaans matches imported rows to existing rows so you can update existing data as well as add new data:
Tab | Matched by |
Job profiles | Code, then Job title |
Roles | Code, then Name |
Levels | Code and Track, then Name and Track |
For the import steps, visit Importing users in bulk with Tables. To learn more about editing data in Tables, visit Tables: Editing data.
Archive or delete levels, roles, and job profiles
To archive a row when you want to stop using it but keep its history:
Click Active in the Status column of the selected row.
Select Archive.
Click Apply changes.
Archived rows don't appear as options when you create a job profile.
To remove a row completely:
Select the row(s) you want to delete.
Click Delete at the top of the table. It appears only once you've selected a row.
Click Apply changes.
The tables show only Active rows by default. To see archived rows, change the Status filter. To restore a row, select it and click Unarchive.
You can't delete a row that's in use. To remove a row that's in use, reassign or remove the people or job profiles that use it first, or archive the row.
Disable Job library
To disable the Job library, you need Owner or Admin permissions.
Go to Settings.
Click Job library.
Click Edit next to Job library.
Select Disabled.
Click Save.
When the Job library is disabled, Humaans hides Job library features and people keep their current job titles. Assigned job profiles are no longer visible. Your library data is kept.
You can't disable the Job library while request types use Job library filters or approval conditions. Update or remove those request types first.
Saved report filters and workflow filters don't block you from disabling the library.







