An invitation is not proof that a member can participate
Read the guide →Guide preview
Track the member’s usable access separately from the invitation and account-creation stages.
Help people reach the right place and their next useful activity.
Help people reach the right place and their next useful activity.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Track the member’s usable access separately from the invitation and account-creation stages.
Welcome an existing member back to their community before introducing every feature of the new platform.
Identify the intended space and access condition before changing accounts or asking the member to pay again.
Confirm the account relationship through authorised procedures before deleting or merging anything.
Explain notification choices and a dependable way to find essential information; do not equate sending with reading.
Verify the next real event’s date, timezone, host and join route independently of the general migration.
Test the intended browser or app route on a real device; a desktop administrator view is not a mobile acceptance check.
A locked-out member needs a reachable help route that does not require access to the locked space.
Look for evidence that essential community tasks remain possible, not an artificial engagement target.