WordPress LMS and Membership MCP that treats access as the risk it is.

How the four plugins differ when a write goes wrong

These modules share a risk, not a data model. Each plugin stores access its own way, so the same mistake has a different cost and a different way back depending on where you made it.

• Tutor LMS keeps a course as a tree of posts, so new courses, topics, lessons and quizzes, and deletes that only trash, can be undone from the change ledger. Quiz questions sit in their own tables and cannot, and neither can reorders, added instructors or permanent deletes. A permanent course delete takes quiz attempts and enrolments with it.
• Paid Memberships Pro keeps levels, memberships and discount codes in its own tables. Every write is logged without a before-image, so none of it rolls back from the ledger; the ability returns the previous values for a person to write back.
• The Events Calendar mirrors each event post into its own date tables. A new event can be undone by trashing it, but edits and deletions count as irreversible, because restoring the post alone may not resync those tables.
• BuddyPress keeps groups in its own tables with no trash. Group writes are logged without an undo, and deleting a group removes its memberships, invitations and metadata for good.

Where to let an agent draft and where to make it ask

That difference ranks the work. Course authoring is the safest place to let an agent draft freely, since drafts stay invisible to learners and most of it can be undone. Event edits deserve a review of the date, timezone and venue before they are confirmed. Membership levels, enrolments and group privacy deserve a person approving each change, because the ledger cannot take them back and the people affected notice before you do. A confirm flag alone does not give you that, since the agent sets it; turn on Pro's approval queue or the "A person approves" confirmation mode for these writes.

Where these plugins meet WooCommerce and each other

A membership or course site is rarely one plugin. The places they connect are where an agent's change can land in the wrong system:

• A Tutor course sold through WooCommerce links an existing product no other course uses. The course abilities attach it; creating or repricing that product is WooCommerce work for the commerce modules.
• A Tutor course priced through Easy Digital Downloads or a membership plugin is refused for paid setup. Set the price in that plugin and let the agent handle the curriculum.
• Granting a Paid Memberships Pro level is an administrative change with no checkout, order or gateway subscription behind it. A paid level granted that way has not been paid for, and nobody will be billed.
• Changing a level's price affects future checkouts only. Existing members stay on their old terms at the gateway; the update reports how many are affected, which is the number to read before approving it.
• Event tickets belong to the separate Event Tickets plugin and are read-only here: inventory and RSVPs, never attendee names, emails or orders.

What each plugin keeps out of the agent's answers

Access work touches personal data, so each module has a fixed list of fields it never returns. Knowing that list helps you write prompts that do not ask for the impossible, and explain to a client exactly what an AI client on their site can see.

• Paid Memberships Pro order reads carry totals, level, gateway and status, never card details, billing addresses, transaction ids or order notes.
• Tutor LMS enrolment reads confirm a record exists without the learner's email, profile or quiz attempts. Quiz attempts have a read of their own; leave it off any token that does not need it.
• BuddyPress member reads leave out email addresses, private messages, extended profile values, authentication data, notification settings and private activity.
• Event ticket reads never include attendee details.

Outside these modules, and what to use instead

Some operations work stays in the plugins' own screens. Plan for these before promising a client an agent can run the whole site:

• Recurring series from Events Calendar Pro. An edit is never series-wide, and an event that belongs to a series is flagged before any change.
• Ticket creation, capacity, check-ins and ticket refunds.
• BuddyPress messages, activity, friendships, extended profiles, invitations, bans and member roles.
• Matching, ordering, image and Tutor Pro interactive quiz questions, which can be read but are edited in Tutor's quiz builder.
• Refunds of any kind. Cancelling a level or removing an enrolment never returns money; that is done where the payment was taken.

Building one of these sites first

If the membership or course site is still being planned, the membership and booking site guide covers the build. This page is about running one once members, learners and attendees depend on it.