“Sessionboard has been one of our most successful investments this year, making our team more efficient and allowing us to focus on the most critical components of our events.”
re:Members is your association management system — membership, dues, and chapters stay there.
re:Members holds the member record, dues, and chapters. Sessionboard is the program layer: call for papers with membership validation, multi-round review, speaker portal, transcription, Attendee Hub, and Advocacy — with SSO and member sync from re:Members; we never create authoritative member records.
Match your role to the job Sessionboard solves — program, content, or marketing attribution.
Program teams want CFP gated on member status — you need validation from re:Members, not duplicate contact records.
Reviewers log in with association identity — SSO from re:Members should gate committee access.
Speaker bios re-keyed from AMS exports — faculty CRM should sync member attributes from re:Members.
Session content trapped in event silos — capture should flow to your LMS from Sessionboard Marketing.
Keep re:Members mid-contract when you need to — Sessionboard owns call for papers, speaker operations, and content marketing on the program graph.
Membership, dues, chapters, and contact master data in re:Members.
re:Members portal authentication.
Basic event registration where contracted on the AMS stack — not deep CFP or speaker ops.
Membership from re:Members validates submission eligibility.
Multi-round review, chair workflows, speaker portal, and agenda on the program graph.
Transcription, Media Library, Attendee Hub, Create, Advocacy, and Dispatch on session records.
Session and webinar artifacts export to Path, TopClass, CloudCME, and other learning platforms — see LMS works-with pages.
Program and session data live in Sessionboard — with optional sync to and from re:Members.
API and import paths: Microsoft Power Platform API (formerly Impexium) — registration and member sync paths.
Sessionboard connects to the assistants your team already uses through MCP (Model Context Protocol). Sessions, speakers, and agenda data stay in Sessionboard — Claude, ChatGPT, and Copilot read it live.
Sign in with OAuth — no API keys to copy. Ask about session status, speaker readiness, committee progress, or agenda gaps in plain English.
Registration and capture tools stay in place. Sessionboard holds the program graph — sync transcripts and media back when you run another vendor beside us.
See how Sessionboard fits beside your existing stack — no rip-and-replace required.
Sessionboard already includes transcription, attendee experiences, and content marketing. A separate subscription makes sense only in narrow cases.
How Sessionboard works beside re:Members.
No. re:Members stays the membership system of record. Sessionboard owns call for papers, abstract review, speaker operations, and content marketing beside your AMS.
re:Members portal authentication. Sessionboard validates submitters and reviewers against membership — ask your rep for current SSO scope.
Yes — member identity and eligibility flow from re:Members for CFP and speaker portal. Sessionboard does not create authoritative member records; the AMS stays source of truth.
Yes — Sessionboard Content Marketing packages transcripts, clips, and Attendee Hub objects for Path, TopClass, CloudCME, and other LMS platforms. See works-with LMS pages.
Registration can stay on Cvent, RainFocus, or EventsAir. Sessionboard connects membership from re:Members to program operations — registration sync is separate.
Sessionboard supports SSO, member validation, and sync paths for re:Members. Ask your rep for connector scope on your org — deployment varies by AMS edition.
Talk through your event workflow — abstracts, speakers, content, and marketing on one program graph.
Running re:Members for membership?
Request a demo