How does Notta Bot work when multiple members enable auto-join?

In workspaces with multiple members, Notta prevents the Bot from joining the same meeting multiple times. This helps avoid duplicate transcripts and keeps meetings running smoothly.

How it works

Even if multiple members in the same workspace have auto-join enabled for the same meeting, the Bot automatically joins only once.

Notta coordinates auto-join settings across members within a workspace so that only one Bot joins each meeting. This prevents multiple Bots from joining at the same time, which could otherwise create duplicate transcripts or disrupt the meeting.

This behavior applies only when all of the following conditions are met:

  • Condition 1: The Bot is invited to the meeting through the calendar's automatic join settings.
  • Condition 2: Members with auto-join enabled for the calendar event belong to the same workspace.

Transcript ownership and access

When multiple workspace members have auto-join enabled for the same calendar event, transcript ownership is determined as follows:

  • First priority: Event creator (host)
  • Second priority: The order in which members were invited to the event

Ownership only determines who is listed as the creator.
Members who are not the transcript creator but have auto-join enabled still have full access to the transcript. They can view, edit, and share it as usual.

Examples

 

Case

Outcome

Example 1

  • A, B, and C belong to the same workspace.
  • All three have auto-join enabled for the same meeting.
  • Only one Bot joins the meeting.
  • Only one transcript is created.
  • The transcript creator is the event creator (host) if they have auto-join enabled. Otherwise, it is the member who was invited first.
  • Other members with auto-join enabled can still view, edit, and share the transcript as usual.

Example 2

  • A, B, and C belong to Workspace①.
  • B also belongs to Workspace②.
  • Either A or C in Workspace① has auto-join enabled.
  • B in Workspace② also has auto-join enabled for the same meeting.
  • This behavior applies separately to each workspace. One Bot joins from Workspace① and one Bot joins from Workspace② — two joins in total.
  • A separate transcript is created for each workspace.
  • The creator of each transcript is determined within that workspace (event creator [host] → order of invitation).
  • Members with auto-join enabled in each workspace can view, edit, and share their respective transcript.

Example 3

  • A is the meeting organizer but does not have auto-join enabled.
  • B and C belong to the same workspace, and both have auto-join enabled.
  • B was invited to the meeting before C.
  • Only one Bot joins the meeting.
  • The transcript creator is not the organizer, but the member with auto-join enabled who was invited first — B.
  • Both B and C can view, edit, and share the transcript.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share