The safest way to launch a MemberClicks-connected WordPress website is in stages. Start with identity. Confirm synchronization. Add access rules. Then introduce the directory, portal, and write workflows appropriate to the organization.
This sequence reduces guesswork and makes each test meaningful.
Stage 1: Connect the Correct Organization
Under API Settings, enter the MC Professional organization ID, API client ID, and API client secret.
Run:
- Test API
- Profile Attribute Check
The first confirms that MemberClicks can issue an access token. The second checks whether the profile attributes required for authentication and synchronization are actually visible.
Confirm primary email, Profile ID, group, member type, and status as appropriate.
Stage 2: Configure SSO
Open SSO & Login.
Decide whether to:
- Show Continue with MemberClicks on
wp-login.php - Use the plugin-managed login page
- Show an optional direct credential form
- Set custom registration or password-help links
Register the public callback URL in MemberClicks exactly as shown by the plugin.
Test in a private browser window with a real member account.
Stage 3: Restore the Five Automatic Login Journeys
Open Automatic Login and configure the destination-specific links required by the organization.
Typical destinations include:
- Member dashboard
- Events
- Training
- Resources
- Profile
Copy the supplied code or URLs into the appropriate MemberClicks panel or website location as explained in the tab.
Test every journey while signed out.
Stage 4: Configure Member Login and Sync
Open Member Sync & Access → Member Login & Sync.
Choose:
- Whether WordPress users are created automatically
- Which supported fields are refreshed
- The WordPress role source
- Status enforcement
- Login and guest redirects
Then review Email Notifications and enable only the messages your staff and members need.
Stage 5: Discover Account Data and Map Roles
Business and Developer should open Member Data & Roles → Member Access & Roles and run account discovery.
Map real groups and member types to existing WordPress roles. Create new roles only when they represent a genuine access level.
Test at least:
- Active standard member
- Member in a special group
- Different member type
- Expired or inactive member
Stage 6: Protect Content
Use Restrict Content to protect selected WordPress pages.
Start with one test page:
- Restrict it to signed-in members or a mapped role.
- Open it as a guest.
- Open it as an allowed member.
- Open it as a member without the role.
Use the Access Library for organized role-aware links to courses, downloads, pages, or resources.
Stage 7: Launch the Directory
Business and Developer can configure the Member Directory.
Decide:
- Live API or synchronized index
- Grid, list, or compact layout
- Two or three columns
- Search shown or hidden
- Visible fields
- Detail pages
- Privacy and colors
Run the initial synchronization if using the WordPress index.
Stage 8: Build the Member Portal
Use the portal wizard to configure each page, template, and preview.
Prioritize:
- Dashboard
- My Profile
- My Events
- Education & Credits
- Directory
- Access Library
Publish pages only after testing the empty state and multiple member roles.
Stage 9: Tune Caching and Operations
Keep the one-hour defaults until traffic and freshness requirements are understood.
Then adjust groups, events, profiles, directories, education, and organizations as permitted by the license.
For synchronized directories, monitor cron and the last synchronization result. Developer should review retry and health information.
Stage 10: Enable Writes Last
Developer write features should be the final stage.
Before enabling them:
- Select editable fields explicitly
- Select registration fields separately
- Turn on approvals
- Run write-readiness diagnostics
- Use a test profile
- Verify the audit trail
- Test one LMS course completion
Recommended Screenshots
- API success and Profile Attribute Check
- Automatic Login panel
- Role mapping and Restrict Content
- Portal overview
Alt text: “Test the MemberClicks API and verify profile attribute visibility.”
Use admin-automatic-login.svg as an initial illustration. Alt text: “Configure five MemberClicks automatic login destinations.”
Alt text: “Map MemberClicks membership values and restrict WordPress content.”
Use pi-wp-suite-mc-pro-hero.svg and frontend-portal.svg as editorial illustrations. Alt text: “MC Professional connected to a complete WordPress member experience.”
Go-Live Checklist
- License edition verified
- API and attribute checks passed
- SSO callback tested
- Automatic login links tested
- WordPress account creation verified
- Roles and statuses verified
- Restricted content tested
- Directory privacy approved
- Portal pages reviewed
- Cache and cron monitored
- Writes tested separately where enabled
- Staff support instructions documented
The result is a staged, supportable member website: MC Professional remains the system of record, while WordPress delivers the member experience.
