Apply least privilege without blocking legitimate work
Separate everyday access from administration, grant permissions for a defined task and review access when the task ends.
In brief
Least privilege means granting the access needed for a job and no unnecessary extras. It is a practical way to reduce the damage from a mistake or compromised account, not a rule that every permission must be removed.
A task-based permission record makes access review possible even for a small organization.
Describe access as an action
“Read one report” is a clearer requirement than “needs the dashboard.” Separate viewing, editing, exporting, billing and permission management. Use the product’s available roles and inspect what each role really allows rather than inferring from its name.
Keep elevated work deliberate
Use individual accounts with appropriate authentication. Elevate for a specific task where the platform supports it, and avoid keeping a broad token in an everyday script. A deployment process can have a different role from the person reviewing content.
Review without a lockout
Before removing an old account, identify anything it owns and transfer ownership through the supported route. Verify a remaining administrator and recovery method. Record the reason and date of each grant so temporary access does not silently become permanent.
Before you act
Removing access blindly can break backups or recovery. Keep a protected emergency route and test changes before deleting the only administrator.
What to do next
- List the person or process, its actual task and required resources.
- Use a limited role for normal work and a separate controlled administration path.
- Review access after project changes or departure, checking that backup and recovery still work.
