> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ally.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule and Record Tabletops on Google Meet

> Schedule and record a tabletop exercise on Google Meet so Ally Security can ingest the recording, generate a transcript, and produce an after-action report.

<Tabs>
  <Tab title="Meeting in Progress">
    This method allows you to invite Asa (our bot) to your live meeting using a Google Meet link. This requires that the meeting has already started and there is at least one participant in the meeting who can admit Asa from Google Meet's lobby.

    <Steps>
      <Step title="Get meeting link">
        Join your Google Meet meeting and copy the meeting link from the address bar or by clicking the meeting info button.
      </Step>

      <Step title="Invite Asa">
        Navigate to your Ally Security dashboard and paste the Google Meet link to invite Asa to join the meeting.
      </Step>

      <Step title="Allow Asa to join">
        When Asa requests to join, admit the bot from the Google Meet lobby. Any participant in the meeting can approve Asa's entry. If needed, use the three-dot menu next to Asa in the participant list and select **Admit entry**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Scheduling for Future">
    This method allows you to schedule Asa (our bot) to automatically join your future Google Meet meetings by adding Asa as a meeting participant.

    Important note: Do not use the schedule for future (i.e. inviting Asa via calendar invite) **unless you are scheduling >30 minutes in advance.** For short notice invites, use "Meeting in Progress" tab.

    <Steps>
      <Step title="Get your Asa email">
        From your dashboard, copy your unique Asa email address that will be used to invite the bot to meetings.

        <img src="https://mintcdn.com/ally-3fa917c3/sbdyCRV9yWM9gmBb/images/image.png?fit=max&auto=format&n=sbdyCRV9yWM9gmBb&q=85&s=5962b9d4e0c2a629410944f977231cfa" alt="image.png" title="image.png" style={{ width:"31%" }} width="1578" height="988" data-path="images/image.png" />
      </Step>

      <Step title="Add Asa to your meeting invite">
        When creating your Google Meet meeting or calendar event, add your Asa email address as an attendee.
      </Step>

      <Step title="Ensure Asa has accepted your invite">
        Check that Asa has accepted the meeting invitation. You should see the acceptance in your calendar or meeting details.
      </Step>

      <Step title="Allow Asa to join">
        When the meeting starts, admit Asa from the Google Meet lobby when prompted. The bot will appear as your designated Asa email address. If needed, use the three-dot menu next to Asa in the participant list and select **Admit entry**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

**Note: You cannot invite Asa through the Google Meet interface, you must add the link to the Ally console.**

<img src="https://mintcdn.com/ally-3fa917c3/sbdyCRV9yWM9gmBb/images/image.png?fit=max&auto=format&n=sbdyCRV9yWM9gmBb&q=85&s=5962b9d4e0c2a629410944f977231cfa" alt="image.png" width="1578" height="988" data-path="images/image.png" />

### Limitations

The following Google Meet features are currently not supported:

| Feature                 | Status        |
| ----------------------- | ------------- |
| Google Meet Livestreams | Not supported |
| Breakout Rooms          | Not supported |

<Info>
  Contact us at [support@ally.security](mailto:support@ally.security) if you need any of these capabilities.
</Info>

### Recording Behavior

No recording permission is needed for Google Meet calls. This means that as long as Asa (our bot) is in the call, it will be able to record.

### Joining Behavior

By default, Asa (our bot) needs to be **manually admitted** into calls and will appear as an "anonymous" user.

Google Meet may **visually identify Asa as a bot** to participants (for example, with a bot label or indicator). That visibility change does **not** affect Asa's ability to join the call or record the meeting after admission—it only makes it clear which participant is the bot.

When Asa attempts to join a Google Meet call, a dialog will be displayed to participants asking to admit Asa. Any signed-in participant in the host's Google Workspace can let Asa in. You can also admit Asa from the participant list: open the **three-dot menu** next to Asa and select **Admit entry**.

### Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Why does Asa need to be manually admitted?">
    By default, Asa (our bot) appears as an anonymous user and needs manual admission to Google Meet calls. This is a security feature of Google Meet to prevent unauthorized access to meetings.

    Any signed-in participant in the host's Google Workspace can admit Asa into the meeting.
  </Accordion>

  <Accordion title="Why does Google Meet show Asa as a bot?">
    Google Meet may display a bot indicator for Asa so participants can see which join request comes from a recording bot. **This does not block Asa from joining or recording** once someone admits the bot. If Asa is waiting to join, use the lobby prompt, or open the **three-dot menu** next to Asa in the participant list and select **Admit entry**.
  </Accordion>

  <Accordion title="What are Google Meet Livestreams and why aren't they supported?">
    A Google Meet livestream allows users to broadcast a video meeting to a large audience in a view-only format. This is particularly useful for events where interaction is not required from the viewers, such as webinars.

    Google Meet livestreams are currently not supported by our recording system.
  </Accordion>

  <Accordion title="Can Asa join breakout rooms?">
    No, Google Meet breakout rooms are not currently supported. The recording will only capture the main meeting room.
  </Accordion>

  <Accordion title="Does Asa need special permissions?">
    No special recording permissions are required for Google Meet calls. As long as Asa is admitted into the call, it will be able to record the meeting.
  </Accordion>
</AccordionGroup>