People and access

The people register connects a person’s name and role title to a user account. It also records whether that person is active. Field tasks assign a person, treatment applications identify an applicator and findings name the person who accepted a measurement. Those references make site work reviewable across a shift change. A typed name in a note cannot provide the same dependable link to the actor who had access at the time.

The user register provides account identity and a platform role value. During setup, the admin maps the operational responsibilities for managers, operators, surveyors, reviewers and custodians to actual permissions. A user marked Pending should not be treated as an active actor for work decisions. A person marked inactive should be removed from new assignments while their prior records remain understandable.

• Identity. Link each active person to the appropriate user record.
• Responsibility. Assign tasks and review findings through person references.
• Access. Test record visibility and update rights with the actual user’s account.

Decide which manager can approve a task and which reviewer accepts a finding. Separate those duties where the team’s policy requires an independent review. Define how an operator is deactivated when leaving a project or changing assignments. Check that the person and user records point to the correct individual, especially when several people have similar names. The user email and role value help identify an account, but the working record should carry the person reference.

Review direct record access as well as saved screens. A limited user should not be able to change a site status through an API route when the interface hides the edit control. Test access with an active operator, a reviewer, a manager and an inactive person. Maintain historic attribution rather than replacing a departed person’s identity with a successor’s.

At Willow Bend, the manager assigns a field task to the operator’s person record. The operator locates the task by assignee and completes the work. The treatment application names its actual applicator. The finding reviewer checks the recorded measure and accepts it under their linked identity. When the manager later reviews the autumn cycle, each action points to the person responsible. If a user account is disabled, a different active person must be assigned before the next task begins.

• Field Tasks by Assignee — Approved and ongoing work with the assigned person shown.
• Tasks Awaiting Approval — Planned work for the manager’s decision.
• Dated Cycle Findings — Cycle measurements and their accepting person.

Review task approval and roles.