All notes

Architecture in practice

From a requirement to an access decision

A collaboration requirement becomes useful when it explains who needs to do what, with which information, and for how long.

Joas Haster English

“The project team needs a shared place to work” is a reasonable starting point. It leaves several decisions open.

Which people belong to the team? What work should they be able to do? Does everyone need to see every document? What happens when someone leaves?

A useful access design makes those questions explicit before they disappear into a set of permissions.

Describe the work first

Consider an illustrative project with three contributors and an external reviewer. The contributors write a report together. The reviewer needs to comment on a selected draft.

The requirement can be made more precise:

Contributors need to edit the working report. The reviewer needs to read and comment on the selected review version until the review is complete.

That sentence gives the design something to preserve. It distinguishes contribution from review and connects each activity to a particular version of the material.

Follow the requirement into a decision

Question Decision for this example
Who needs access? The named contributors and the invited reviewer.
What do they need? Contributors use the working material; the reviewer receives the selected review version.
What may they do? Contributors edit; the reviewer reads and comments.
When should access change? Review access is revisited when the review closes; contributor access when project membership changes.
Who is responsible? A named workspace owner handles invitations, changes and removal.

Different platforms may realise these decisions in different ways. The requirement remains useful because it describes the intended result independently of the configuration.

If a chosen tool cannot distinguish commenting from editing, that limitation needs a decision: accept broader access, use a different review mechanism, or change the requirement deliberately.

Check the result from the participant's position

An administrator seeing the correct settings is one part of the check. The people doing the work also need to be able to complete their task.

For this example, useful checks are concrete:

  • Can a contributor open and edit the working report?
  • Can the reviewer find the selected version and leave a comment?
  • Is unrelated working material outside the reviewer's access?
  • Does the agreed access change happen when the review ends?

These checks connect the original requirement to behaviour someone can observe. They can also reveal a usability problem: access may be technically correct while the invitation points to the wrong place or leaves the next step unclear.

Keep the connection available

A compact record can link the requirement, the access decision, the responsible person and the observed check.

That connection matters when the team changes. A new reviewer or an additional workstream should prompt a question about the work and its audience. The existing permissions then become a design to reassess, rather than a pattern to copy without context.

The practical test is whether another person can explain why the access exists and what should cause it to change.