Help Centre
Back to the portal

Feature reference

Membership

Accounts, applications, membership types, subscriptions and the member lifecycle.

What it does

  • Organization-scoped user accounts with profile and photo.
  • Membership applications carrying education history, work experience, referees, next of kin and custom identifiers.
  • Review workflow with notes, approval, rejection and return.
  • Membership number assignment: automatic, admin-assigned, or provided by the member from an existing record.
  • Membership subscriptions with coverage dates, grace periods and billing cycles. Renewal is reminder-driven: the member is told their cover is ending and pays. Nothing is charged automatically.
  • Birthday capture with member-controlled visibility, feeding celebrations.

The member lifecycle

register → verify email → complete application → submit → review → approve → pay → membership number → certificate → renew

Payment sits either before or after review depending on the organization’s configuration. Renewal returns to the payment step on the billing cycle, without repeating the review.

Two of the wizard’s steps are optional for the organization rather than the applicant. Phone verification runs first where the organization has SMS or WhatsApp configured, and is skippable by the applicant; payment is omitted entirely by organizations that collect nothing until after approval. Nothing downstream should assume a fixed number of steps.

Companies and institutions follow a parallel track: register → corporate profile → documents → projects → submit → review → approve → pay → membership number → seats. The member is the body, not the person who filed; representatives occupy seats against it, one seat per person per organization.

Membership structure

Each organization defines its own:

  • Membership types — categories with fee, currency and whether approval is required.
  • Chapters — geographic or branch divisions.
  • Subdivisions — internal groupings.
  • Specialties — professional areas.
  • Member identifier definitions — extra required fields such as licence numbers.
  • Membership number settings — the generation pattern.

Where it lives

Permissions

Permissions required

  • user:create,read,update,delete
  • application:create,read,update,delete
  • application_identifier:create,read,update,delete
  • education_history:create,read,update,delete
  • work_experience:create,read,update,delete
  • referee:create,read,update,delete
  • next_of_kin:create,read,update,delete
  • membership_type:create,read,update,delete
  • organization_chapter:create,read,update,delete
  • organization_subdivision:create,read,update,delete
  • organization_specialty:create,read,update,delete

Organization owners and staff accounts have these already. If a screen is missing for you, ask an owner to add the codenames above to your role.

Print the whole feature reference
Platform overviewPayments
Membership | Help Centre