Menú adicional

¡Consiga MemberPress hoy mismo! ¡Empieza a cobrar por los contenidos que creas! Obtenga MemberPress ahora
  1. Inicio
  2. Base de conocimientos
  3. MemberPress App
  4. App Access Control
  5. Migrating Require Purchase to Access Controls in MemberPress App

Migrating Require Purchase to Access Controls in MemberPress App

The Require Purchase setting restricts entire app access behind a single paywall. Access Controls provides granular, rule-based restrictions using membership plans and custom logic. This document explains how to migrate from Require Purchase to Access Controls using Access Groups and access rules.

Understanding the Migration Process

Require Purchase functionality applies a single access restriction to the entire app. Access Controls replaces this approach with flexible, condition-based restrictions. Migration involves documenting existing Require Purchase settings, enabling Access Controls, creating equivalent Access Groups, and configuring access rules that replicate previous functionality.

Documenting Current Require Purchase Settings

Require Purchase settings to be documented before migration begins. The toggle disappears after Access Controls activation.

  1. Vaya a Dashboard > MP App > Settings > In-App Purchases.
  2. Take note of your Require Purchase setting.
  3. Once Access Controls is enabled, this toggle will disappear, and its logic must be rebuilt manually using Access Groups.

Accurate documentation ensures equivalent access restrictions after migration completes.

Enabling Access Controls Component

Access Controls activation begins the migration process.

  1. Vaya a Dashboard > MP App > Components.
  2. Locate Controles de acceso in the components list.
  3. Compruebe el Activate Access Controls casilla de verificación.
  1. Haga clic en Guardar cambios.

A migration prompt may appear if Require Purchase was previously configured. Follow the migration link to continue the process.

Understanding Migration Impact

Access Controls activation removes the Require Purchase toggle from settings. Previous paywall logic must be recreated manually using Access Groups and rules. This change provides more flexibility but requires configuration effort.

Creating Equivalent Access Groups

Access Groups replicate the membership or product requirements from the Require Purchase settings.

  1. Vaya a Dashboard > MP App > Access Controls > Access Groups.
  1. Haga clic en Add Group.
  1. Enter a descriptive name in the Group Name campo.
  2. Seleccione Condition Type matching the previous requirements:
  • Membership Plan for membership-based restrictions;
  • User Role if role-based access was required.
  1. Select the specific membership plan or role from the secondary dropdown.
  2. Haga clic en Save Group.
  3. Repeat steps 2-6 for each membership plan or condition previously required.

Each Access Group represents one membership plan or condition from the original Require Purchase configuration.

Configuring General App Access Restrictions

General access restrictions replicate the app-wide paywall from Require Purchase settings.

  1. Vaya a Dashboard > MP App > Access Controls > General.
  2. Compruebe el Restrict Access checkbox to require login.
  1. En Access Groups, select all groups created in the previous section.
  1. Elija una Restricted Action for unauthorized users:
  • Return to Login;
  • Show App Page
  1. Haga clic en Guardar cambios.

These settings replicate the app-wide restrictions from the original Require Purchase configuration.

Selecting Appropriate Restricted Actions

The Restricted Action should match the original Require Purchase behavior.

Show Product Screen replicates paywall behavior by displaying membership options. This action matches the most common Require Purchase configuration, where users see available plans.

Return to Login redirects unauthenticated users to login screens. This action suits scenarios where a purchase happens outside the app, with login required after purchase completion.

Open App Page directs users to custom messaging or information. This action provides maximum flexibility for explaining access requirements or guiding users through purchase processes.

Enabling Private App Mode

Private App mode hides the app entirely from logged-out users, providing maximum access restriction.

  1. Vaya a Dashboard > MP App > Settings > General > Privacy.
  2. Compruebe el Private App casilla de verificación.
  1. Haga clic en Guardar cambios.

Private App mode complements Access Controls by preventing app discovery before authentication. This setting enhances security for member-only apps.

¿Le ha resultado útil este artículo?

Artículos relacionados

chica del ordenador

¡Consiga MemberPress hoy mismo!

Empieza a cobrar por los contenidos que creas.