Positions and duty assignments

I’d build this around reusable positions and time-limited duty assignments. This is the proposed design; automatic position-based access is not implemented yet.

• Positions define the job.

  • Name, description, reporting relationship, and approved roles.
  • Define whether access requires an event, specific shelters, or another supported scope.
  • Reporting to another position does not automatically inherit its permissions.

• Assignments put people into positions.

  • Select the person, position, event, and assigned locations.
  • Set a start and end time, or explicitly approve an ongoing assignment.
  • People may hold multiple assignments.
  • A person without a linked user account can be recorded for staffing, but receives no system access.

• Access combines both sources.

  • Direct account roles remain available.
  • Active position assignments add their scoped permissions.
  • Ending one assignment removes only access supplied by that assignment.
  • Suspended accounts and security holds still block access.

• Access stays within the assignment.

  • Managing Alta Vista does not grant management of every shelter.
  • Only roles that support the required scope can be attached.
  • Swamp Dice administration remains an explicit, separately assigned role.

• Administrators review before granting access.

  • Show exactly what will be added, where it applies, and when it ends.
  • Position-role changes show affected assignments before confirmation.
  • Scheduled assignments activate at their start time; expired assignments stop granting access immediately.

• Every change remains traceable.

  • Record who assigned, extended, changed, or ended the duty.
  • Keep completed assignments in history.
  • A person’s access screen explains why they have each role.

The preview shows Position setup → Assign duty → Person’s access. Try assigning someone, then ending their duty to see their regular account role remain.