Give Access a Purpose and an End

The concept

An account should have the access needed for its current role, with additional privileges granted deliberately. This is the practical idea behind least privilege. Separate ordinary work from administration where appropriate, review who can see sensitive records, and remove access when responsibilities change. Shared passwords make individual accountability and prompt removal harder.

Worked example

A fictional arts organization invites a temporary designer to update an event page. The designer needs editing rights for that content, not the entire membership database or billing settings. A coordinator grants a limited role and schedules its removal when the contract ends. Later, the designer's personal email is compromised, but the narrow permissions limit the potential impact on the organization's other services.

Limits and judgment

Excessively restrictive permissions can create workarounds, such as staff sharing an administrator's password to get necessary work done. Design usable roles and a quick process for legitimate requests. Periodic reviews should consider old integrations as well as people; an abandoned application may retain powerful access. Write down why a permission exists, who approved it, and when it should be reconsidered.

RETRIEVE. REASON. REMEMBER.

Knowledge check.

Choose one answer for each question, then check your reasoning.