An event is a shared piece of data, and we associate the attendants to an event. Mnay ask why they cannot name their personal meeting (bot) attendant anymore and we explain the bot behavior in detail below.
The term deduplication is going to refer to how an attendant handles the occurrence of more than one for a scheduled event
At Reelay we believe it is an Organizational Attendant and have built the logic around this belief. Here ere is what that means:
* Per Organization (1 Attendant : 1 Org) This is how our system works today and means that many users could have Reelay scheduled on the same meeting but only one would attend per org. In this meeting we would see three bots, one for our respective orgs. In a normal work day you would see one attendant present even though it may be scheduled for it to attend by 6 users. Once the meeting is complete those six would be shared the information from the one that was allowed. The host would get the primary asset and the attendees will have access to the meeting as viewers.
Personal (1 Attendant: 1 User) - If we take this approach Reelay acts more along the lines of a Personal Attendant with a custom name. Many free versions offer personal attendants. These are often not provisioned or secured at an organizational level.
All (1 Attendant) - This is how it worked previously and means that in this call we would actually only see one attendant even though at the end we would all receive an asset. The limitations here are that you may not know in the call who will be receiving assets. Let’s say Scott, Vid, and Deric are expecting to have an Attendant in the meeting that is happening now. Only one of those would make its way in. We may see in the call Meeting Attendant which would lead to some confusion for Deric and Scott on if they were going to get an asset at the end. The way things work they would be getting a Reelay asset within their organizations but not be clear in meetings. We opted to move to an Organizational Asset.
