> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/platform-administration/administration/identity-provider-integration/integration-of-idp-groups-with-digibee-groups/how-to-test-a-group-integration.md).

# How to test a group integration

Learn how to test a group integration.

Follow these steps to test a group integration:

1. Go to the **Administration** page.
2. Click on **Groups**.
3. Click on the **Group Integrations** tab.
4. Search the table for the group integration you want to test, or use the search bar.
5. Click on the **Test integration** icon.
6. Enter an email from a user who belongs to the IdP group you want to test.
7. Click on **Test**.

A URL will be displayed on your screen.

1. Open a new anonymous window.
2. On the anonymous window, paste the URL to be redirected to your realm’s login page.
3. Using the anonymous window, log in to the Digibee Integration Platform with your IdP, using the email you entered in step 6.

The **test status** column will change according to the results of this test. You can learn more about group integrations and test statuses by reading the article Integration of IdP groups with Digibee groups.


---

# 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.digibee.com/documentation/platform-administration/administration/identity-provider-integration/integration-of-idp-groups-with-digibee-groups/how-to-test-a-group-integration.md?ask=<question>&goal=<user_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.