> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/feature-experimentation-settings.md).
# Feature Experimentation Settings
Access your Feature Experimentation and Rollout settings
Set up environment and team settings for your feature experimentation and rollout campaigns.
### Manage teams
Create and manage teams to assign folder permissions to groups of users.
{% stepper %}
{% step %}
#### Access teams settings
Go to **Feature Experimentation** > **Teams**.
{% endstep %}
{% step %}
#### Create new team
Click **Create a team** to open the team creation dialog.
{% endstep %}
{% step %}
#### Configure team details
Enter a **Team name** and search for users to add to the team in the **Add a user** field.
{% endstep %}
{% step %}
#### Assign folder permissions
After creating the team, assign it to folders with specific permission levels (Viewer, Editor, Admin).
{% endstep %}
{% step %}
#### Save team configuration
Click **Create** to save the team, then **Assign** to apply folder permissions.
{% endstep %}
{% endstepper %}
###
---
# 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.abtasty.com/feature-experimentation-and-rollout/feature-experimentation-settings.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.
