Our goal is to ensure this plugin is easy to work with for customizations. If a hook doesn’t exist where you think it should, please submit a ticket so we can consider its addition.

This reference lists helpful filters, actions, and methods and is meant to be a directory. This document may not outline every available or hook or method, so please see the plugin’s inline documentation for additional details on parameters, returned values, and usage, or example usage.

If you need help changing this code or extending it, we recommend getting in touch with a WooExpert or a developer at Codeable.

Data Structure

Teams for WC Memberships leverages a few custom data structures, but you would also benefit from being familiar with the data structure of WooCommerce Memberships itself. The Memberships Data Structure overview and developer documentation will be helpful resources.

We also recommend reviewing the methods in the WC_Memberships_User_Membership class, as these methods are quite commonly used by developers to manipulate user memberships. User memberships can easily be instantiated with the wc_memberships_get_user_membership() global method.

For its own functionality, Teams adds a “team” and “invitation” custom post type to manage groups of members, and invitations to join a team. Teams also makes modifications to particular products and membership plans to store additional data related to purchasing a team, and managing team access.

Teams

Post type: wc_memberships_team

The team post serves as a data store for all team information, such as purchase record, owner, and members (along with the roles of each member on the team).

The team owner is stored as the post_author, given a team can only have one owner, and the configured team name is stored as the post_title. The team’s post_parent is the post ID of the Membership Plan to which the team grants access (as currently a team can only provide access to a single plan).

Team posts store other data about the team as well:

Team Invitation

Post type: wc_team_invitation

Invitation posts store data about invitations sent to particular emails. The invitation post will use custom statuses to determine the invitation status: wcmti-pending, wcmti-accepted, or wcmti-cancelled. The post_author is the user who sent the invitation, while the post_parent is the team to which the invitation belongs.

Pending invitations will store no meta, but accepted invitations will add 2 pieces of meta data:

Product Data

To associate a team with a product or variation, the product post will store a few pieces of data:

User capabilities

Teams provides a few custom WP User capabilities for both admin management of teams, and frontend management for team owners and managers.

Team Lifecycle

You can hook into the team lifecycle at several instances to fire third party code or adjust teams.

Created Team Filters

When a new team is created, the team data can be filtered.

wc_memberships_for_teams_new_team_data

@since

 

1.0.0

 

@param

 

array $data team data

 

@param

 

array $args an array of team arguments {

• • @type string $name the team name
  • @type int $plan_id the plan id the team has access to
  • @type int $owner_id the user id the team is assigned to
  • @type int $product_id the product id that creates the team (optional)
  • @type int $order_id the order id that contains the product that creates the team (optional)

}

Created Team Actions

Team creation and management also fires several actions that can be used to run additional code.

wc_memberships_for_teams_team_created

Fires after a team has been created. This action hook is similar to wc_memberships_for_teams_team_saved but doesn’t fire when teams are manually created from admin.

@since

 

1.0.0

 

@param

 

Team $team the team that was just created

 

@param

 

bool $updating whether this is a post update or a newly created team

wc_memberships_for_teams_team_saved

Fires after a team has been created. This action hook is similar to wc_memberships_for_teams_team_created but will also fire when a team is manually created in admin, or upon an import or via command line interface, etc.

@since

 

1.0.0

 

@param

 

Team $team the team that was just saved

 

@param

 

bool $updating whether this is a post update or a newly created team

wc_memberships_for_teams_process_team_meta

Fires when a team is saved/updated from admin.

@since

 

1.0.0

 

@param

 

int $post_id post identifier

 

@param

 

WP_Post $post the post object

Invitation Lifecycle

You can hook into the team lifecycle at several instances to fire third party code or adjust invitations.

Created Invitation Filters

When a new invitation is created, the invitation data can be filtered.

wc_memberships_for_teams_new_invitation_post_data

@since

 

1.0.0

 

@param

 

array $data new invitation post data

 

@param

 

array $args array of Invitation arguments {

• • @type string $email email of the invitation recipient
  • @type int $team_id the team id
  • @type int $sender_id the sender user id
  • @type string $role the role to assign the invited user to

}

wc_memberships_for_teams_join_team_redirect_to

Filters the URL to redirect to when a user joins a team by invitation or via link

@since

 

1.0.4

 

@param

 

string $redirect_to URL to redirect to

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team the team object

 

@param

 

false|SkyVergeWooCommerceMembershipsTeamsInvitation $invitation the invitation object

Created Invitation Actions

Invitation creation will also fire an action that can be used to run additional code.

wc_memberships_for_teams_invitation_created

Fires after an invitation has been created.

@since

 

1.0.0

 

@param

 

SkyVergeWooCommerceMembershipsTeamsInvitation $invitation the invitation that was just created

Frontend Hooks

This is a non-exhaustive list; these represent some often-used frontend hooks.

Frontend Filters

wc_memberships_for_teams_product_team_user_input_fields

Filters user input fields for a team product.

@since

 

1.0.0

 

@param

 

array $fields associative array of user input fields

 

@param

 

WC_Product $product the product

wc_memberships_for_teams_add_team_member_form_fields

Filters form fields for the add team member form on frontend.

@since

 

1.0.0

 

@param

 

array $fields associative array of form fields

wc_memberships_team_teams_area_sections

Filters the available sections for the teams area.

@since

 

1.0.0

 

@param

 

array $sections associative array with teams area id and label of each section

wc_memberships_for_teams_teams_area_{$section_id}_title

Filters the teams area section name title. Core section IDs include “members”, “add-member”, and “settings”.

@since

 

1.0.0

 

@param

 

string $section_name the section name (e.g. “Members”, “Add Member”, “Settings”…)

 

@param

 

Team $team the current team displayed

wc_memberships_for_teams_teams_area_my_team_details

Filters the teams area team details.

@since

 

1.0.0

 

@param

 

array $details associative array of settings labels and HTML content for each row

 

@param

 

Team $team the team the details are for

Frontend Actions

wc_memberships_for_teams_before_renewal_auto_login

Fires right before logging a team member in. Can throw SV_WC_Plugin_Exception to halt the login completely.

@since

 

1.0.0

 

@param

 

int $log_in_user_id the user ID of the member to log in

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team team instance

 

@param

 

bool $allow_login whether automatic log in is allowed

Admin Hooks

This is a non-exhaustive list; these represent some often-used admin hooks.

Admin Filters

wc_memberships_for_teams_team_member_roles

Filters the list of available team member roles. Note that this does not include owner by design.

@since

 

1.0.0

 

@param

 

array $roles an associative array of role => label pairs

wc_memberships_for_teams_settings

Filters Memberships for Teams settings.

@since

 

1.0.0

 

@param

 

array $settings array of teams settings

wc_memberships_for_teams_invitation_statuses

Filters invitation statuses.

@since

 

1.0.0

 

@param

 

array $statuses associative array of statuses and their arguments

wc_memberships_for_teams_skip_invitations

Filters sending an invitation when adding members to a team

@since

 

1.1.2

 

@param

 

bool $skip_invitations whether invitations should be skipped

 

@param

 

null|SkyVergeWooCommerceMembershipsTeamsTeam optional argument to evaluate if invitations should be skipped for a particular team

 

@param

 

null|int|string|WP_User optional entity being invited to join a team (either email, ID or object)

wc_memberships_for_teams_team_membership_can_be_renewed

Filters whether a team membership can be renewed

@since

 

1.0.0

 

@param

 

bool $can_be_renewed whether can be renewed by a user

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team the team to renew membership for

wc_memberships_for_teams_team_management_status

Filters team management status

@since

 

1.0.0

 

@param

 

array an associative array with two keys: “can_be_managed” and “messages”

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team the related team

wc_memberships_for_teams_team_can_add_seats

Filters whether a team can have seats added

@since

 

1.1.0

 

@param

 

bool $can_add_seats whether seats can be added

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $this the Team object

wc_memberships_for_teams_team_can_remove_seats

Filters whether a team can have seats removed

@since

 

1.1.0

 

@param

 

bool $can_remove_seats whether seats can be removed

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $this the Team object

wc_memberships_for_teams_allow_editing_user_membership

Filters the editing of a user membership

@since

 

1.1.2

 

@param

 

bool $allow_edit default true for non-subscription linked memberships

 

@param

 

WC_Memberships_User_Membership|WC_Memberships_Integration_Subscriptions_User_Membership $user_membership membership object

wc_memberships_for_teams_should_perform_seat_change

Filters whether a seat change should be performed

@since

 

1.1.0

 

@param

 

bool $should_perform_seat_change

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $this the Team object

 

@param

 

int $new_seat_count the desired seat count

wc_memberships_for_teams_should_prorate_seat_change

Filters whether a seat change should be prorated

@since

 

1.1.0

 

@param

 

bool $should_prorate_seat_change default false

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $this the Team object

 

@param

 

int $new_seat_count the desired seat count

wc_memberships_for_teams_seat_change_notice_message

Filters the notice message that is shown after a successful seat change

@since

 

1.1.0

 

@param

 

string $seat_change_message the notice message

 

@param

 

WC_Order $order the order object

 

@param

 

WC_Order_Item $item the order item object that contains the seat change data

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $this the Team object

Admin Actions

wc_memberships_for_teams_before_team_billing_details

Fires before the billing details in edit team screen.

@since

 

1.0.0

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team the team instance

wc_memberships_for_teams_after_team_billing_details

Fires before the billing details in edit team screen.

@since

 

1.0.0

 

@param

 

SkyVergeWooCommerceMembershipsTeamsTeam $team the team instance

Methods and Global Functions

This is a non-exhaustive list; these represent some often-used plugin methods.

Plugin main class

The instance of the main plugin class can be accessed with: wc_memberships_for_teams()

Any other plugin classes are instantiated in this main plugin class, or another class that’s instantiated by the main plugin class. Therefore, if you want to unhook methods in a particular class, you’ll need to use this helper to access the class instance. For example, many classes are instantiated by the main plugin class, and can be accessed with:

wc_memberships_for_teams()->get_*_instance()

For example:

wc_memberships_for_teams()->get_orders_instance()

Classes that are not instantiated in the main plugin class can be accessed through instances of the class that instantiates them:

wc_memberships_for_teams()->get_frontend_instance()->get_teams_area_instance()

Teams object

While we won’t list every method here, the Team object is a good one to review, as this provides methods to get or set almost any piece of team data, or programmatically process seat changes, member invites, adding or removing members, etc.

An instance of this class can be accessed with:

wc_memberships_for_teams_get_team( $team_id_or_post )

Conditional Checks

There are a few conditional checks that can help you determine team or product information.

wc_memberships_for_teams_is_valid_team_member_role( $role )

Checks if a team member role is valid or not.

@since

 

1.0.0

 

@param

 

string $role the role to check

SkyVergeWooCommerceMembershipsTeamsProduct::has_team_membership( $product )

Checks if a product has a team membership attached (purchasing this product creates a team). You must pass an instance of WC_Product to this method.

@since

 

1.0.0

 

@param

 

WC_Product $product

SkyVergeWooCommerceMembershipsTeamsProduct::has_per_member_pricing( $product )

Checks if a product uses per-member pricing (false if per-team pricing is used). You must pass an instance of WC_Product to this method.

@since

 

1.0.0

 

@param

 

WC_Product $product

Global & Static Functions

A non-exhaustive list of some helpful global and static methods for use in customizations.

SkyVergeWooCommerceMembershipsTeamsProduct::get_min_member_count( $product )

Gets the minimum member count required to purchase the team product; returns the integer count or null if not set. You must pass an instance of WC_Product to this method.

@since

 

1.0.0

 

@param

 

WC_Product $product

SkyVergeWooCommerceMembershipsTeamsProduct::get_max_member_count( $product )

Gets the maximum member count allowed when purchasing the team product; returns the integer count or null if not set. You must pass an instance of WC_Product to this method.

@since

 

1.0.0

 

@param

 

WC_Product $product

SkyVergeWooCommerceMembershipsTeamsProduct::get_membership_plan_id( $product )

Gets the membership plan ID that will be granted to a team created via this product; returns the integer count or null if not set. You must pass an instance of WC_Product to this method.

@since

 

1.0.0

 

@param

 

WC_Product $product

wc_memberships_for_teams_get_team( $id_or_post )

Can be used to get an instance of a team. Accepts the team post object or post ID. Returns a Team instance if found, or false on failure.

@since

 

1.0.0

 

@param

 

int|WP_Post $post optional team id or post object, defaults to current global post object

wc_memberships_for_teams_get_teams( $user_id, $args, $return, $force_refresh )

Returns a list of teams for a user (should be preferred over get_posts() calls to protect against data structure changes). Can return either a plain list of team objects or an associative array with query results and team objects, and will return false on failure.

@since

 

1.0.0

 

@param

 

int $user_id optional, defaults to current user

 

@param

 

array $args an array of arguments to pass to WP_Query – additionally, a few special arguments can be passed: {

• • @type string|array $status team status, defaults to ‘any’
  • @type string|array $role a comma-separated list or array of team member roles, defaults to ‘owner, manager’ – specifying this will only fetch teams that the user has one of the given roles
  • @type int $paged the page number for paging the results (corresponds to paged param for get_posts())

}

 

@param

 

string $return (optional) what to return – set to ‘query’ to return the WP_Query instance instead of a list of invitation instances

 

@param

 

bool $force_refresh (optional) whether to force reloading the results even if a previous result has been memoized, defaults to false

wc_memberships_for_teams_get_user_membership_team( $user_membership_id )

Returns the team for a given user membership, if any. Returns false if the membership does not belong to a team.

@since

 

1.0.0

 

@param

 

int $user_membership_id user membership id

wc_memberships_for_teams_get_team_members( $team_id, $args, $return, $null )

Returns a list of team members given the input query (should be preferred over get_posts() calls to protect against data structure changes). Can return either a plain list of team member objects or an associative array with query results and team member objects.

@since

 

1.0.0

 

@param

 

int|SkyVergeWooCommerceMembershipsTeamsTeam $team_id team id or instance to get the team members for

 

@param

 

array $args (optional) an array of arguments to pass to WP_Query – additionally, a few special arguments can be passed: {

• • @type string|array $role a comma-separated list or array of team member roles, empty by default – specifying this will only fetch members with the given role
  • @type int $paged the page number for paging the results, corresponds to paged param for get_users()
  • @type int $per_page the number of team members to fetch per page, corresponds to the number param for get_users()

}

 

@param

 

string $return (optional) what to return – set to ‘query’ to return the WP_User_Query instance instead of a list of team member instances

 

@param

 

bool $force_refresh (optional) whether to force reloading the results even if a previous result has been memoized, defaults to false

wc_memberships_for_teams_get_team_member_roles()

Returns a an associative array of available team member roles.

@since

 

1.0.0

wc_memberships_for_teams_create_team( $args )

Programmatically creates a team. Returns a new Team object on success which can then be used to add additional data, but will return SV_WC_Plugin_Exception on failure.

@since

 

1.0.0

 

@param

 

array $args (see below)

 

@param

 

string $action ‘create’ or ‘renew’; defaults to ‘create’

 

@return

 

Team|SV_WC_Plugin_Exception

The arguments you can pass in to create a new team are as follows:

wc_memberships_for_teams_create_invitation( $args )

Programmatically creates a team invitation. Returns a new Invitation object on success which can then be used to add additional data, but will throw SV_WC_Plugin_Exception on failure.

@since

 

1.0.0

 

@param

 

array $args (see below)

 

@return

 

Invitation|SV_WC_Plugin_Exception

The arguments you can pass in to create a new invitation are as follows:

wc_memberships_for_teams_get_invitation( $id, $email )

Returns a specific invitation for a team, or false on failure.

@since

 

1.0.0

 

@param

 

string|int|WP_Post|Invitation|Team $id invitation token, id, or instance; or team id or instance

 

@param

 

string $email (optional) invitation recipient email, required if $id is a team id or instance

wc_memberships_for_teams_get_invitations( $team_id, $args, $return, $force_refresh )

Returns a list of invitations (should be preferred over get_posts() calls to protect against data structure changes). Can return either a plain list of invitation objects or an associative array with query results and invitation objects.

@since

 

1.0.0

 

@param

 

int $team_id team id to get the invitations for

 

@param

 

array $args an array of arguments to pass to WP_Query – additionally, a few special arguments can be passed: {

• • @type string|array $status invitation status, defaults to ‘pending’, can be used instead of $post_status
  • string|array $role a comma-separated list or array of team member roles, empty by default – specifying this will only fetch invitations that grant the one of thge specified roles for the user
  • @type int $paged the page number for paging the results, corresponds to paged param for get_posts()
  • @type int $per_page the number of invitations to fetch per page, corresponds to the posts_per_page param for get_posts()

}

 

@param

 

@param string $return (optional) what to return – set to ‘query’ to return the WP_Query instance instead of a list of invitation instances

 

@param

 

bool $force_refresh (optional) whether to force reloading the results even if a previous result has been memoized, defaults to false

User Documentation

The post Teams for WooCommerce Memberships Developer Documentation first appeared on CODIBU.

MailChimp for WooCommerce Memberships gives you the ability to sync your members from WooCommerce Memberships to a MailChimp list of your choice.

When you connect your site to MailChimp, this plugin will ensure all member data remains synced to MailChimp, letting you segment your mailing list by membership type, status, and more!

Installation

1. Download the extension from your WooCommerce dashboard
2. Ensure your store meets the plugin requirements.
3. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded
4. Click Install Now, and then Activate
5. Click the Configure link, or go to WooCommerce > Memberships, and read the next section to learn how to setup and configure the plugin.

Requirements

• WooCommerce 2.6.14 or newer
• WordPress 4.6 or newer
• PHP 5.3 or newer (you can see this under WooCommerce > Status)
• WooCommerce Memberships 1.9.0 or newer

Setup & Configuration

Settings for this plugin can be found under WooCommerce > Settings > Memberships > MailChimp Sync. Here, you’ll enter your API key for your MailChimp account, then configure how member data should be tied to MailChimp.

Get MailChimp API key

First, we need to get your API key from your MailChimp account, as this will let the plugin pull in data about your lists. You can find this by clicking “Account” from your menu while logged in.

Next, click “Extras”, then API Keys, to view any API keys for your account, or create new ones.

Finally, if you have an API key already, you can use your existing key, or generate a new one (we recommend using a new key). Then, copy this key.

Paste your API key into the plugin settings, and save your settings. You’ll then be able to configure plugin settings with access to your MailChimp lists and merge tags.

Extension settings

Under WooCommerce > Settings > Memberships > MailChimp Sync, once you’ve saved a valid API key, you’ll now see data related to your MailChimp account.

The first thing to do is to select the list your members should be synced to, and save your settings. When you’ve selected your list, the plugin will automatically push new merge tags to your MailChimp Account. You’ll have one merge tag per plan, along with an ISACTIVE merge tag.

You can now map merge tags to your existing membership plans. You can use the tags the plugin has created for you, or select merge tags of your own (in case you’ve already had member data present in MailChimp).

To see more details on what each merge tag represents, please view our notes on MailChimp segments. These merge tags are automatically updated every time a membership is changed to ensure that status and member data are always up-to-date in MailChimp.

Other settings

• Enable Debug Mode – enable if you experience issues with your MailChimp connection; as a best practice, this should be disabled unless actively troubleshooting.
• Members Sign up – Determine if members are signed up for your list automatically, or if they must opt into your list. Please see our overview below on whether or not opt in is required.
• Members Signup Prompt Text – Enter the text to use for opt in at checkout and from the members area if a member has not opted into your list.
• Members Signup Button Text – Enter the call to action text for the members area opt in.

Finally, you can configure some general settings for how to handle certain membership events.

• Deleted memberships – Determine whether deleting a user membership unsubscribes the member from your list, or removes the member from your list. If the member has more than one membership, the member will only be removed or unsubscribed if all memberships have been deleted (though merge tags will still be updated to reflect accurate membership data).
• Deleted plan merge fields – Determine what to do with plan merge tags if a plan is deleted. You can keep existing merge tags in MailChimp, or delete those merge tags when plans are deleted.
• Sync members – This action forces a member sync with MailChimp — helpful if you’ve just installed, or had your site in maintenance mode and need to update membership records.

MailChimp usage

Do I need consent to add members to my list?

This depends entirely on what kind of emails you’ll be sending to this list. Are you sending emails related to the membership perks and content available? Or related to the lifecycle of this person’s membership? If your emails are for the purpose of fulfilling a contractual obligation, legal obligation, or for a legitimate business interest, you likely do not need consent. Jilt has a great overview of the GDPR and email marketing that we’d recommend reading in order to determine how your own business should comply with privacy regulations like the GDPR and PECR.

MailChimp segments

As changes happen to membership data on your site, these changes are automatically synced with MailChimp so your subscriber data is always updated. The following events will update your subscriber data in MailChimp:

In short, you’ll always have a plan merge tag updated with the current membership status (such as “active”, “pending”, “expired”, etc), as well as an ISACTIVE merge tag that is updated to reflect whether the subscriber has any active membership on your site (will always be “yes” or “no”).

This helps you create segments in MailChimp so you can target emails to particular members, all members, or members with specific statuses.

MailChimp only allows for up to 5 segmentation conditions, so the ISACTIVE tag can be very handy to target multiple plans at once.

Here are a couple general rules to help you create segments:

• The ISACTIVE merge tag will be empty if the subscriber has no membership records on your site. It will be “yes” if they have any active memberships, and “no” if they have had memberships that have since become inactive.
• The plan-specific merge tags will always have the current status as the value of the merge tag (here’s a quick reference list). The plan-specific merge tag will be empty if the subscriber has no memberships for that plan (active or inactive).

Admin Usage

For the most part, you’ll never have to push a member sync to MailChimp after set up, as the plugin will do this automatically. Once you’ve set up your list and merge tags, we do recommend using the “Sync now” action in settings to push your membership data to MailChimp.

If you find that you want to force data to update at any time, you can do so from the plugin settings, or from your “Members” list via bulk action or single membership action.

Your plans list will also have merge tags displayed for quick reference if you’re building segments.

Note that merge tags are not editable from the plan view; they can only be edited via plugin settings. We do not recommend changing merge tags once you’ve started syncing members. If you do, please perform a full sync from the plugin settings so MailChimp data is accurate.

Customer experience

For most stores, customers will not see anything on the frontend of your site while using this plugin. However, if you’ve enabled opt-in for members (after reviewing our notes on privacy / opt-in), then your customers will see opt-in prompts in two locations:

At checkout while purchasing a membership as a guest, or while logged in as a member:

In the members area of their account if they haven’t opted in:

Members can unsubscribe from your emails when sent.

Frequently Asked Questions

Q: Can I remain GDPR-compliant while adding members to my list?
A: Yes! It depends on the basis you have for sending those emails, and what kind of emails you’re sending. Please review our notes on privacy to determine what’s best for your site.

As for personal data erasure requests, these are handled by the main memberships plugin, along with your settings for deleted memberships. Please review the Memberships privacy details for further information.

Q: What will happen if I delete or expire a membership, but the customer still has other active memberships on my site?
A: When there’s a change to expire or remove one membership, other memberships are also checked before pushing data to MailChimp. In this case, since the customer has other active memberships, they won’t be removed or unsubscribed, and your “Is active” merge tag will remain “yes”. The membership being deleted will have its plan merge tag cleared in this case only to reflect there is no longer member data for that plan.

Q: I have a lot of plans, and I want to target active members of some of them, but I don’t have enough segmentation conditions. How can I do this?
A: Unfortunately you may be limited by the segmentation options within MailChimp if you have several plans you want to target in a segment. When this happens, we recommend creating a segment for each plan, then duplicating your campaigns to segment for different plans with the same content so you can reach your intended audience.

Troubleshooting

Having difficulty with the plugin? Please ensure your site meets the plugin requirements, and if so, get in touch with the support team for assistance.

The post MailChimp for WooCommerce Memberships first appeared on CODIBU.

Teams for WooCommerce Memberships lets you sell memberships to groups of people, such as companies, organizations, and classes. When you sell a team membership, the team owner is responsible for team maintenance (such as adding members and managing billing), while members enjoy all the benefits associated with the membership plan.

Installation

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
4. Click Install Now and then Activate.
5. Click Configure and read the next section to learn how to setup the plugin.

Requirements

At a minimum, your site must meet the following requirements to use Teams for Memberships:

• WooCommerce 3.0.4 or newer
• WordPress 4.6 or newer
• PHP 5.3 or newer (you can see this under WooCommerce > Status)
• WooCommerce Memberships 1.9.4 or newer

Translations

This plugin is translation-ready under the following text domain:

woocommerce-memberships-for-teams

Click here for guidelines on translating extensions.

Getting Started

Settings

You can find the following Teams for Memberships settings under WooCommerce > Settings > Memberships > Teams:

• Teams are called: If you’d like to use a different term instead of “team” and “teams” (e.g., club / clubs, family / families, etc.), you may update these fields with your desired terms.
• Allow removing members: Check to let team owners and managers remove members from their teams.
• Owners must be members: Check to require that team owners take up a seat on their teams.
• Allow managers to add or remove other managers: Check to let managers add or remove other managers from the team. Team owners are always allowed to add and remove managers. Click here to learn more about team roles.

The Teams for Memberships endpoint settings for team account management are found under WooCommerce > Settings > Advanced in the Account endpoints section:

Creating Team Membership Products

You must create a team membership product to let customers purchase a team membership. Team membership products require special configuration to detail the size, price, and plan access associated with the team.

Follow the steps below to create a team membership product:

1. Go to Products and click Add New.
2. Under the Product Data section, set the product type. You can use simple/variable products or simple/variable subscriptions for a team membership product.
3. Check the Team Membership box. This will expose new fields related to team pricing, size, and membership plan:
   • Team Pricing: Should the team be priced per-member or per-team?
   • Price: The per-team or per-member price.
   • Sale price: (Optional) The per-team or per-member sale price.
   • Minimum member count: For per-member priced teams, the minimum number of members required to purchase a team. Leave blank to enforce no minimum member count.
   • Maximum member count: The maximum number of members allowed on the team. Leave blank to allow unlimited seats.
   • Team members will have access to: Select the membership plan that members of this team will be assigned to.

   

   If you are working with a variable product or variable subscription, these settings can be largely controlled from the individual variations:

   

4. Populate any other details for the product and its variations, if applicable, as desired.

As an administrator, you can view the products and variations required to purchase a team membership from the associated membership plan’s page under WooCommerce > Memberships > Membership Plans:

However, please note that due to the additional settings associated with team membership products (such as team pricing and size requirements), you can’t add or remove team products from this area. All other settings associated with the membership, such as its length, content, discounts, etc. are configured on this page as with an individual membership.

If team access is sold via a simple or variable product, team members will have access to the membership plan for the plan length. For example, suppose a team was purchased on January 1 for a plan that grants access for 1 year. If a member is added to the team on February 1, the member has access until February 1 of the follow year. Once the user membership ends, the membership is over unless the team is renewed.

Team Roles

There are three roles for the users associated with a team – owners, managers, and members:

Creating, Joining, and Managing Teams as a Customer

When a customer purchases a team, they become the team owner and are responsible for managing the team and its members.

Purchasing Teams

Purchasing a team membership product is similar to purchasing any other product, with a few extra steps:

• Team Name: The owner must enter a name for their team. This can be changed later by the team owner or the site administrator.
• Take up a seat: Unless you require owners to take up a seat on the team, owners can choose whether or not they will be a team member as well as an owner. If a team owner is also a team member, they can access all content, products, and discounts associated with the membership plan. If a team owner is not a team member, they can manage the team but can’t take advantage of the membership plan benefits.
• Number of Seats: For a per-member priced team, the owner must include the number of seats they’re purchasing for their team. Team minimum and maximum seat counts, if applicable, will be enforced.

As with all memberships, the team owner must create an account before or during the checkout process when purchasing a team membership so they can manage the team from their My Account area.

Inviting Members

Owners and managers can add members to their team by going to My Account > Teams > Add Member. From this page, the owner or manager can add users to the team in two ways:

• Registration Link: Any user that clicks this link can register for the team. The owner or manager can regenerate the link to deactivate the previous link. This method is quick and easy, but less secure.
• Add Member: The owner or manager can enter the user’s email and role to add members to the team individually. This method is secure, but requires more manual work.

The owner or manager can view pending invitations by going to My Account > Teams > Members > Pending invitations. From this page, the owner or manager can resend the invitation, cancel the invitation, or change the new user’s role.

Once a user is invited to a team or selects the Registration Link, they can register for an account (if they haven’t already done so) and join the team. The process varies for new users and existing users, but everyone must have an account on your site before they can join the team.

If the invitation was sent to email A, but the user has an account on your site under email B, they can choose to either join the team under email B or create a new account for email A.

When a member joins a team, they can access all the benefits and content associated with the team’s membership plan. Members can view the membership perks from the member area, if enabled, under My Account > Memberships. From the members’s perspective, the only difference between an individual membership and being a member of a team is that the team member has no control over billing or renewals – that’s all managed by the team owner.

Managing Members

If Teams for Memberships settings allow owners and managers to remove members, they can do so by going to My Account > Teams > Members and selecting the Remove button. They can also change the role assigned to users from this page.

Members can also choose to leave the team by going to My Account > Memberships > Manage > Leave Team, but they will lose access to the membership perks at that point.

Adding Seats to a Team

After a team is purchased, the team owner may want to adjust the number of seats on the team. Team owners can add seats to teams that are:

• Active
• Associated with a product
• Under the maximum allowed seat count
• For per-team priced teams, limited in seat count – there’s no need to add seats to unlimited teams! 

For teams that meet these conditions, owners can add seats by following the steps below:

1. Go to My Account > Teams > Team Settings.
2. Click Add Seats.
3. Enter the number of seats you want to add to the team. For per-team priced teams, enter the number of blocks of seats you want to add. A block of seats is equal to the team’s maximum seat count.
4. Click Submit.

The team owner will be directed to a checkout page to pay for the new seat(s). For per-member priced teams, the owner will be charged according to the per-member price for that team product. For per-team priced teams, the owner will be charged the team price for the new block of seats.

Managing Billing

If the team membership expires, the team owner can renew the membership by going to My Account > Teams > Team Settings and selecting Renew. The team owner will then go through a checkout process for the new membership.

Managing Teams as an Administrator

You can view all the teams on your site from WooCommerce > Memberships > Teams. From here, you can view, filter, add, edit, and delete teams.

You can also view team memberships from the WooCommerce > Memberships > Members page. From this page, you can see the team associated with the membership and the user role’s within the team, if applicable. You can also search by teams or filter the list of members to exclude team members.

When editing a team member from this page, you’ll see a notice that recommends editing the team membership instead of the membership access for the team members. This is because editing the membership of a team member directly (instead of initiating that change from the team settings) can cause problems with that member’s access. For example, changing the expiration date for a team member’s access will place that member out of sync with the rest of the team’s access to membership content and perks.

Adding Existing Members to a Team

If you want add existing members to a team, you can manually create and move their memberships under a team by following the below steps:

1. Go to WooCommerce > Memberships > Teams and click Add New.
2. Set the team name. The team owner can change the team name later.
3. In the Team Details section, set the owner and other team settings.
4. In the Billing Details section, you can designate the team membership product, which is important if you want owners to be able to renew the team’s access.
5. Click Update.

The team owner can now manage the team from their account. You can advise the owner to share the Registration Link to invite members to their new team. When the members select this link and join the team, their existing membership will move under the team’s management and billing.

Exporting Team Data

You can use the WooCommerce Memberships export to retrieve the following Teams for Memberships information:

• Team ID
• Team Slug
• Team Name
• Team Role

Please note that these fields are read-only – you cannot update Teams for Memberships information via an import at this time. If updating teams via import is important feature for you, please let us know.

Teams for Memberships and WooCommerce Subscriptions

When you use Teams for Memberships with WooCommerce Subscriptions, you can sell team access with recurring billing. Before getting started, please review our documentation on the integration between WooCommerce Memberships and WooCommerce Subscriptions.

In general, subscription-tied teams are similar to regular teams. When a team is tied to a subscription, all team user memberships follow the subscription record. If the subscription is paused or cancelled, the user memberships will also be paused or cancelled. If the team is unlinked from the subscription, all the team user memberships will be unlinked from the subscription, too.

Creating Team Subscription Products

Creating a team subscription product is very similar to creating a standard team membership product. You can use simple or variable subscriptions to sell access to team memberships. When using per-member pricing for the team, all subscription fees (including sign-up fees, if applicable) are multiplied by the seat count.

The team subscription product will appear when editing the membership plan from WooCommerce > Memberships > Membership Plans. You can set the subscription-tied membership length from this page, which will also apply to any individual subscription-tied memberships under this plan. Click here to read more about subscription-tied membership length.

Adding Existing Members to a Subscription-tied Team

To add existing members to a subscription-tied team, you can manually create the team, link it to the subscription, and move their memberships under the team by following the below steps:

1. Manually create the subscription

First, you’ll need to manually create the subscription for the team owner. Click here for instructions on manually creating subscriptions. If you’re creating a per-member priced team, be sure that the subscription quantity and price correspond to your desired number of seats!

2. Manually create the team

Follow the steps below to create the team in the admin area:

1. Go to WooCommerce > Memberships > Teams and click Add New.
2. Set the team name and Team Details, such as owner and seat count.
3. Click Update.

3. Link the team to the subscription

Follow the steps below to link the manually created subscription and team:

1. In the team you just created, check the URL bar to get the team ID and copy it to your clipboard.
2. Go to WooCommerce > Subscriptions and open the manually created subscription.
3. Click the pencil icon for the team membership product item.
4. Click Add Meta.
5. Enter _wc_memberships_for_teams_team_id as the meta key Name and the team ID (copied to your clipboard!) as the Value.
6. Click Add Meta.
7. Enter team_name as the meta key Name and the team name as the Value.
8. Click Save.

4. Update team details

Now, you’ll need to update the team details by following these steps:

1. Go to WooCommerce > Memberships > Teams and open the team.
2. Under the Billing Details section, link the team membership product and the subscription.
3. Click Update.

5. Invite members

The team owner can now manage the team from their account. If the owner should take up a seat on the team, you can add them to the team at this stage. If you want to leave that up to the owner, they can add themselves to the team.

You can advise the owner to invite members to their new team by sharing the Registration Link. When the members select this link and join the team, their existing membership will move under the team’s management and billing. Once members migrate to the team, you’ll need to cancel their existing member subscriptions so the owner can manage all billing.

Changing the Seat Count on a Subscription-tied Team

Team owners can add or remove seats from their subscription-tied team. The impact on billing varies based on whether the owner is adding or removing seats and how the team is priced – per-team or per-member.

Adding or Removing Seats on a Per-Member Priced Team

The team owner can follow the steps below to change the number of seats on their team:

1. Go to My Account > Teams > Team Settings and click Change Seats.
2. Enter the new seat count.
3. Click Submit.

If the owner is adding seats, they will go through the checkout process to pay for the new seat’s immediate access and to update the recurring total going forward. The initial charge will be prorated to account for the time remaining in the current billing cycle to ensure the owner is charged fairly for the new seats.

For example, if a subscription charges $10/member/month and the team is halfway through the billing cycle when a seat is added, the owner will initally pay $5 for that seat. When the team renews at the end of the month, the new seat will be charged $10 for renewal, like all other seats on the team.

If the owner is removing seats, the recurring total will be reduced to account for the lost seats. However, the owner will not be reimbursed for any unused time on the current billing cycle for those seats. The new recurring total will apply to the next renewal payment.

Adding Seats on a Per-Team Priced Team

All seat additions on a per-team priced team are made in a block equal to the team’s maximum seat count. For example, if a team permits up to 10 seats, you can add seats in 10-seat blocks. Adding seats for a per-team priced team is essentially like purchasing a new team and bringing it under the current team’s management. You cannot remove seats from a per-team priced team.

The owner can follow the steps below to add seats to their team:

1. Go to My Account > Teams > Team Settings and click Add Seats.
2. Enter the number of blocks you want to add to the team.
3. Click Submit.

Frequently Asked Questions

Q: Can team owners change the name of their team?
A: Yes – team owners can change the name of their team from My Account > Teams > Team Settings.

Q: Will team members get renewal emails for their memberships?
A: No – individual team members won’t get their own renewal or expiration emails because they can’t act upon them. The team owner alone is responsible for managing billing and renewals, so they will receive all renewal and expiration emails.

Q: Can team owners add or remove seats from their team?
A: Yes! Team owners can change the seat count on their team, though this varies based on the type of team and how it is priced. Click here to read about changing seats.

Q: Can I provide quantity discounts for increasing the number of members?
A: Sure thing! For a stepped approach (e.g., price breaks at 5 members, 10 members, 15 members, etc.), you can use variable products to create tiered discounts. You can also use Dynamic Pricing to discount the per-member or per-team price based on the number of seats or teams selected.

Q: Can I move existing user memberships into a team so they’re managed by one person?
A: Sure! Click here to learn more about adding existing members to a team.

Q: Can I make the membership plan length longer or shorter for team members than for individual members?
A: No – at this time, members share the same plan length, regardless of team affiliation. If you’d like to set different access periods for team members vs individual members, you’ll need to setup two different plans. You can duplicate a plan to assist with set up! Please let us know if this feature is important to you.

Q: What happens if a team purchase is refunded?
A: For a full refund, all memberships on the team are cancelled. This means that the team owner and managers can’t add any new members to the team. For a partial refund, you can adjust the team seats and cancel members manually as needed.

Q: What happens if the team owner stops the subscription?
A: For subscription-tied teams, changes in the subscription status are inherited by all members of the team. If the subscription is paused, all team memberships are paused. If the subscription is cancelled, all team memberships are cancelled as well.

Q: How long do team members have access to membership perks?
A: This depends on the team billing:

• If the team is tied to a regular product, then members have access for the full membership period. If the membership should last one year, each user’s membership runs for a year, regardless of when they started.
• If the team is tied to a subscription product, then this depends on your plan settings. If the subscription has a set-length, the user memberships will act like regular memberships. If the team follows the subscription length, the team memberships last until the subscription ends or is cancelled.

Q: One or more of my team owners renewed their team for $0, and I saw an admin notice that says this was due to a plugin bug. How can I ensure this team owner pays for their access?
A: First, we are so sorry about this issue. While it only impacts a small number of teams – only teams with per-team pricing and unlimited seats – we regret any frustration caused by this issue. At this point, you can choose to do nothing and your future renewals will be charged appropriately, or you can end the affected team memberships to force the team owner to renew now by following these steps:

1. Go to WooCommerce > Memberships > Teams and look for any teams with unlimited seats in your teams list.
2. View the team’s most recent renewal under the Billing Details to see if the renewal processed for $0.
3. Change the Team memberships begin to expire field to today and click Update.

If you have any questions about this process or need assistance locating affected teams, please contact our support team. We would be happy to help make this right.

Troubleshooting

Having difficulty with the plugin?

• Please ensure your site meets the plugin requirements.
• If you’re experiencing issues migrating existing memberships or subscriptions into a team structure, please review our guide for adding existing members to teams or manually adding existing members to subscription-tied teams.
• If you’re experiencing a different issue, please get in touch with the support team for assistance.

The post Teams for WooCommerce Memberships first appeared on CODIBU.