> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/organization-administration/per-feature-configuration.md).

# Per feature configuration

Some features have configuration options in addition to an availability switch. Use these options to adjust the feature’s behavior for your organization.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FULHnY96EGqnebfKG9YHX%2FG092.mp4?alt=media&token=cb0d35fc-aae0-4be9-a7a3-7fabd0d837e8>" %}

## Before you start

Identify the specific behavior you need to change and the affected users before opening the options. Use [Feature Access catalog controls](https://docs.stackai.com/guides-and-quickstarts/organization-administration/feature-access-catalog-controls.md) for availability switches. Configuration settings can change behavior even while a feature remains available; read the individual option description and plan a check in the affected product area.

You need permission to manage organization feature settings.

## Find the configuration options

In Feature Access, open the appropriate category and select the feature.

![Feature Access category and feature details](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/yErEIhbMBJTckXCUdggU/assets/g092-g092-01-catalog.png)

Use the feature name to locate the behavior you want to configure.

Open Configuration Options and read the description and current state.

![Feature Configuration Options](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/njDQggM4bbsCaGNFpA56/assets/g092-g092-02-detail.png)

The available fields and their effects vary by feature.

## Change and verify an option

Change the required option and confirm the displayed state.

![Changed configuration option](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/3UmHAT1IleiqhIwHPrZI/assets/g092-g092-03-enabled.png)

Review its scope before applying a setting that affects other users.

Open the relevant product area and inspect the affected behavior.

![Affected product area](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/KmPSRZzfjnNmWJQVb2cO/assets/g092-g092-04-surface.png)

For a navigation setting, check the actual tab or control whose visibility changes.

Review the final setting and revisit the affected area.

![Saved setting and affected control](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/LFNkZFRg9YRr0kmj0mc9/assets/g092-g092-05-restore.png)

Confirm that its behavior matches the organization's intended configuration.

## Review consequential changes

Read any confirmation shown for a consequential feature change.

![Consequential feature-change confirmation](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Wk5BTBvyserzfnie7w9N/assets/g092-g092-06-confirmation.png)

Cancel if the described security or access effect is not the change you intend.

## Important behavior

Options differ by feature. Read the description and scope before changing a setting for the organization.


---

# 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.stackai.com/guides-and-quickstarts/organization-administration/per-feature-configuration.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.
