> ## Documentation Index
> Fetch the complete documentation index at: https://fal.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Access and availability

> Enable fal Assets, choose the right account, and understand team permissions and enterprise access.

## Enable Assets

Sign in at [fal.ai/assets](https://fal.ai/assets). If Assets is available but not yet enabled, review the terms. Select the agreement checkbox. Choose **Enable fal Assets**.

Enabling Assets allows your generations to be saved and organized, reused on supported fal surfaces, and processed for semantic search. A role with read-only access cannot enable or modify the library.

## Personal and team libraries

Assets uses the currently selected account. Switch accounts to move between your personal library and a team's library. A file in one account does not automatically appear in another account's library.

If expected media is missing, check the account before uploading it again.

## Permissions

Your role determines whether you can browse the library, upload media, edit entities and collections, or delete assets. Request-payload permissions also affect whether you can inspect prompts and generation details.

If you can view an asset but cannot edit it, ask an account administrator to check your role. See [Teams](/docs/documentation/setting-up/teams) for account membership.

## Organization and enterprise access

An organization can disable Assets for its teams. If the page says Assets is disabled for the organization, an organization administrator must enable it.

Enterprise accounts that have not enabled Assets must contact [support@fal.ai](mailto:support@fal.ai) to discuss access. Enabling Assets on another account does not override an organization's policy.

## Which generations appear

The request sources included in Assets depend on your account's configuration. Access to the library does not by itself mean every API request is included. If browser generations appear but API generations do not, check the account's configuration with your administrator or support.

## Features with separate requirements

* **Agent reuse** requires [fal Agent access](/docs/documentation/agent/access-and-pricing).
* **New model generations** require the model's normal access and credits.
* **Collection sharing** is available only for eligible independent self-service personal accounts. See [Sharing collections](/docs/documentation/assets/sharing).
* **Programmatic access** requires an API key for an account with Assets enabled. See [Using the Assets API](/docs/documentation/assets/api).