Proposal: Member admittance [S13-03]

Member admittance is the process of a non-member request and and entering the common

**User Flow: Request side**

1. User enter a certain common via
1. Explore page
2. Direct link to common agenda
2. In screen: Common Agenda - User clicks on “Join Common” button
3. Common Disclaimer (”Please understand what is this common goals and means”) with stats and links to the common white-paper, member list, funds request, default circle on admittance. At the bottom of the page there will be a continue button “I’m good with it all, let’s move forward”
4. User is requested to fill in request form including
1. Intro: Why do I want to join the common (in the request presented to the common member there will be a representation of the user profile and commons he/she is members)
2. Links to FB, Twitter, Personal Website
5. If common request funds and If user has no credit card in the system there will be a request to fill in credit card details.
6. Payment review screens showing the credit card used and the following payment to be done (single, monthly)
7. Thank you please wait message.
1. Under the user’s activity page the common will be shown under pending approval
8. A “member admittance” proposal is generated

1. A proposal is generated upon completion of the request and user is added to the list of pending users of the common
2. A push notification and email with a link to the proposal page is sent to
1. All valid member (with voting rights)
2. The user who requested (different email)
3. Member with the rights to approve this proposal could click on the request card and see all user details (intro, links, proposals, etc.)
4. The voting panel will be shown under the proposal (approve, abstain, reject, countdown etc.)
5. Approval vote
6. Option: When quorum is reached an acceleration mode begins
7. If user approved it moves to members tab, if rejected it moves to rejected members

The issue describes an end-to-end member-admittance flow but names no files, tests, or entry points. Start by mapping the existing common agenda, request, proposal, notification, payment, and member views, then confirm the intended approval and rejection states. Done means the complete request-to-admittance flow is implemented and verifiable.

Written by the indexing model from the issue text.