SFDO-Community-Sprints/Membership-Essentials-App

Determine whether to use Custom Metadata or Custom Settings to control membership behavior

D-McGovern opened this issue · 2 comments

Would be good to pull in an SFDO engineer to get current best practices/guidelines for this as both are present in recently released packages

Currently have CMTD in place but not attached to this

Configuration options

Membership terms -
Globally defined in settings for all membership type, or product based (recurrence defined on the product)

Opportunity Automation -
Allow opportunity to to auto-create membership

MCR Automation -
Enable/disable

NPSP Integration -
Populate MCRs from affiliations
List of affiliation roles that trigger MCR automation
Default GAU allocations for a product

Standard/primary membership type -
Base membership type - are they a member of our org or not