Some competencies only count when the person holds a valid professional licence: a nurse registered with SCFHS, an engineer registered with SCE. Accreditation is how Jadiroon records those licences and shows the result next to the competency. Verification is pluggable by licence type and specialty, with manual review by HR; sector registries are connected during onboarding.
A licence is a legal credential, not training. It never changes a competency level. It only decides whether a competency that requires verification shows as verified.
Licence checks
An employee records a licence from My credentials by choosing the type Professional licence, picking SCE, SCFHS, SOCPA or NCA, and entering the licence number. Jadiroon sends the number to the registry configured for that licence type and records the answer every time, so each check stays in the licence's history.
| Registry answer | What happens |
|---|---|
| Active | The licence is verified and takes its expiry date from the registry. |
| Not active, or not found | The licence stays awaiting review. HR sees the result and decides. |
| Pending | The licence stays awaiting review and shows "Pending at registry". |
| Unavailable | The licence stays awaiting review and shows "Registry unavailable". HR can retry. |
A check never downgrades a licence that is already verified, and never rejects one.
Manual review and the demo registry (only where enabled)
Every workspace starts on Manual review: Jadiroon calls no external service, every licence waits for HR, and HR verifies it by hand after looking at the issuing body's own register. When verifying by hand, HR can type the licence's Specialty so competencies that require one can match it.
Where the platform administrator has turned it on, a Demo registry is also available. It answers instantly from the licence number and calls no real service: numbers starting with 000 are not found, 999 are not active, 555 stay pending, and any other number is active for one year. It exists to try the flow and is labelled as a demo wherever it verifies a licence. Real registries are added one at a time by the platform team and call in-Kingdom endpoints only.
Pending at registry
Some registries answer later. Until they do, the licence shows Pending at registry and counts as not yet verified. HR can press Verify with registry at any time to ask again, from Develop → External credentials or from the person's page. Each attempt is added to the history; none of them overwrites an earlier answer.
Flagging a competency
Open a competency and use the Verification card to say that it only counts when the person holds a valid licence. You need the permission to edit the functional structure.
- Licence type. Choose SCE, SCFHS, SOCPA or NCA.
- Required specialty (optional). Leave it empty to accept any specialty. When filled, the person's licence must carry that specialty, for example "Psychology" for an SCFHS licence. Where the demo registry is enabled, the card lists its specialties as a hint.
- Registry. Choose Manual review, or the Demo registry where it is enabled. There is one registry per licence type: the choice applies to every competency in your workspace that uses the same licence type, so saving one rule updates the others. If a stored registry is no longer available, the card says so and checks fall back to manual review.
- Notes. Optional Arabic and English notes for reviewers.
You can flag global competencies as well as your own. A global competency is flagged for your workspace only: the competency itself is never changed and other workspaces do not see your rule. Archived competencies keep their rule, and you can still edit it, but you cannot add a rule to an archived competency.
Flagged competencies show a shield icon in the competency list. Settings → Develop → Accreditation lists every flagged competency with its licence type, specialty and registry, and shows which registries are available.
Marks and expiry
Each flagged competency carries one of three marks on the person's page and on My competencies:
| Mark | Meaning |
|---|---|
| Verified | The person holds a verified licence of the required type, with the required specialty if one is set, and it has not expired. The tooltip shows the expiry date. |
| Expired | A matching licence was verified but its expiry date has passed. |
| Verification required | No matching verified licence yet. If a licence was submitted and the registry answered, the registry result (for example "Pending at registry") appears next to the mark. |
Expiry is checked every time the page loads, so a licence flips to Expired the day after its expiry date without anyone touching it. Competencies that are not flagged show no mark.
Verified practitioner
A person shows a Verified practitioner badge in their page header when their current job description contains at least one flagged competency and every flagged competency in it is Verified. Only the competencies of the job description count; flagged competencies outside it do not affect the badge. Without a flagged competency in the job description there is no badge.
Automatic check when a flagged competency is assessed
When an employee completes an assessment that covers a flagged competency, Jadiroon re-checks that person's licences of the required types that are still awaiting review. Verified licences are not re-checked. A licence is only re-checked if its latest check is missing or more than 24 hours old, so a recent answer is reused, and a licence already pending with a manually reviewed registry is not asked again. The check runs in the background and never delays or blocks the assessment. Candidate assessments in a hiring pipeline do not trigger it.
Opening requirements and the HR re-check
An opening can list accreditation requirements (see Creating a role). Applicants answer them on the application form. When a portal applicant's licence fails the registry check and the requirement is mandatory with auto-reject on, the application is excluded automatically with the reason Accreditation and no email is sent. A pending or unavailable registry never excludes anyone. HR can enter a licence number or re-check one on any application, however the candidate arrived; a re-check never excludes. See Working the pipeline.
Licences copied at hire
When a candidate is hired, every licence that was verified on their application is copied to the new employee as a verified licence credential. It happens whichever way you hire: the Hire button or dragging the card to Hired.
- The credential shows Copied from application on the person's page, with the licence type, number, expiry and the registry check as its first history entry.
- A licence the employee already holds with the same type and number is not copied again, so hiring twice never duplicates it.
- Licences that were only declared, pending at the registry, failed or not checked are not copied.
- If the copy cannot be completed, the hire still goes through; add the licence to the employee's page by hand.