Screen reference
People and training
Who joined, who left, which trainings are done and which policies remain to accept.
What the screen is for
The app keeps only the Atlassian account, the dates and the status; the name comes from the Atlassian directory.
Who can do what
| Action | Reader | Compliance manager | Jira administrator |
|---|---|---|---|
| Open the page | no: "This page is restricted" | yes | yes |
| Add a person, edit their file, assign a training, mark it done | no | yes | yes |
The files name individuals and what they have not done: only people who run the compliance programme can read them.
Step by step
- Filter: All, Onboarding, Active, Left, With gaps, Training overdue, Policies to acknowledge; or search for a person.
- "Add a person": choose the account in the directory, the status and the start date. A person who left has an end date.
- In the drawer: "Assign a training" (title, due date), then "Mark as done". A person who left no longer receives training.
- "Policies to acknowledge" are read, not written, here: the person accepts on the policy itself (Policies). Any policy in force that requests an acknowledgement and addresses the person counts.
Gaps flagged
- left with trainings outstanding (trainings only: leavers no longer owe acknowledgements);
- end date passed, departure not recorded;
- onboarding for more than 30 days with no training done.
Known limits
- The rules "no training before assignment" and "rejected vendor" are not built.
- The policies-to-acknowledge calculation reads once per policy; it is not measured on a large site.
Was this page helpful?