Building Brain™PRACTICAL RESOURCE LIBRARY

← All 30 articles

Team practices

Permission levels that match the work

A new staff member needs access to one set of maintenance records, but the easiest option appears to be access to the entire backend.

A useful distinction

Access should follow a person’s approved duties and the information necessary to perform them.

Start by describing the work, not choosing a software role label. A person arranging a maintenance visit may need contact and access coordination details but not financial, personnel or confidential tenancy records. The responsible owner should approve the scope and identify any exceptions. Avoid distributing sensitive information in a general task description.

Keep access arrangements separate from convenience. Shared personal accounts make it difficult to establish who changed a record or whether access was removed. Use the organization’s approved identity and administration process. Where the existing system cannot provide the required restriction, document that limitation and obtain an appropriate solution before expanding access.

Review permissions as part of handover and role changes. Confirm that necessary work can continue while unnecessary access is removed. Keep an administrative record of the change and its authorization. This article describes a management approach; it does not establish that a particular platform’s security controls have been implemented or tested.

Put it into practice

  1. Define the tasks and records the role actually needs.
  2. Use the approved account and permission process for that scope.
  3. Review access when duties change or the person leaves.

What to verify

Check actual permissions with authorized administrators, including direct access where appropriate. A menu hidden on screen does not demonstrate that underlying records are protected.

Your next step

List the minimum information required for one staff role.

Explore another question →