Open-to-everyone invites is now "Connection Invites: Rollout—Unrestricted".
"Connection Invites: Rollout (open-restricted)" is a new option that filters invite eligibility based on a new whitelist which only permits whitelisted users to receive invites. The whitelist is normalized to user ids in the DB but can be uploaded and downloaded as a CSV file email addresses.
Ignore empty user_id notify-connect
For ease of use, the main option is now a dropdown, the max. invite pool size now defaults to 10, and help text is rearranged for clarity.
"Whitelist" now means "is eligible to receive a connection invite". Related store methods have been refactored/repurposed and now serve the new whitelist semantics.
The old "whitelist" really meant "user has connected at some point in time and should always be permitted to reconnect if they become disconnected." — this "has-connected" tracking has moved to new columns in msteamssync_users - .lastconnectat and .lastdisconnectat.
The old msteamssync_whitelisted_users table is not removed, but its rows are deleted as a marker that the migration was completed. This is largely backwards compatible as prefillWhitelist in prior versions rebuilds the old whitelist from the users table (only presently-connected users, however.) Tracking of users who were previously-connected, but are not presently-connected is not accessible in rollback scenarios, but is preserved in the new .lastconnectat and .lastdisconnectat columns for all forward versions, even in the event of rollback and re-upgrade.
Summary
notify-connectFor ease of use, the main option is now a dropdown, the max. invite pool size now defaults to 10, and help text is rearranged for clarity.
"Whitelist" now means "is eligible to receive a connection invite". Related store methods have been refactored/repurposed and now serve the new whitelist semantics.
The old "whitelist" really meant "user has connected at some point in time and should always be permitted to reconnect if they become disconnected." — this "has-connected" tracking has moved to new columns in
msteamssync_users-.lastconnectatand.lastdisconnectat.The old
msteamssync_whitelisted_userstable is not removed, but its rows are deleted as a marker that the migration was completed. This is largely backwards compatible asprefillWhitelistin prior versions rebuilds the old whitelist from the users table (only presently-connected users, however.) Tracking ofusers who were previously-connected, but are not presently-connectedis not accessible in rollback scenarios, but is preserved in the new.lastconnectatand.lastdisconnectatcolumns for all forward versions, even in the event of rollback and re-upgrade.Ticket Link