Domain recognition, aka "Recognized Domains", allows individuals to be automatically granted a group membership under their organization membership, simply by having a domain that "belongs" to the group membership.
To make this more clear, let's use an example.
This description assumes you know what a Group Membership, Employee Account, and Primary Member is. If you don't please see the linked article(s).
The Association for Member-based Organizations (AMO) has group memberships with unlimited Employee Accounts. The AMO runs lots of events, providing training and networking for people in various roles within their respective member-based organizations. Anyone can attend these events, but people who are members of the AMO get tickets at a "members only" price.
One of the members of the AMO is the organization Member365. The Primary Member of Member365 is John Smith and he signs up for the AMO membership using the email: john.smith@member365.com.
John can now add Employee Accounts under the membership; meaning anyone with an Employee Account is considered a member of the AMO (under the Member365 membership) and will receive member pricing for the events they wish to attend.
But imagine Member365 has 100 employees and John doesn't know who will take advantage of the membership perks, so he doesn't want to send out an invite to all 100 employees. Instead, the AMO membership John is a member of is setup to use the recognized domain feature and when he became a member using the email domain "member365.com" that domain automatically became a recognized domain. Now, whenever someone with an email address with the "member365.com" domain goes to register for an event, the system will automatically recognize their domain, make them an Employee Account under the Member365 Group Membership, and present them with the member (opposed to the non-member) pricing for the tickets to the event - even if they've never registered for an event or otherwise been added to the system before.
So, just to make it concrete. Let's say Sally Chan is the Chief Communications Officer at Member365 and does not have an Employee Account with the AMO, but the AMO is hosting an "Optimizing Organization to Member Communications" Event, that she wants to attend. When Sally clicks on the registration link to sign up for the event, she's prompted to put in her email. She types "sally.chan@member365.com" and even though she didn't have an employee account before that moment, the system automatically recognizes that she is an employee of Member365, enrolls her under their membership, and presents her with the tickets priced for members. John doesn't have to add or invite Sally to the membership, she's automatically granted a membership account because her domain ("member365.com") was recognized by the system.
Comments
Please sign in to leave a comment.