> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/collections/manage-user-group-visibility.md).
# Manage user group visibility
How to manage visibility of a collection for user groups and set items locked
Once a collection has been created you need to set which user groups should be able to view and open it
{% content-ref url="/pages/lfVDshVPz4s4mhXd8EeX" %}
[Creating groups](/docs/users-and-groups/creating-groups.md)
{% endcontent-ref %}
Open the collection in question and use the submenu to go to **User groups**. From here you'll see an overview of all the groups that have access already, you can revoke access from here as well as add new user groups to the collection.
You can also go via the user group to see what content each group has access to
{% content-ref url="/pages/9y2EjzNCUlF8ZfGDPJZg" %}
[User information](/docs/users-and-groups/user-information.md)
{% endcontent-ref %}
Access can be prevented on each item, items that do not have 'Allow access' enabled will show to users as 'Coming soon'. For quizzes, this will also prevent users from adding that quiz to their study.
You can make quizzes available but prevent users from adding them to their study using the 'Enable add to study' toggle. If its not set, but allow access is, users will be able to take the quiz in the collection but not add it to their study.
These settings are found by clicking the pencil icon on the collection item and scrolling to the bottom of the collection item menu.
---
# 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://synap.ac/docs/collections/manage-user-group-visibility.md?ask=&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.
