> ## Documentation Index
> Fetch the complete documentation index at: https://orgo.space/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Adhesion (Membership Applications)
> Require a formal application and approval process before granting membership
Adhesion adds a formal application step to joining your organization. Instead of "register and you're in," members must submit an application that administrators review and approve, return for revision, or reject.
**When to use Adhesion:**
* You need to vet applicants (professional associations, selective clubs)
* You require documents or qualifications before granting membership
* You need a paper trail for who was accepted and why
* Regulatory requirements demand a formal application process
**When you don't need it:**
* Open communities where anyone can join
* Casual groups with no vetting requirements
* If you just need a simple approval gate, use [Status After Register → Unapproved](/platform/users/statuses) instead — it's lighter weight
***
## How to enable
**Settings** → **Users & Profiles** → **Adhesion** → toggle **Active**
| Setting | What it does |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active** | Turns on the adhesion module |
| **Mandatory** | When on, all new registrations must complete adhesion. Members can't access the platform until approved. When off, adhesion is available but optional. |
| **User type after approval** | Automatically assign a [User Type](/platform/users/user-types) when an application is approved. Example: auto-assign "Full Member" to approved applicants. |
| **Admin email** | Email that receives notifications for new submissions. Use a shared HR inbox. |
| **Change-to-draft reasons** | Predefined reasons admins can select when returning an application. Enter each on a new line (e.g., "Incomplete information", "Missing documents", "Photo not acceptable"). |
***
## The application workflow
```
New → Pending → Approved
↓
Draft (needs revision)
↓
Rejected
```
After registering (or as part of registration if mandatory), the member fills out the adhesion form — which can include profile fields, custom fields, document uploads, and declarations.
The admin email receives a notification. The application appears in the **Adhesions** admin queue.
Open the application to see all submitted information, uploaded documents, and history. Then choose an action:
* **Approve** — Member gains full access. User type is auto-assigned (if configured).
* **Return to Draft** — Select a reason (from your predefined list). The member is notified and can revise their application.
* **Reject** — Deny membership. The member is notified.
The member receives a notification with the reason. They update their application and resubmit. It goes back to Pending.
The member's status becomes Active (if it wasn't already). Their user type is set. They have full platform access.
***
## Building the adhesion form
**Settings** → **Users & Profiles** → **Adhesion Form**
The form can include:
* **Standard profile fields** — Name, address, phone, etc.
* **Custom fields** — Organization-specific data like license numbers or qualifications
* **Document uploads** — Profile photo, ID document, supporting documents
* **Declarations** — Terms acceptance, code of conduct, privacy policy consent
***
## Managing applications
Navigate to **Members** → **Adhesions** in the sidebar to see the queue.
### Finding applications
| Method | How |
| ------------------- | ---------------------------------------------------------------------------- |
| **By status** | Filter by Pending, Draft, Approved, or Rejected — Pending is your work queue |
| **By Local Center** | See applications for a specific branch |
| **By user type** | Filter by what membership type they applied for |
| **By date range** | Find applications from a specific period |
| **Search** | Search by name or email to find a specific application |
### Reviewing an application
When you open an application, you see:
| Section | What to check |
| ------------------------ | ------------------------------------------------------------------- |
| **Personal information** | Name, email, phone, address — verify completeness |
| **Custom fields** | Answers to your organization-specific questions |
| **Documents** | Uploaded ID (front/back), profile photo, supporting files |
| **Local Center** | Which center they selected (if applicable) |
| **Payment** | Fee payment status (if membership requires payment) |
| **History** | Every status change with timestamps and notes from previous reviews |
If [Identity Validation](/platform/identity-validation) is enabled, you can compare the profile photo to the ID photo, check document authenticity, and auto-extract data from scanned IDs.
### Taking action
**Approve** — Click Approve. The applicant becomes an active member and is notified. User type is auto-assigned (if configured).
**Return to Draft** — Select a reason from your predefined list. The member is notified and can revise their application. When they resubmit, it returns to Pending.
**Reject** — Deny membership with a reason. The member is notified.
**Bulk approve** — Select multiple applications → **Bulk Actions** → **Approve Selected**. Useful during enrollment periods with many straightforward applications.
***
## The adhesion template (PDF generation)
You can generate a PDF from approved applications — useful for official records, member files, or physical signatures.
The template editor provides a rich text editor where you can design the PDF layout. Use placeholders like `{{firstName}}`, `{{lastName}}`, `{{dateCreated}}` to dynamically insert member data. The template supports organization branding (logo, colors) and signature fields.
Configure the template at **Settings** → **Users & Profiles** → **Adhesion Template**.
***
## Interview tracking
For organizations that require interviews before final approval:
Enable interview tracking to add a step between application submission and approval. The workflow becomes:
1. Application submitted
2. Interview scheduled (admin sets date/time)
3. Interview completed (admin records notes)
4. Final approval or rejection
This is common for professional associations, leadership positions, and selective membership programs.
***
## Adhesion vs other joining methods
| Method | Process | Best for |
| ------------------------------------ | ------------------------------------------------------------------- | ----------------------------------------- |
| **Open registration** | Register → immediately Active | Communities, hobby groups |
| **Registration + Unapproved status** | Register → admin clicks Approve | Simple gate, no forms needed |
| **Adhesion** | Register → fill application → admin reviews → approve/reject/revise | Formal membership, documentation required |
| **Waitlist + Adhesion** | Join waitlist → invited → fill application → admin reviews | Limited capacity + formal membership |
***
## Combining with other features
| Feature | How it works with Adhesion |
| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| [Identity Validation](/platform/identity-validation) | Require ID documents as part of the application. OCR pre-fills form data from uploaded documents. |
| [User Types](/platform/users/user-types) | Auto-assign a type when application is approved. Different types can have different adhesion forms. |
| [Custom Fields](/platform/users/custom-fields) | Add organization-specific fields to the application form. |
| [Waitlist](/platform/users/waitlist) | Members wait in queue first, then go through adhesion when invited. |
| [User Statuses](/platform/users/statuses) | Approved applicants become Active. Pending applicants may have limited access. |
***
## Common scenarios
Use **Return to Draft** with a clear reason (e.g., "Missing proof of qualification"). The member is notified and can update their application. When they resubmit, it comes back to your queue as Pending.
Check if your admin email is being monitored. If you're the only reviewer, consider giving another admin HR Tenant permissions so they can help. Process applications in order — first come, first served is fairest.
They'll need to submit a new application. The old rejection stays in the system as a record. If there were specific issues, communicate what needs to change before reapplying.
Set Adhesion to Active but **not** Mandatory. Then use the registration form to route applicants: include the User Type field so members self-select, and only require adhesion for types that need vetting. Members who select types that don't require adhesion go through normal registration.
When adhesion is mandatory, members who haven't completed the process have limited platform access. Make sure your review process is fast enough that legitimate applicants aren't stuck waiting.
***
## Related
* [Registration Form](/platform/users/registration-form) — What members fill out before or alongside adhesion
* [Waitlist](/platform/users/waitlist) — Queue before adhesion for capacity-limited organizations
* [Identity Validation](/platform/identity-validation) — Document verification as part of the application
* [User Types](/platform/users/user-types) — Auto-assign on approval