Approving join requests
People waiting on you to let them into a project. Which joins appear here depends on the role they asked for and on the project's auto-approve setting.
📷 Screenshot placeholder — Join requests: the four stat cards and a pending affiliate request.
What lands here
Join requests is one inbox for all of your projects. A join is gated — lodged here instead of becoming a membership at once — in two cases:
- Affiliate and influencer joins always land here, whichever link they came through. Someone earning from a downline is a decision, not a default.
- Farmer joins land here only when that project's Auto-approve farmers switch is off. That covers joins through your official link, through a member's personal link, and code-less joins on a project open to anyone.
With auto-approve on, farmers who follow a link start farming immediately and never appear here.
The person who asked sees "Your request to join … is pending" on the invite landing until you decide. Submitting again while a request is pending changes nothing.
Where auto-approve is set
Auto-approve is a setting on the project, on its detail page — not on the link and not here. Next to it, Who can join decides whether a code is required at all. Neither setting changes what happens to affiliate and influencer joins.
Reading the inbox
The stat cards show how many requests are pending, approved and rejected across the whole inbox, and your median decision time over the last thirty days.
The table lists each request with the requester's wallet or name, the project, the requested role, who invited them — a member's name, or Official invite for your own link — and when it arrived. Pending requests are listed oldest first so you work front to back; decided ones newest first.
Filter by requester (wallet or email), project, state tab and role.
📷 Screenshot placeholder — the Approve confirmation, "Admit … as Affiliate on …".
Approving
Approve asks you to confirm — Admit this person as this role on this project? — and then creates the membership. The person is admitted exactly as their request was lodged: the role the link granted and their place in the referral tree under whoever invited them. If they came through your official link they start at the root, with no one above them.
An approval into an affiliate or influencer role is recorded in the member's activity history. A request on a project whose organisation is suspended cannot be approved until the suspension is lifted.
Rejecting
Reject asks for a reason, which is required. No membership is created; the request moves to the Rejected tab with your reason shown on the row, for your reference. The requester is not shown the reason.
Rejecting does not bar the person from the project. If they use a link again, a new request appears here.
What a decision does not do
- It does not change the role on the link. A link minted for influencer keeps inviting influencers.
- It does not affect members already in the project. Promotions and demotions are made from the Recruitment roster.
- It does not pay anyone. An invite reward, where you offer one, waits for the invitee to qualify after they are a member.