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

# Sessions

> A session is a single logged time entry within a bundle. Sessions track the date and duration of each meeting, and together they determine how many hours a bundle has consumed.

A session records one unit of work: the date it occurred and how long it lasted (in minutes). Every session belongs to exactly one bundle, and together your sessions determine how many hours that bundle has consumed.

## Session properties

| Property     | Description                                                                                     |
| ------------ | ----------------------------------------------------------------------------------------------- |
| **Date**     | The date and time the session took place.                                                       |
| **Duration** | Length of the session in minutes. Displayed as hours (e.g., 90 min → 1.5 h).                    |
| **Status**   | One of: **Completed**, **Scheduled**, **Pending** (awaiting manager approval), or **Rejected**. |
| **Notes**    | Optional free-text notes attached to the session.                                               |

## Adding sessions

You can add sessions in two ways:

<CardGroup cols={2}>
  <Card title="Manual entry" icon="pen">
    Open a bundle and click **Add session**. Enter the date and duration in minutes, then save.
  </Card>

  <Card title="Google Calendar import" icon="calendar">
    Connect your Google Calendar and import events that match a bundle's calendar keyword. The app fetches events from the last 90 days and lets you select which ones to import.
  </Card>
</CardGroup>

<Note>
  Imported sessions are de-duplicated using the Google Calendar event ID. Re-importing from the same calendar will not create duplicate sessions.
</Note>

## How sessions affect bundle progress

Every time you add or delete a completed session, the bundle's completed hours update automatically. The bundle status also updates: when completed hours reach or exceed the total hours, the bundle is automatically marked **completed**.

For example, if you add three 60-minute sessions to a 10-hour bundle, the bundle will show 3 of 10 hours completed (30%).

## Deleting sessions

You can delete any individual session from the session list inside a bundle. Deleting a completed session reduces the bundle's completed hours accordingly.

<Warning>
  Deleting a session cannot be undone. If you delete a session by mistake, you will need to re-add it manually.
</Warning>

## Session visibility

Session history is visible to both the **Bundle Manager** and any **Guest** who has an active invite link for that bundle. Guests see the same session list, including dates, durations, and statuses.