First Setup

Installation got the plugin running and connected your CRM. This page walks the rest of the path: tags, a membership, a protected page, a login page, the automation that grants access, and a full test at the end.

Work through it once and you'll have the complete pattern every membership on your site will follow.

1. Create your tags

Under Membership → Tags, create the local tags your first membership needs. For a subscription-style membership that means two: an access tag (say, membership-foundations) and a cancel tag (membership-foundations-cancel).

Map each one to its matching tag in your CRM: click the remote tag field, pick the CRM tag from the list. If a tag doesn't exist in your CRM yet, check "create matching CRM tag" when you create the local one and both sides get made for you.

The full story on local tags, mapping, and local-only tags is in User Tags.

2. Create the membership

Under Memberships, add a new membership. Give it a name, set the access tag and the cancel tag you just created, and activate it.

Then set its Login Redirect URL: the page members land on right after logging in. You'll create that page in the next step, so come back and set it once it exists.

What makes a membership different from a bare tag? Settings like that redirect, plus a level, so higher memberships can inherit the access of lower ones. A tag is just a tag; the member has it or doesn't. Tags & Memberships covers the division of labor in full, including the PAYF and SUSP modifier tags you'll meet if you turn on Advanced Mode.

3. Protect a page

Create the membership's home page and publish it. Scroll to the content protection settings on the page editor and:

1. Enable Require Membership and check your membership. (You can protect by individual tags here too.)
2. Choose what happens without access. The default hides the page entirely, as if it were a 404. Redirecting to a "no access" page is friendlier when you want people to see a login prompt or an upsell instead of nothing.

Now revisit the membership and point its Login Redirect URL at this page. A member logs in, lands on their home page; anyone else never sees it.

4. Put up a login page

Create a page called Login and give it two shortcodes:

[memb_login_form]

That's the email and password form. Then below it:

[memb_request_magic_link]

Torii does not generate or store passwords the way the older Keap and ActiveCampaign editions did, so the magic link form is how a brand-new member gets in the first time: they enter their email, receive a one-time link, click it, and they're inside. Members who set a password later can use the form above; everyone else can keep using links forever.

The same shortcode on your post-purchase thank-you page lets people sign in immediately after checkout, before any email arrives.

5. Wire the welcome automation your CRM

In your CRM, create an automation triggered by the purchase, filtered to the product that grants this membership. Filtering by product is the safest trigger; add more filters if you need to be stricter.

Then the actions, in order:

1. Apply the access tag. This is what grants the membership.
2. Webhook: create the member. Add an HTTP POST action with the Create Member webhook URL from your Torii settings. The operations and CRM-specific wiring guides are in Webhooks.
3. Wait at least one minute. Gives the webhook time to finish before the email goes out.
4. Send the welcome email. Include the member's magic link so one click signs them in. The full recipe, including the sync field setup, is in Magic Links.

Two settings worth the trouble: make sure the automation can run again when a past customer repurchases, and add a step that removes the cancel and PAYF tags on re-purchase. Otherwise a lapsed member who comes back pays you and still can't get in, which generates exactly the support email you think it does.

6. Test the whole flow

Don't wait for a real customer to find the gaps.

1. In your CRM, create a test contact with an email inbox you can open.
2. Add the contact to your automation manually. (In production the purchase trigger does this; for testing, skip it.)
3. Confirm the access tag appears on the contact.
4. In WordPress, check Users: the account exists and carries the membership.
5. On your login page in a private browser window, request a magic link, open the email, click it.

You should land on the membership's home page, signed in. If that worked, every piece did its job: tag applied, webhook fired, member created, link generated, email delivered, access enforced.

Next: User Tags for the tag system, or Magic Links for everything about passwordless login.