Skip to main content
Membership.io is easiest to understand as a set of connected building blocks.

​
Team

A team is the creator-side tenant. Users log in to manage a team. Team-scoped API routes usually look like: 
/api/v1/teams/{team_id}/...
Use team-scoped routes to manage contacts, hubs, products, media, access rules, tags, segments, and API keys.

​
Hub

A hub is a branded member destination. A creator can run multiple hubs from one team, such as:
  • A paid coaching community.
  • A free lead magnet hub.
  • A course library.
  • A premium members-only portal.
Hubs scope member-facing content, pages, community, policies, checkout display, and memberships.

​
Contact

A contact is a person in the creator’s world. Leads, customers, members, and alumni are all contacts. This keeps a single person tied together across purchases, content progress, email activity, and community activity.

​
Team contact

A team contact is the CRM record for a contact inside one team. The same email can exist globally as one contact while still having team-specific fields, tags, attributes, and lifecycle data.

​
Hub membership

A hub membership says a contact belongs to a hub and tracks member-specific state such as onboarding, terms acceptance, notification preferences, ban status, and role.

​
Content, pages, and media

Content is the structured learning or library tree. Pages are the hub-rendered surfaces such as homepages, sales pages, and structured sections. Media stores the files that pages, content, community posts, and playlists reference.

​
Products, checkout, and access

Products describe what is for sale. Prices describe how it is sold. Checkout creates orders, payments, and subscriptions. When checkout succeeds, deliverables grant access to hubs or content. Access rules are the enforcement layer. They answer the practical question: “Can this member see this thing right now?”

​
Community and email

Community gives each hub spaces, discussions, comments, reactions, messages, moderation, profiles, and member directories. Email handles transactional messages, templates, drip campaigns, suppression, unsubscribe, and per-hub sending configuration.