MemberPass
Account & Security

Overview

Everything you can configure on your MemberPass account — sign-in methods, two-factor authentication, passkeys, recovery options, notifications, and more.

Your MemberPass account is the home for every project you run, every payment you collect, and every subscriber you serve. Because so much depends on it, we've built a rich set of tools to help you keep it safe, tidy, and tuned to how you like to work.

This section covers every setting you'll find under the Account and Settings menus — from creating your very first account through deleting it if you ever need to.

A quick map

Where to find account settings

Once you're signed in, open the account menu in the top-right of any page and choose Settings. You'll see a sidebar with all the sections above grouped for quick access:

  • Profile/settings/profile
  • Security/settings/security
  • Notifications/settings/notifications
  • Teams / Roles / Groups/settings/teams, /settings/roles, /settings/groups
  • Appearance/settings/appearance
  • Localization/settings/localization

Your account settings are separate from the settings of any individual project you create. Project-specific options — like plans, payment methods, or members — live on the project's own settings page. See Creating a Project for more on project configuration.

Security at a glance

We recommend every creator layer on at least two forms of protection:

  1. A strong, unique password (enforced — see Creating an account).
  2. One of: two-factor authentication, a passkey, or a linked social account you trust.
  3. At least one recovery email on file so you can always get back in.

Projects, members, and payouts are tied to your account. Losing access to it is disruptive for you and your subscribers — so treat account security as a business-critical task, not just a personal preference.

Teams vs. your personal account

If you're working with collaborators, you don't need to share your sign-in. Head to the Teams & Roles section to set up team members with scoped permissions instead.

On this page