Groups

Use groups to manage relationship information with subscriptions, to set up special pricing for subscriptions, and to track usage across organizations. Using groups to set up special pricing for subscriptions allows the groups to share balances and be restricted to using only part of the shared group balance.

Groups can have a relationship with zero or one owners (a user assigned a role with owner permission), zero or more administrators (a user assigned a role with administrator permission), and any number of users. A group can have only one parent group but can have multiple subgroups, which can only be nested hierarchically or situated in-parallel with each other. Subgroups cannot be cyclical, meaning that a subgroup cannot be a member of a parent group in its hierarchy and a parent group cannot be a member of a subgroup in its hierarchy. Groups can be organized hierarchically and span multiple tiers so different pricing configurations can be set up at each tier.

Figure 1 shows three examples of how groups can be organized:
  • Group A is a flat group that consists of one tier and a set of subscriptions. It has an owner, one administrator, and one observer.
  • Group B is a hierarchical group that has three tiers. Tier one has one group with no subscriptions and tiers two and three each contain one subgroup with a set of subscriptions. Group B has multiple administrators in the group hierarchy. Subgroup B1 has an observer and subgroup B2 has an owner.
  • Group C is a hierarchical group that also has three tiers, but organized differently. Tier one is one group with no subscriptions, tier two has two subgroups, one with subscriptions and one without, and tier three has two subgroups, each one with a set of subscriptions. Group C has multiple administrators in the group hierarchy. It has two owners and one observer.
Note: Users assigned one of the predefined roles (owner, admin, or observer) have notification permission and can receive notifications for any of the enabled notification types. For more information about roles, notification types, and enabling product offer/bundle, balance/meter, and threshold notifications, see My MATRIXX Help.
Figure 1. Groups

Associated users with notification permission receive notifications when subscriptions and subgroups reach balance thresholds and credit limits for balances that exist in the group wallet.

Use the GroupAddMembership and GroupRemoveMembership APIs to add and remove group members.

For information about the user and group APIs, see MATRIXX Subscriber Management API.