Skip to main content
An applicant source records where a candidate came from — your careers site, LinkedIn, a recruitment agency, an employee referral, a walk-in, and so on. Maintaining a tidy list of sources, and tagging each applicant with one, is what lets Hitaji 360 tell you which channels are worth your time and money: the dashboard’s source-effectiveness chart groups applicants by source and shows how many from each were ultimately hired. This page covers creating and managing your list of sources. You’ll find this at: /hr/recruitment/applicant-sources
📷 Screenshot: Applicant Sources grid with the “New Source” button — to be added.

​
Before you start

  • Applicant sources are master data, managed with the hr-recruitment:config permission — the same level used for interview types, opening templates, and offer-term templates. With only hr-recruitment:read you can see the list but not change it.
  • A source created with a business selected in the switcher belongs to that business; a source created with no business in context is shared across the whole tenant. In normal use, your sources belong to the active business.

​
Managing sources

The page is a simple searchable grid of source cards. Each card shows the source name and its description, with edit and delete actions (visible only with hr-recruitment:config).

​
Creating a source

Choose New Source. A dialog opens: Save with Create. To change a source later, open it, edit, and choose Update.

​
Deleting a source

The delete action (trash icon) asks you to confirm (“Delete this source?”). Deletion is a soft-delete — the source is hidden from the list, not destroyed — so applicants that were already tagged with it keep their value.

​
How sources are used

When you add or edit an applicant, the Source dropdown is populated from this list. The source you pick is what the dashboard groups by in the source-effectiveness chart and what the Source filter on the applicants board uses.
⚠️ Current state: The applicant’s source is stored as the source’s name rather than a hard link to the source record. In the app you always pick from the dropdown, so this is rarely a problem; but it does mean that renaming a source here won’t retroactively re-label applicants already tagged with the old name, and there’s no hard guarantee at the data layer that an applicant’s source matches an entry in this list. Keep source names stable. (Noted for awareness.)

​
Permissions