Setting up · page 7 of 13
People, seats and invitations
Constat asks who a person is once, and what they may do per project where it matters.
The three roles
| Role | May |
|---|---|
| admin | Everything, including people and settings. |
| author | Write and approve requirements, dispatch attempts. |
| reader | Read. Nothing else. |
Being a judge is separate
A judge is named per project, not per organization, because the person who should judge the mobile app is not always the person who should judge the billing service.
An organization admin can name a judge on a project from People. Until somebody is a judge on a project, no verdict can be given there — and nor can a requirement be approved, which is the usual reason a newly created project seems to refuse everything.
Inviting somebody
An invitation carries a role and, for a judge, the project they will judge. Both are on the same line, so you never send an invitation and then remember to grant something.
By email — Constat sends the invitation through your sender, with a link.
By GitHub username — for somebody you already know is on GitHub.
People shows, for each invitation, whether it was sent, opened, or signed in. An expired link offers to ask for a new one through whoever sent it.
What a reader actually gets
A reader invited by email opens the record from the link alone, with no GitHub account. That is the point of the seat: a client or a manager should be able to read a sealed record without being made to join anything.
A judge invited by email is told, on arrival and before any verdict is refused, that judging needs a GitHub sign-in. Constat says so at the door rather than after they have read everything and pressed a button.
Removing somebody
An admin can change a role or remove a member. You cannot remove the last administrator, and Constat says so rather than letting the room lock itself.
What people cannot do
Nobody can accept work they are not a judge of. Nobody can change a requirement's words after it is approved — the words freeze, and that is what makes the evidence mean anything. And no role lets a person edit what CI observed.
Who can judge here, and what does each seat allow?
Everyone in the organisation is an admin, an author or a reader. Judging is a separate seat, given per project: only a project's judge can approve its requirements and give verdicts there. A project with no judge can be read but not moved. A reader cannot give a verdict. Seats are set on the People page.