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

# My Tickets tab

> Open your Ravenna tickets inside Microsoft Teams with the embedded My Tickets personal tab, signed in automatically with Microsoft Entra single sign-on.

The Ravenna app for Microsoft Teams includes a **My Tickets** personal tab that embeds the Ravenna web app inside Teams. Open it to see the tickets you've requested, are assigned to, or are following, without leaving Teams.

<View title="Human" icon="user">
  ## Open the tab

  <Steps>
    <Step title="Open the Ravenna app">
      Click the Ravenna icon in the Teams left rail. If you don't see it, pin the app from **Apps > Built for your org** or search for **Ravenna**.
    </Step>

    <Step title="Open My Tickets">
      Select the **My Tickets** tab inside the Ravenna app. Ravenna signs you in automatically using your Microsoft Entra (Azure AD) identity, with no second login.
    </Step>

    <Step title="Work the same as the web app">
      The embedded view is the same Ravenna interface you use in the browser. Open a ticket, comment, change status, or assign it directly inside Teams.
    </Step>
  </Steps>

  <Info>
    The tab signs you in with Microsoft Entra single sign-on, so you only see tickets that your Ravenna user can see. If your Teams account doesn't match a provisioned Ravenna user, Ravenna provisions you on the fly the first time you open the tab.
  </Info>
</View>

<View title="Agent" icon="bot">
  ## Mental model

  The My Tickets tab is a Teams `staticTab` declared in the Ravenna app manifest. It loads a route in the Ravenna web app inside the Teams web view, scoped to the signed-in user.

  Authentication uses **Microsoft Entra SSO via the Teams JS SDK**:

  * The web app requests an SSO token from Teams using the Ravenna app's Entra app registration.
  * The token is exchanged on the Ravenna API for a Ravenna session cookie. The exchange resolves the Microsoft Entra `oid` to a Ravenna user (provisioning a new one if needed via the standard Graph user-sync path).
  * All subsequent requests use the Ravenna session, so the tab inherits the user's existing Ravenna permissions.

  ***

  ## Provisioning behavior

  If the signed-in Microsoft Entra user has no matching Ravenna user yet:

  * A new Ravenna user is created from Microsoft Graph using the standard `UserSyncMixin` resolver.
  * The user is provisioned as a **Member** if their email matches a verified organization domain, otherwise as a **Guest**.
  * The Ravenna session is issued for the newly-created user and the tab loads immediately.

  This matches the just-in-time provisioning behavior of the rest of the Teams integration.

  ***

  ## Constraints and gotchas

  * The tab requires the Ravenna Teams app to be installed for the user. Org admins can pin the app for all users via a Teams app setup policy.
  * SSO requires the Ravenna Entra app to be admin-consented in the tenant. This is granted as part of the initial [setup](/integrations/microsoft-teams/setup) flow.
  * The tab loads the full Ravenna web app. Feature parity, theming, and shortcuts are identical to the browser experience.
</View>