Skip to main content

Documentation Index

Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Overview

The Client Portal is the primary management interface for association staff to administer all aspects of their membership organization.

Role & Responsibilities

Client Portal users manage day-to-day operations:
  • Membership Management: Create, edit, and manage member accounts and plans
  • Event Management: Create events, manage tickets, track attendance
  • Course Administration: Build courses, manage enrollments, issue certifications
  • Content Management: Resources, help center articles, job postings
  • Financial Operations: Revenue tracking, invoicing, payment configuration
  • Reporting & Analytics: Generate reports across all modules

Access Control

RoleAccess Level
ROLE_CLIENT_ADMINFull access - all features
ROLE_CLIENT_USERLimited access - view and basic operations
ROLE_PLATFORM_ADMINSupport access - can assist with issues

Feature Groups

Memberships

Member accounts, plans, revenue, CPD, groups, notifications, invoicing

Events

Event creation, tickets, attendance tracking, reporting

Resources

Resource library management and analytics

Support

Help center, ticket management, support metrics

LMS

Courses, certifications, CPD points, AI tools

Directory

Business directory, company profiles, leads

Sponsorships

Sponsor tiers, assignments, support, widgets

Careers

Job board management and reporting

Data & Exports

Data exports and bulk operations

Widgets

Embeddable widgets for external websites

Integrations

Configure Stripe, Xero, Salesforce, HubSpot, WordPress

Technology

The Client Portal is built with:
  • React + TypeScript - Modern frontend framework
  • TanStack Table - Data grid for member lists, reports
  • TanStack Query - Server state management
  • shadcn/ui + Radix UI - Accessible component library
  • React Hook Form + Zod - Form handling and validation

Acceptance Criteria

Frontend

  • UI supports the workflows described on this page.

Backend / API

  • Backend behavior supports these workflows (data fetch, mutations, exports).

Permissions

  • Access is restricted per the Capabilities matrix (or role rules) for this area.

Business Rules

  • All business rules described on this page are enforced.

Error Handling

  • User-visible errors are clear and recoverable where possible.