How review works
Review in iyedy always concerns one version of a diagram. On your own, you are the one who signs it off, and the people you ask give opinions. In an organisation, the author asks colleagues, and their verdicts decide. The checks run without AI on every change, whichever way you work.
On this page
Two ways to conclude a version
How a version concludes depends on where the diagram lives, never on your plan.
| On your own (My diagrams) | In an organisation (Team, Enterprise) | |
|---|---|---|
| Who concludes | You, the author: Author sign-off | The approvers you ask: Review |
| Who else takes part | People you invite give an opinion that never counts | People, directory groups or workspace roles give a verdict |
| The words you see | Sign-off, opinion, In favour | Review, approver, Approve |
| The result | Approved, signed off by the author | Approved once enough approvals are given |
On your own: author sign-off
In My diagrams, you sign off your own version. Before that, you can ask a person who has access for their opinion: they answer In favour, In favour with a condition or Changes requested. Their opinion shows in the diagram's history and in the sign-off pack, never under Approved by. The sign-off stays yours.
In an organisation: review with approvers
In an organisation, the author asks for a review and others decide (four eyes): the author gives no verdict. By default, one approval from an editor of the workspace is enough. Each approver chooses Approve, Approve with a condition or Request changes. The version is Approved once the approvals needed are given; one request for changes moves it to Changes requested.
The organisation's review policy can ask for more: several approvals, required reviewers, guests whose opinion counts. See Request a review.
What a verdict covers
A sign-off, an opinion or a verdict covers the whole version that was asked for: its changes and the decisions that come with it. If the diagram changes after the request, the change makes a new version. In an organisation, the author resubmits it so that approvers review that version; on your own, your sign-off then covers the newest version.
There is at most one open review on a diagram at a time.
The open HIGH finding rule
A finding of severity HIGH that is still open asks for more than a plain approval: a condition written with the approval, or an accepted risk with its reason. On your own, this is your rule, on by default, and you can turn it off in your settings. In an organisation, the review policy sets it.
Where the result shows
- The status stamp of the version: Draft, In review, Changes requested, Approved, Withdrawn or Superseded. See Status stamps.
- Approved by, in the Inspector: filled by the sign-off or the review, never typed by hand.
- The history of the diagram: who asked, who answered, when.
- The review pack (PDF), called the sign-off pack on your own. See Create a review pack.
Comments
Comments are open during a review and outside it. They sit on an element, a relationship or a view, and keep the version they were written against. See Comment on a view.
What this means for you
- You work alone: save your version, read the checks, then sign it off. Ask for an opinion when a second pair of eyes helps.
- You work in an organisation: request a review and say in one sentence what is decided; your approvers read that first.
- You were asked: open the link you received and give your verdict, or your opinion as a guest. It is free. See Review and sign off a version or Give your opinion as a guest.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.