> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/connect-and-administer/account-and-team/understand-single-sign-on-and-partner-accounts.md). # Understand single sign-on and partner accounts Learn how company single sign-on and white-label partner accounts work in Podigee, and how to get them. Podigee has two account structures for larger customers: single sign-on (SSO) with the identity provider of your company, and white-label partner platforms. Podigee sets up both structures for you. This page explains what they do. Neither has a self-service setup in the app. ## Single sign-on with your company identity provider Every Podigee user can sign in with an email address and password, or with a Google, Apple, or Microsoft account. Companies that manage their staff in an identity provider with Security Assertion Markup Language (SAML) 2.0 support can add a third option. Their employees sign in with the corporate account. ### How it works * Podigee registers the identity provider of your company together with the email domains of your staff. Podigee does this for you. You cannot register a provider in the app. * An employee opens the identity provider sign-in page of Podigee, enters the work email address, and selects **Log in**. Podigee finds the identity provider by the email domain and sends the person to the company sign-in. * After the company sign-in, Podigee signs the person in. The first sign-in creates the Podigee account with the name and the email address from the identity provider. Podigee verifies the account at once. * An account that signs in through the company identity provider cannot also sign in with a Google or Microsoft account. ### What to expect * The sign-in page of Podigee has no button for the company sign-in. The identity provider sign-in page has its own address. Ask Podigee for the address when your provider is registered. * An email domain that is not registered shows the message **No IDP present for this user**. IDP stands for identity provider. * Single sign-on decides how people sign in. It does not decide what they can do. Podcast access still comes from the organization membership, roles, and permissions. See [Set organization roles and permissions](/documentation/connect-and-administer/account-and-team/set-organization-roles-and-permissions.md). To get single sign-on, contact Podigee Sales. ## White-label partner accounts A white-label partner runs Podigee under its own brand for its own customers. Podigee creates the partner platform. There is no self-service setup. ### How it works * Partner administrators see the entry **Accounts** in the user menu. * The **Producer accounts** tab lists the producers. **Producers can create and manage podcasts** on the partner platform. The partner invites a producer by email with **Invite producer**. * The **Managers** tab lists the **People who can manage the whitelabel platform**. The partner invites a manager with **Invite manager**. * An invited person receives the email **Invitation for joining the podcasting platform of \[partner name]** and creates the account on the partner platform. * A producer account gets the plan that the partner defined for its platform. ### What to expect * Producers manage their own podcasts and episodes like any Podigee user. * Password reset links for producers point to the partner platform, not to the Podigee app. * Partner administrators can invite editors to the podcasts of the platform. To become a white-label partner, contact Podigee Sales. ## Related tasks * [Invite and manage organization members](/documentation/connect-and-administer/account-and-team/invite-and-manage-organization-members.md) * [Manage your account settings](/documentation/connect-and-administer/account-and-team/manage-your-account-settings.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/connect-and-administer/account-and-team/understand-single-sign-on-and-partner-accounts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.