Responsible systems

Grant the access needed for the task

Editorial edition · 16 November 2026

The idea

Access should match a clear task and scope. A person who only needs to read a report usually does not need to modify its source tables. Smaller permissions reduce the consequence of mistakes and make reviews easier to understand.

Design choice

Prefer roles with documented purposes over a growing set of personal exceptions. Keep privileged operations separate from ordinary work. Review temporary grants when the task ends, rather than assuming that an old permission is still justified.

Worked example

An analyst receives read access to a curated dataset. A separately authorised maintenance role handles schema changes and records each use of that privilege.

Before you ship

  • Map permissions to tasks
  • Separate routine and privileged access
  • Expire temporary grants

Examples are illustrative. Adapt the checks to your own environment.

Further reading

W3C provenance overview

Search the library