This article shares a possible use case you could support, as well as a sample flow that could support this use case. This can be a helpful jumping-off point.
In this scenario, a platform hosts virtual events, and during these events, participants should temporarily make their profiles public to encourage networking and interaction. However, once the event is over, participants’ profiles should revert to their original privacy settings.
To change privacy settings for an event:
- Call Create Event and store the event details along with a list of participants.
- Schedule when the privacy settings should change for participants, such as starting 1 hour before the event begins and ending 1 hour after the event finishes.
- Before the event starts, call Set Member Privacy Settings and change the
publicMemberVisibility field to VISIBLE_TO_ALL.
- After the event ends, revert the profile visibility settings to the original settings using the stored backup. This ensures that the participant’s profile returns to the level of visibility it had before the event.
- The entire process can be automated through event triggers, such as:
- Event started: Triggered automatically at the event’s start time.
- Event ended: Triggered automatically at the event’s end time.