Targeted member invitations
Create a separate invitation for a specific email address or phone number instead of relying on one reusable invitation link for everyone.
Membership and role management
Invite members, assign group roles, manage membership status, and keep the membership record connected to the same platform used for contributions, loans, meetings, voting, and reports.
Free plan available. No card required to start.
PamojaHub separates targeted invitations, membership roles, and membership status so joining a group and managing an existing member are not treated as the same action.
Create a separate invitation for a specific email address or phone number instead of relying on one reusable invitation link for everyone.
Keep the invitation lifecycle visible as pending, accepted, declined, revoked, or expired so group administrators can distinguish open invites from resolved ones.
Organize memberships around owner, admin, treasurer, and member roles, with ordinary role changes limited to admin, treasurer, or member.
Preserve membership history across active, suspended, left, and removed states rather than deleting the relationship whenever access changes.
Authorized group owners and admins can suspend or remove another member while members can leave a group through their own dedicated action.
PamojaHub protects the last active owner and does not allow ordinary role changes or invitations to grant ownership.
Targeted invitations
Each targeted invitation has its own token and lifecycle. The invitation is addressed to a specific email address or phone number, and acceptance checks the signed-in person's matching profile identity.
An owner or admin chooses an assignable role and provides an email address or phone number.
Email invitations are sent through the platform on a best-effort basis; the generated link is also available to copy and share directly.
The invitation context is preserved through login or account confirmation so the recipient can return to the intended invitation page.
The recipient can accept or decline a valid invitation addressed to their own profile identity, while the invitation status is retained.
Group membership uses defined roles and statuses rather than one unrestricted administrator flag. Management operations are routed through authorized database functions instead of ordinary direct membership writes.
Owners and admins can manage other members, including ordinary role changes, suspension, and removal.
The assignable roles for an invitation or ordinary role change are admin, treasurer, and member; owner is excluded.
Role change, suspension, and removal cannot target the caller's own membership.
Suspended, left, and removed membership rows remain available as history but no longer count as active group access.
Ownership is handled more carefully than ordinary role administration. The current product does not expose ownership transfer as a normal member-management action.
A database trigger prevents a membership change from leaving a group with zero active owners.
An invitation cannot assign the owner role, even if someone bypasses the client and calls the database function directly.
An ordinary role change cannot promote a member to owner; ownership transfer remains a separate future product decision.
Duplicate membership for the same user and group is prevented by a database-level uniqueness rule.
Common questions about invitations, roles, and membership status in PamojaHub.
Member management software gives a group one place to maintain memberships, roles, invitations, and membership status instead of keeping those administrative records across separate spreadsheets, chats, and informal lists.
Yes. A targeted invitation can be addressed to an email address or phone number. If an email address is provided, PamojaHub attempts to send the invitation email automatically. Phone-only invitations do not send SMS or WhatsApp; the generated invitation link can be shared manually.
The membership model supports owner, admin, treasurer, and member. Ownership is intentionally more restricted: invitations and ordinary role changes cannot assign the owner role.
No. The member-management operations for role change, suspension, and removal reject self-targeting. A member who wants to leave uses the dedicated leave-group action instead.
No. The database protects the last active owner so a group cannot be left without an active owner. A dedicated ownership-transfer flow is not currently implemented.
Start with PamojaHub's Free plan and manage membership alongside contributions, loans, meetings, voting, and reports.