Performance
Review cycles, the visibility rule, and goals.
The whole module exists to get one thing right: a manager's review of somebody is invisible to that person until HR deliberately shares it. A half-written review containing hard feedback that its subject can read is a catastrophe for everyone involved.
Who can see a review, exactly
- HR: always, at every status, both the manager review and the self-assessment.
- The reviewer: their own manager review always; the self-assessment only once it has been submitted.
- The subject: their own self-assessment always; the manager review only once it is shared or acknowledged.
- Anyone else: never.
Submitting is not sharing. A reviewer cannot push their own review to its subject — only HR can. And the permission that lets a subject acknowledge a shared review does not let them edit it.
Running a cycle
- 1Performance → Cycles → New cycle. Pick a template, choose participants, and adjust the reviewer column where the default reporting line is not who should write it.
- 2Launch creates every review at once, so 'not started' is a real countable state and the progress meter has an honest denominator.
- 3Share, per person or in bulk, when you are ready for people to read what was written about them.
Goals
Goals are the opposite of reviews: deliberately visible to the employee, their management chain and HR. A goal nobody can see is a private note. Each update is kept, so the history shows how progress actually went rather than only where it ended. Dropped is a neutral outcome — deciding not to pursue something is a legitimate result.
Does this not match what you see on screen? That's a bug in the guide — tell us and we'll fix it.