Add comprehensive documentation for the Waitlist and Approval Gate system in the Milo platform#413
Merged
JoseSzycho merged 3 commits intomainfrom Jan 30, 2026
Conversation
…stem in the Milo platform.
3 tasks
JoseSzycho
requested review from
bmertens-datum,
drewr,
jacobsmith928,
mustela and
scotwells
Member
jacobsmith928
left a comment
jacobsmith928
left a comment
There was a problem hiding this comment.
This seems quite old @JoseSzycho - do we still need it?
Contributor
Author
|
I think it might be useful to keep the documentation. |
ecv
approved these changes
Jan 30, 2026
JoseSzycho
deleted the
feat/user-journeys-for-platform-waitlist-access
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a detailed README documenting the end-to-end user journeys for platform access using a waitlist and admin approval process and platform invitations. The document outlines the conceptual model, new/updated API resource types, controller behaviors, enforcement mechanisms, and the UI/application flow for both self-signup and invitation-based onboarding scenarios. This aims to clarify design intent and provide implementation guidance for related features.