> 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/feature-access-catalog-controls.md).

# Feature Access catalog controls

Feature Access controls which product capabilities are available in your organization. Use it to manage providers and individual actions that your team can select.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fr62ql0iN2wT9UyoyAtfj%2FG091.mp4?alt=media&token=4843995a-d455-457b-ac1e-77e3ceb62455>" %}

## Before you start

Identify the provider or action and the business workflows that depend on it. You need permission to manage organization feature access. Coordinate a restrictive change with the affected workflow owners; the effect on existing runs is explained below. Use [Per feature configuration](https://docs.stackai.com/guides-and-quickstarts/organization-administration/per-feature-configuration.md) for options beyond availability.

You need permission to manage organization feature access.

## Find a feature or provider

Open Settings → Feature Access and review the categories and default controls.

![Feature Access categories and defaults](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Y6GRdlkBZT8gq1bHFwgg/assets/g091-g091-01-catalog.png)

These settings determine which product capabilities the organization makes available.

Search for the provider or feature you want to manage.

![Provider or feature search](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/qWkhXUw54dXZpyRIbqzv/assets/g091-g091-02-search.png)

Open its details to distinguish provider-wide controls from individual action settings.

Review the provider's connection type and Actions list.

![Provider connection type and Actions list](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/w3IrOeXZrQECCBXSst8H/assets/g091-g091-03-detail.png)

Read each switch label before changing availability.

## Plan the effect on existing workflows

Disabling a catalog provider or action affects more than its appearance in a picker. Workflow runs check the organization's current catalog policy, including references saved in existing workflow versions. New runs of an already-published workflow can therefore fail when they reference a disabled provider or action; a published version does not preserve an exemption from the current policy.

A provider-level restriction can block its child actions even if an individual action was previously enabled. Existing saved configuration and connection credentials are not a substitute for policy permission. Availability also does not grant access to the provider account: a valid connection and provider-side authorization are still needed.

Before a team-wide restriction, identify projects that use the provider or action and coordinate the change with their owners. For example, disabling an action used to retrieve records can stop a published assistant from completing its response. Decide whether those owners will replace the action before the restriction or accept the interruption.

After saving, check both the picker and a representative run of an affected existing workflow. Use a safe input and avoid unnecessary external writes. Inspect the actual error or response in [Inspect project analytics](https://docs.stackai.com/guides-and-quickstarts/evaluations-and-observability/inspect-project-analytics.md); a hidden picker entry alone does not verify the effect on existing projects.

If a required workflow is unexpectedly blocked, have the authorized policy owner review the provider and action states. Restore the intended availability when organizational policy permits, then rerun the affected request. If the restriction must remain, the workflow owner must remove or replace the dependency, test the changed draft, and release it. Do not treat the toggle as a credential-revocation procedure or assume it cancels a run that was already in progress.

## Set availability

Change the required provider or action setting and inspect the remaining enabled actions.

![Provider and action availability switches](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/pGiDCaJsHnZpZC1Igp1M/assets/g091-g091-04-actions.png)

Keep the configuration aligned with the operations the organization permits.

Open a workflow's node or tool picker and search for the affected provider.

![Affected provider in the workflow picker](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/HosOVATZLNz9wGsY7YvA/assets/g091-g091-05-picker.png)

Check which actions are available under the updated policy.

Return to Feature Access and review the final provider and action states together.

![Final provider and action policy states](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/uu0O3KEgfOy4wRr4a0i2/assets/g091-g091-06-restore.png)

Remove unintended changes before leaving the configuration.

## Important behavior

Making an action available does not authorize it to access a provider account. Users still need the required connection and provider permissions.


---

# 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/feature-access-catalog-controls.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.
