> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-iam.md). # IAM Manage accounts and access in your identity provider from Siit.
:google: Connect Google WorkspaceConnect Google Admin to Siit, review default and optional scopes, and enable Google Workspace actions such as group changes, password reset, suspend user and clear sessionsConnect Google Workspace
:windows: Connect Microsoft Entra IDConnect Microsoft Entra ID to Siit with your tenant ID to import employee data for onboarding and offboarding; app discovery from SSO sign-ins needs an Entra P1 or P2 licenceConnect Microsoft Entra ID
:user-pen: Use Microsoft Entra ID actionsRun Microsoft Entra ID actions such as group changes, suspend user or password reset from requests, workflows and AI agents, with permissions, examples and troubleshootingUse Microsoft Entra ID actions
:octagon: Connect OktaInstall the Siit API Service from the Okta marketplace and add its client ID and secret in Siit to run Okta actions like suspend user, reset MFA or update groups from requestsConnect Okta
:j: Connect JumpCloudConnect JumpCloud to Siit to run actions from a request: activate or suspend users, reset passwords and MFA, update groups, and send recovery keys privatelyConnect JumpCloud
:unlock: Recover a locked-out userSend locked-out employees a temporary password, access code or recovery key privately via JumpCloud, Google, Entra ID, Okta, Jamf, Iru or Intune actions, logged on the requestRecover a locked-out user
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/integrations/integrations-iam.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.