# GitBook

[GitBook documentation can be found here.](https://docs.gitbook.com/account-management/sso-and-saml)

You must be an **organization admin** to enable SSO for your GitBook organization.

1. Sign in to your **GitBook console**.
2. In the GitBook console, click **Settings** (In the sidebar) and then **Organization settings**.
3. In the **Organization Settings**, click **SSO** (In the sidebar).
4. Click the **Register Identity Provider** button
5. Enter **Key9 Identity** into the **Which identity provider are you connecting to?** field and click **Next**.
6. Copy and paste the URLs from your GitBook to Key9 **Setup Items**:
   1. **ACS URL**
   2. **Entity ID**
7. You can map the **Parameters**, in Key9, now or later
8. Click the **Create Application** in **Key9**.

After you have created your Key9 application, click the **SSO** tab in the side navigation, and copy the following information to GitBook:

1. Copy the Key9 **ACS (Consumer) URL** url to the **Identity provider single sign-on URL** field.
2. Copy the Key9 **Audience (Metadata)** url to the **Identity provider issuer (entityID)** field.
3. Upload the Key9 **X.509 Certificate** to the **X.509 Certificate** field.

(To view and download the x509 certificate in Key9, select **View Certificate Details** from the **Certificate Options** dropdown menu, then click the download icon.)

Click the **Save and Enable** button in GitBook

\-------------------

By default, applications are not active upon creation. Active applications are immediately available to assign groups. Applications should only be activated when you have configured the Service Provider (SP).


---

# Agent Instructions: 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:

```
GET https://docs.k9.io/key9-identity/web/marketplace/gitbook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.