How to keep invite accessible at scale?

[MarliesRikken]

New Feature Request

Summary

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
How to keep overview of roles and users at high usage numbers? Currently overview might become limited.
Consider each perspective -> user, inviter, role manager, institution admin.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
To ensure long term usability of Invite.

Proposed Solution

• Action: Describe the logic or flow change.
• Design: [Link to Figma/Screenshots]
• Impact: Does this affect existing APIs or UI components?

Developer Checklist

To be completed by the developer during implementation.

• Add required changes and feature flags config files
• Create and document database changes and migrations
• Create and document API changes and migrations
• check for backwards compatibility
• Updated CHANGELOG and other documentation where needed

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup

1. Point to [URL/Branch]
2. Use account with [Role/Permissions]

Test Checklist

• Happy Path: Feature works as intended under normal conditions.
• Edge Case: [Describe specific test item]
• Validation: [Describe specific test item]
• UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.