The coordinated itinerary is an overloaded itinerary with the added ability of supporting multiple or recursive itineraries.
A user can create a coordinated itinerary where they can add people into the event, group them by event in the itinerary, attach specific notifiers to specific users or events that notify users in the group based on available notification methods, etc..
Users can assign other coordinators who can manage the itinerary as-well, each of these persons is provided a scope of id's that they're allowed to access which correlate with the itinerary they're accessing.
Users should be able to invite people into events and users within that managed itinerary should be able to manage their own sub-itinerary such as personal flight information if a group coordinated flight hasn't been assigned or they have specific preferences.
They should have elevated security measures to ensure non-coordinators cannot view information not associated with them. The flow state can return something such as "coordinator" to signify the context they're within is viewable to them where "coordinated" is a person only allowed to view their specific information or collective information about the event.
The coordinated itinerary is an overloaded itinerary with the added ability of supporting multiple or recursive itineraries.
A user can create a coordinated itinerary where they can add people into the event, group them by event in the itinerary, attach specific notifiers to specific users or events that notify users in the group based on available notification methods, etc..
Users can assign other coordinators who can manage the itinerary as-well, each of these persons is provided a scope of id's that they're allowed to access which correlate with the itinerary they're accessing.
Users should be able to invite people into events and users within that managed itinerary should be able to manage their own sub-itinerary such as personal flight information if a group coordinated flight hasn't been assigned or they have specific preferences.
They should have elevated security measures to ensure non-coordinators cannot view information not associated with them. The flow state can return something such as "coordinator" to signify the context they're within is viewable to them where "coordinated" is a person only allowed to view their specific information or collective information about the event.
https://github.com/heyitsmass/BayView/blob/b335f46bd55299100313360e111e700b8bc3f6a0/src/types/ItineraryManager.ts#L205-L232