---
title: "Plan for automation before requiring organization SSO | Proofline Help"
description: "Requiring single sign-on changes how API clients can authenticate. Inventory the organization's automation before enabling enforcement to avoid interrupting jobs that depend on nonhuman credentials."
url: https://proofline.sh/help/plan-for-automation-before-requiring-organization-sso/
---

[Help center](/help/)

# Plan for automation before requiring organization SSO

Requiring single sign-on changes how API clients can authenticate. Inventory the organization's automation before enabling enforcement to avoid interrupting jobs that depend on nonhuman credentials.

## Check the affected credential types

Open **Settings → API tokens → Tokens** and identify jobs using organization tokens or service account keys. Those credentials stop working while single sign-on is required. Personal API, CLI and MCP credentials need a current identity-provider sign-in for their owner.

GitHub pull request comments, checks and CI jobs are unaffected by this sign-in requirement itself. Once the credential impact is understood, the GitHub owner can test and enable enforcement under **Settings → Organization → Single sign-on**.

## Related guides

-   [Deprovision people with directory sync (SCIM)](/help/directory-sync/)
