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

# SSO Discovery

> Connect your identity provider and your agent discovers every app your team accesses — instantly.

# SSO Discovery

Connect your identity provider and your agent maps every application your team accesses — who's using what, how often, and what's flying under the radar.

## Why Connect SSO?

<CardGroup cols={2}>
  <Card title="Complete Discovery" icon="magnifying-glass">
    Find every app your team accesses via SSO
  </Card>

  <Card title="Usage Tracking" icon="chart-line">
    See who's using which applications
  </Card>

  <Card title="Access Insights" icon="users">
    Identify unused licenses and access patterns
  </Card>

  <Card title="Shadow IT Detection" icon="eye">
    Discover apps IT didn't know about
  </Card>
</CardGroup>

## Supported Identity Providers

<Tabs>
  <Tab title="Google Workspace">
    <Card title="Connect Google Workspace" icon="google" href="/integrations/sso/google-workspace">
      Discover apps accessed via Google SSO
    </Card>

    **What we discover:**

    * All SAML and OAuth apps in your Google Workspace
    * User access patterns and login frequency
    * Application usage by team member
    * Third-party app permissions
  </Tab>

  <Tab title="Microsoft Entra">
    <Card title="Connect Microsoft Entra ID" icon="microsoft" href="/integrations/sso/microsoft-entra">
      Discover apps accessed via Azure AD / Entra ID
    </Card>

    **What we discover:**

    * All enterprise applications in Azure AD
    * User sign-in activity and frequency
    * Application usage by team member
    * Conditional access policies
  </Tab>

  <Tab title="Okta">
    <Card title="Connect Okta" icon="key" href="/integrations/sso/okta">
      Discover apps accessed via Okta SSO
    </Card>

    **What we discover:**

    * All applications in your Okta org
    * User assignments and access
    * Login frequency and patterns
    * Application usage by team member
  </Tab>
</Tabs>

## How SSO Discovery Works

```mermaid theme={null}
graph LR
    A[Connect IdP] --> B[Sync Apps]
    B --> C[Track Logins]
    C --> D[Match Vendors]
    D --> E[Dashboard]
```

<Steps>
  <Step title="Connect your identity provider">
    Authenticate with admin credentials and grant read-only access
  </Step>

  <Step title="Initial application sync">
    Porcia retrieves all SSO-enabled applications from your IdP
  </Step>

  <Step title="Login tracking">
    Monitor user login events to track actual usage (with consent)
  </Step>

  <Step title="Vendor matching">
    Match discovered apps to our global vendor database
  </Step>

  <Step title="Dashboard updates">
    View all discovered apps, usage patterns, and insights
  </Step>
</Steps>

## What We Discover

### Application Information

* **App name and logo** - Visual identification
* **Vendor details** - Company behind the app
* **Integration type** - SAML, OAuth, OIDC
* **Configuration** - SSO settings and policies

### Usage Data

* **Active users** - Who's actually using each app
* **Login frequency** - How often apps are accessed
* **Last login** - When each app was last used
* **Usage trends** - Increasing or decreasing usage

### Access Patterns

* **User assignments** - Who has access to what
* **Unused licenses** - Users with access but no usage
* **Shadow IT** - Apps added without IT approval
* **Access anomalies** - Unusual access patterns

<Info>
  All usage tracking requires user consent and can be disabled in Settings → Privacy.
</Info>

## Permissions Required

### What We Need

All SSO integrations require **read-only admin access** to:

* ✅ **Read application catalog** - List all SSO-enabled apps
* ✅ **Read user assignments** - See who has access to what
* ✅ **Read login events** - Track application usage
* ✅ **Read user directory** - Match users to team members

### What We DON'T Need

* ❌ **Modify applications** - We never change SSO configurations
* ❌ **Manage users** - We never add, remove, or modify users
* ❌ **Access credentials** - We never see passwords or tokens
* ❌ **Change permissions** - We never modify access controls

<Warning>
  SSO integration requires admin permissions on your identity provider. If you don't have admin access, ask your IT team to set this up.
</Warning>

## Multi-Provider Support

You can connect multiple identity providers simultaneously:

### Common Scenarios

**Scenario 1: Acquisition or Merger**

* Connect both Google Workspace and Microsoft Entra
* See unified view of all applications
* Identify duplicate tools across organizations

**Scenario 2: Hybrid Environment**

* Some teams use Google, others use Microsoft
* Connect both to get complete visibility
* Consolidate vendor relationships

**Scenario 3: Migration**

* Migrating from Okta to Azure AD
* Connect both during transition
* Track migration progress

<Tip>
  Porcia automatically deduplicates vendors discovered across multiple IdPs. If the same app is found in both Google and Azure AD, it appears once in your dashboard.
</Tip>

## Privacy & Security

### Data Collection

* **Application metadata** - App names, logos, vendors
* **User assignments** - Who has access (anonymized in analytics)
* **Login events** - Timestamps and frequency (no session data)
* **Usage patterns** - Aggregated usage statistics

### Data Protection

* **Encryption** - All data encrypted at rest (AES-256) and in transit (TLS 1.3)
* **Access control** - Only workspace admins can view user-level data
* **Audit logs** - Complete audit trail of all SSO sync activity
* **Token security** - OAuth tokens stored securely with encryption at rest

### Compliance

* **Data privacy** - Right to access, delete, and export data (GDPR compliance in progress)
* **User consent** - Usage tracking requires explicit user consent

<Info>
  **Security:** Porcia follows industry-standard security practices including end-to-end encryption and role-based access control. Full security documentation coming soon.
</Info>

## Comparison: Email vs SSO Discovery

| Feature         | Email Discovery        | SSO Discovery         |
| --------------- | ---------------------- | --------------------- |
| Setup time      | 2-5 minutes            | 5-10 minutes          |
| Discovery scope | Vendors you email with | Apps accessed via SSO |
| Usage tracking  | ❌ No                   | ✅ Yes                 |
| Historical data | ✅ 6 months             | ⚠️ Ongoing only       |
| Admin required  | ❌ No                   | ✅ Yes                 |
| Best for        | Vendor communications  | Application usage     |

<Tip>
  For complete visibility, use both email and SSO discovery. Email finds vendors you communicate with, SSO finds apps your team uses.
</Tip>

## Disconnecting SSO

To disconnect your identity provider:

1. Go to **Settings → Integrations → SSO**
2. Find your connected IdP
3. Click **Disconnect**
4. Confirm disconnection

<Info>
  Disconnecting will stop new application discovery and usage tracking. Historical data will be preserved unless you choose to delete it.
</Info>

## Next Steps

<CardGroup cols={3}>
  <Card title="Google Workspace" icon="google" href="/integrations/sso/google-workspace">
    Connect Google SSO
  </Card>

  <Card title="Microsoft Entra" icon="microsoft" href="/integrations/sso/microsoft-entra">
    Connect Azure AD
  </Card>

  <Card title="Okta" icon="key" href="/integrations/sso/okta">
    Connect Okta
  </Card>
</CardGroup>

## Troubleshooting

<CardGroup cols={2}>
  <Card title="Email Sync Issues" icon="envelope" href="/troubleshooting/email-sync">
    Fix email integration problems
  </Card>

  <Card title="FAQ" icon="question" href="/troubleshooting/faq">
    Common SSO questions
  </Card>

  <Card title="Google Workspace Setup" icon="google" href="/integrations/sso/google-workspace">
    Google Workspace guide
  </Card>

  <Card title="Microsoft Entra Setup" icon="microsoft" href="/integrations/sso/microsoft-entra">
    Microsoft Entra guide
  </Card>
</CardGroup>
