HIGH story-multi-org-membership-handling-organization-administrator-004 3 pts

User Story

As a Organization Administrator
I want to designate or change which local association is a user's primary affiliation from the Membership Affiliation Screen
So that So that the system has an unambiguous default organization for attributing that user's activities when no explicit context override is provided, reducing the need for manual conflict resolution

Acceptance Criteria

  • Given a user with multiple organization memberships, when an Organization Administrator selects 'Set as Primary' for a specific affiliation, then that affiliation is marked as primary and all other affiliations for that user are marked as secondary
  • Given a primary affiliation is updated, when the Membership Service persists the change, then the update is reflected in the Membership Affiliation Screen without requiring a page reload
  • Given the primary affiliation has changed, when subsequent activities are registered by that user without an explicit context override, then the new primary affiliation is used as the default attribution organization
  • Given an Organization Administrator attempts to remove the primary designation without assigning it to another affiliation, when the action is submitted, then the system rejects it with a clear error message explaining that a primary affiliation is always required
  • Given a user has only one affiliation, when the Organization Administrator views the Membership Affiliation Screen, then that single affiliation is automatically shown as primary and the designation cannot be removed

Business Value

A clear primary affiliation designation eliminates ambiguity in activity attribution for multi-membership users, directly reducing the manual coordination effort Organization Administrators currently spend reconciling which organization should report which activity in Bufdir grant submissions.