Operate the whole membership network from one platform

Every page, program, and policy has a national version owned by HQ and a chapter version owned by the chapter. Chapters inherit the national version by default. You decide which fields a chapter can override (local hours, contact details, event listings, local sponsor logos) and which stay locked (logo, brand colours, member benefits language, legal copy). Changes at HQ flow down automatically. Changes at the chapter stay scoped to that chapter.

Yes. Chapters get their own sub-section, their own admin permissions, and their own catalog scope for local programs and events. They can swap hero images, local sponsor logos, event listings, and local content. They cannot change locked brand elements, national policy pages, or member benefits language. Approval gates can require HQ sign-off for changes outside the configured permitted scope.

A member has one record on the platform, tied to a primary chapter and any additional chapter affiliations. The public site, the member portal, the LMS, and event registration all read from this one record. A member who moves from a state chapter to a national role keeps the same record, the same CPD history, and the same dues record. You do not run separate identity systems per chapter.

Both options work. Some networks fully replace iMIS, Personify, or NetForum with Core dna's custom-entity model for members, chapters, dues, and certifications. Others keep their AMS in place during a phased migration and bridge it to Core dna while the public site, member portal, and LMS move first. Discovery confirms which path fits your data, your renewal cycle, and your team. Most networks fully consolidate within 18 to 24 months.

Yes. The member portal handles annual dues, monthly dues, multi-year dues, tier upgrades, one-time event registrations, donations, and merchandise on one checkout. Dues renewal runs as a subscription with the renewal date, grace period, and lapsed-dues recovery configured per tier. Lapsed members lose gated-content access on the date you specify. Renewal emails are triggered by the platform, not by a separate email tool.

Yes. CPD progress, certification status, and continuing-education credits are tracked as part of the member record. A member completing a course in the LMS updates their record on the platform without an external integration. Certification renewal can require completed CPD as a condition, and dues renewal can require active certification. The full chain works inside one data model.

Content can be public, member-only, or scoped to a specific member tier, chapter, certification, or program. Access rules read from the member record at request time. A member who downgrades a tier loses access at the moment the downgrade saves. A member whose dues lapse loses access on the date you configure. Search and SEO crawlers see what you let them see.

Yes. Events are first-class entities with their own session catalog, ticket types, registration workflow, and tier-specific pricing. A member at a higher tier sees a different price than a non-member. Registration writes to the member record so CPD credits and conference history sit alongside dues and program history. Multi-day conferences with sub-sessions, workshops, and ticketed extras are supported.

Most national bodies go live in 12 to 20 weeks. Federations with 30 to 100 chapters and deep AMS integration run 20 to 28 weeks. Discovery (3 to 4 weeks) maps your member data, your chapter governance, and your integrations. Configuration and integration (8 to 14 weeks) build the custom entities, migrate the AMS data, and wire the payment processor. UAT runs with HQ and one chapter pilot. Deployment includes a real renewal cycle in production before full rollout.

Those tools are association management systems. Strong on CRM, dues, and event registration. Weak on modern public web, weak on chapter governance at scale, and almost always paired with a separate CMS (WordPress, Drupal) plus a separate LMS plus a separate event tool. With that stack, member identity lives in seven places. With Core dna, members, chapters, programs, and dues are modelled on one platform. If you are under 1,000 members with no chapter structure, an AMS-plus-WordPress stack is often enough. For chapter-based networks at scale, the stitching cost compounds.

Agentic = describe the change in plain language; the platform ships it across every property, with approval and audit built in. For a national membership body, that means a Director of Communications says "update the professional-tier renewal copy on every chapter site and refresh the linked CPD compliance language" and the platform drafts the change, previews it per chapter, and stages it for approval. Two humans approve. A diff per chapter is shown before ship. Rollback is armed.

The platform does not change brand voice, tier rules, dues amounts, or member benefits language without an explicit instruction and an explicit approval. Agentic is a layer on top of the same governance you already run — chapter scope, role permissions, approval gates, audit log — not a replacement for it. It is also opt-in per workflow. Networks that prefer to keep agentic dormant on Day 1 and turn it on per workflow after the first renewal cycle are common.