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

# Overview

AccessOwl provides seamless integrations for **over 300 applications**, offering various integration types and categories to simplify access management and automate workflows. This documentation outlines the three primary integration types, capabilties and categories.

<Card title="View all of AccessOwl's integrations" icon="sparkles" href="https://www.accessowl.com/integrations" horizontal />

## Integration Types

<Tabs>
  <Tab title="AccessOwl Agentic Integrations">
    Designed to bypass the high cost or unavailability of SCIM/SAML [("SSO Tax")](https://ssotax.org), these integrations work by adding a service account to each SaaS application. AccessOwl utilizes RPA, screen scraping, private APIs, and AI to automate provisioning, deprovisioning, and user list syncing. Over 300 applications are supported, and new integrations can typically be delivered within 7–14 days.
  </Tab>

  <Tab title="SCIM/SAML via Okta">
    For organizations already leveraging Okta, AccessOwl can assign users to Okta app groups based on AccessOwl access requests. Okta’s SCIM or SAML integrations then handle user account provisioning in connected apps. See [Okta-managed applications](/integrations/all/okta/okta-managed-apps) for setup steps.
  </Tab>

  <Tab title="Direct API">
    Ideal for applications with complex permission structures or readily available APIs (such as GitHub), this method allows AccessOwl to connect directly to the app’s API for provisioning, deprovisioning, and other access-management tasks.
  </Tab>
</Tabs>

***

## Integration Categories

<Tabs>
  <Tab title="HRIS">
    AccessOwl connects to HR tools such as BambooHR, HiBob, and Personio to streamline employee onboarding and offboarding workflows. It extracts essential user and manager details from your HR system, identifies new hires and terminations, and triggers automated onboarding and offboarding processes to save time and reduce errors.
  </Tab>

  <Tab title="Directories">
    AccessOwl integrates with directories like Google Workspace, Microsoft, and Okta to provide a unified source of truth for user management. By centralizing directory data, it simplifies access governance and ensures consistency across platforms, enabling streamlined and efficient management of users and permissions.
  </Tab>

  <Tab title="Regular SaaS Applications">
    AccessOwl connects with popular SaaS tools to automate the provisioning and deprovisioning of user accounts. This integration supports a wide range of applications across various industries, improving compliance and security while ensuring accurate and up-to-date user access management.
  </Tab>
</Tabs>

***

## Capabilities

<CardGroup cols={2}>
  <Card title="Structure Sync" icon="diagram-project">
    AccessOwl periodically syncs the permissions schema of an application.
  </Card>

  <Card title="User Sync" icon="arrows-rotate">
    AccessOwl periodically syncs a list of users along with their assigned permissions.
  </Card>

  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates or removes user accounts with the specified permissions during access requests or revocations.
  </Card>

  <Card title="Directory Sync" icon="folder-open">
    AccessOwl syncs (creates, removes, or deactivates) users from directories like Slack, Microsoft365, Okta, or Google into the AccessOwl users database.
  </Card>

  <Card title="Access Review Evidence" icon="file-signature">
    AccessOwl uploads access control evidence to compliance vendors such as Vanta.
  </Card>

  <Card title="HRIS Sync" icon="briefcase">
    AccessOwl integrates with HRIS platforms to automate employee onboarding and offboarding. It also syncs all employees to AccessOwl, including details such as their title, department, and manager.
  </Card>
</CardGroup>

***

## Reliability

AccessOwl integrations are designed to fail loud, not silent. Three principles back this up:

<CardGroup cols={3}>
  <Card title="Stable surface" icon="shield-check">
    User management UI is the most stable surface of any SaaS app and rarely changes compared to the main product. This is where AccessOwl operates.
  </Card>

  <Card title="Never fails silently" icon="bell">
    When an integration can't complete an action (for example the app is out of licenses, hits an unexpected prompt, or the workspace is deactivated), AccessOwl automatically reassigns the request to the application admin so nothing slips through.
  </Card>

  <Card title="We maintain it" icon="wrench">
    AccessOwl monitors integration health and our team patches the connector when an upstream UI or login flow changes. Customers never write or repair scripts. UI-change incidents are typically resolved within hours and communicated proactively.
  </Card>
</CardGroup>