Notes on the IIA Training and how all the pieces fit together
"It's just data" as long as everything is turned on properly.
- GZ set up API that syncs changes in GZ to IIA's national "Active Directory"
- AD is pass-through from GZ to IIA Nat'l
- How does GZ know what should be sent to AD? Membership types
- There are "rules" -> Agency owns membership, branches inherit membership
- Custom fields: "Sync as Member" or "Sync as Affiliate": These are Yes/No custom fields that need to be set up as Membership Type and added to each
- (Member Editable and Required- this is how Big I Kentucky is set up) USUALLY DONE BY ONBOARDING (eventually will be included in the actual Insurance Edition)
- Only have one Agency memtype, and only one Affiliate memtype
- Set custom fields appropriately:
- Agency: Member Yes, Affiliate No
- Affiliate: Member No, Affiliate Yes
- Only ONE memtype set to sync as Member, only ONE memtype set to sync as Affiliate. They can do whatever they want with the rest.
- Integration settings: should all be set up ahead of time
- Agency to Branch relationship: needs to be set to Location so the branches inherit the membership
- Mapping Information details AD/GZ mapping. Cheri is getting required fields from Jack to better indicate.
- "Rules" are from AD, not GZ, and MUST be followed in order for contacts to sync as expected.
- From here on out is mostly just GZ functionality.
- Scenario-based situations:
- When a branch becomes a parent
- When a parent becomes a branch
More details on IIA Sync:
Two way sync from AD to GZ to AD
- States sync to AD (aka DataRec)
- AD syncs to State AND Nat'l tenant (GZ1113)
- Sync was put in place; at the time, GZ didn't have the ability to sync from tenant to tenant
- Not robust sync; doesn't handle things some well due to AD (home-grown solution from Nat'l, NOT WinAD)
- If you are in a GZ tenant (state or Nat'l)- if you make a change to an active record, that will trigger the IIA sync to send to AD (every 15 minutes)
- Sync will take action on record, and will sync back to state if need be, AND will sync to Nat'l
- Changes can be made in AD, at the State, and at Nat'l; no one communicates, it's easy for info to get out of sync
- DataRec= AD (Hank tries to not use "AD" due to possible confusion issues)
- See Hank's "IIA Sync Functionality" doc
- Create org first + billing contact, assign membership to it; do not add agents until national id is assigned and sync has completed!!!!
- If update is changed in DataRec, it syncs to Nat'l and State at the same time