> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/structural-user-access/single-sign-on/sso-view-groups-list.md).

# Viewing the list of SSO groups in Tonic Structural

{% hint style="info" %}
**Required license:** Professional or Enterprise

**Required global permission:** Manage user access to Tonic Structural and to any workspace
{% endhint %}

If you use SSO to manage Tonic Structural groups, then Structural displays the list of groups for which at least one user has logged in to Structural.

To display the SSO group list:

1. In the Structural heading, click **Structural Settings**.
2. On **Structural Settings** view, click **Access Management**.
3. On the **Access Management** tab, click **Groups**.

If no users from a group have logged in to Structural, then the group does not display in the list.

The list only displays the group names. To manage the group permissions:

* To [assign global permission sets](/app/structural-user-access/permissions/global-permissions/global-permission-set-access.md), go to the **Global Permission Sets** tab.
* To [assign team permission sets](/app/structural-user-access/permissions/team-permissions/configuring-access-to-team-permission-sets.md), go the **Team Permission Sets** tab on **Team Settings** view.
* To [assign workspace permission sets](/app/workspace/workspace-access-management/workspace-sharing.md), go to **Workspaces** view.


---

# 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.tonic.ai/app/structural-user-access/single-sign-on/sso-view-groups-list.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.