Platform
Registrations
Application review, duplicate-safe submission, approval, and the transition to active membership.
Roles and permissions
Understand approval permissions and the default Member role.
Notifications
Understand registration review alerts.
How people join
A community can accept portal registrations or require a valid invitation link. The application collects name, email, password, sex, and a review note. Every public response is deliberately neutral so it does not reveal whether an account or pending application already exists.
Registration protection
Submissions are protected by per-address and per-network rate limits. When configured, a CAPTCHA challenge is verified before a request is accepted. Invitation links can expire, be revoked, carry a use limit, and are counted when a new application is created.
For administrators
- Review the applicant name, address, note, invitation context, and prior attempt information before deciding.
- Approve and Reject are separate permissions; a completed or superseded application is no longer actionable.
- Configured review alerts create persistent notifications for active Owners and Admins.
After approval
Approval creates or reuses the account, creates or reactivates the community membership, assigns the Member role, and creates the initial profile identity. Other pending applications for the same address are superseded. The application-held password hash is cleared after review.
After rejection
Rejection closes the application without creating membership access. The review action and optional reason are recorded in audit history, while the public submission flow continues to avoid revealing account state.
Duplicate and repeat submissions
A repeat submission does not create parallel active applications. PE Community records the attempt, keeps the canonical pending application, and queues a cooldown-controlled reminder or account guidance message. Concurrent submissions converge on the same application.
Approval is not permanent active status
Registration review and membership administration are different workflows. After approval, an authorized administrator may suspend an active membership and later reactivate that suspended membership. Only active members appear in the member directory, and directory access can also be hidden community-wide.