medium complexity extracted Organization Management Confidence: 100%
5
Components
32
Shared
0
User Stories
Yes
Analyzed

Description

Member Associations manages the relationship between peer mentors and their local chapters (lokallag) within an organization. A peer mentor may belong to one or more local associations, each of which falls under a regional or national organization. This feature provides the admin interface for creating, editing, and assigning local associations, as well as managing which users are members of each association. It also handles edge cases such as a peer mentor who is active in multiple local chapters, ensuring activities are attributed to the correct association for reporting purposes.

User Flow

Member Associations user flow
Click to expand

Analysis

Business Value

Local associations are the operational unit of the Norwegian voluntary sector. Without clear association membership, activity data cannot be correctly attributed for Bufdir reporting, coordinator oversight is impossible, and duplicate reporting cannot be detected. NHF specifically flagged that a peer mentor can belong to up to five local chapters - a scenario that breaks naive single-membership models. Solving this correctly is a prerequisite for accurate statistics and compliant government reporting. From a sales perspective, demonstrating that Meander handles real-world membership complexity out of the box is a strong differentiator against generic CRM tools that organizations currently cobble together.

Implementation Notes

The `local_associations` table links to `organizations` (via region) and `user_roles` (via membership junction). The Local Association Service provides CRUD endpoints and membership management APIs. The Association Management Page in the admin portal allows admins to create local associations, assign them to regions, and manage member lists. The UI supports bulk assignment of users to associations. When a user belongs to multiple associations, activity registration in the mobile app prompts the user to select which association context applies (or defaults to primary). Duplicate reporting detection is implemented as a background validation job that flags activities from the same user/date/type across multiple associations.

Components (37)

User Interface (2)

Service Layer (2)

Data Layer (1)

Shared Components

These components are reused across multiple features

User Stories

No user stories have been generated for this feature yet.