# Enable AIP features
[Palantir AIP (Artificial Intelligence Platform)](../../platform-overview/aip-capabilities/index.md) is enabled by default in new enrollments. Enrollments that began prior to 2024 may need to manually turn on access to AIP features in [Control Panel](../../administration/control-panel/index.md). Your AIP configuration can be managed in **Control Panel > AIP settings** if you are an enrollment administrator.
Enabling AIP may [incur additional compute usage.](../aip-compute-usage/index.md)
[Review the list of supported models.](../supported-llms/index.md)
## AIP and capabilities for custom workflows
AIP's AI functionality can be divided into three categories:
* **AIP Assist:** An LLM-powered support tool designed to help users navigate, understand, and generate value with the Palantir platform. Users can ask AIP Assist questions in natural language and receive real-time help with their queries.
* **AIP assistant features in platform applications:** Native LLM-backed features designed to help end users perform regular workflows in the Palantir platform. These are highly-specific features that leverage knowledge of the platform to accelerate a user's day-to-day operations.
* **AIP capabilities for custom workflows:** A set of capabilities that allow developers to build their own LLM-backed workflows or applications. These are open-ended functionalities built for developers or data scientists.
## AIP permissions
AIP usage on the Palantir platform is governed by two levels of permissions:
* **[AIP and core assistant features](../aip-features/index.md):** Turns on AIP, [AIP Assist](../../assist/overview/index.md), and associated assistant features in [Code Repositories](../../code-repositories/aip-features/index.md), [Pipeline Builder](../../pipeline-builder/pipeline-builder-aip/index.md), and Workshop.
* **AIP capabilities for custom workflows:** With AIP enabled, platform administrators can enable an additional layer of capabilities to empower developers and application builders to create custom AIP workflows and grant users the necessary permissions to use these custom AIP workflows. The capabilities that are unlocked when permission is granted are as follows:
* **Capabilities with LLM support in point-and-click interfaces**
* [AIP Logic: Use LLM Board](../../logic/getting-started/index.md#getting-started)
* [Pipeline Builder: Use LLM node](../../pipeline-builder/pipeline-builder-llm/index.md) and [Text-to-embeddings](../../pipeline-builder/pipeline-builder-aip/index.md#text-to-embeddings)
* [AIP Automate](../../logic/aip-logic-integration-automate/index.md)
* [AIP Model Catalog](../../model-catalog/overview/index.md)
* [AIP Chatbot Studio](../../chatbot-studio/overview/index.md) (formerly AIP Agent Studio)
* AIP Workshop widgets: [AIP Chatbot](../../workshop/widgets-aip-chatbot/index.md), [AIP Generated Content](../../workshop/widgets-aip-generated-content/index.md)
* [AIP Workshop translations](../../workshop/translations/index.md#automatic-translation-with-aip)
* [Quiver](../../quiver/quiver-aip/index.md)
* [AIP Threads](../../threads/overview/index.md)
* **Capabilities for development with code-based tools**
* [Transforms using LLMs](../../transforms-python-spark/palantir-provided-models/index.md)
* [Functions using LLMs](../../functions/language-models-python-tsv2/index.md)
* [Jupyter® in Code Workspaces with LLMs](../../code-workspaces/overview/index.md)
## Restrict AIP usage
Platform administrators can restrict AIP usage on two different levels; user groups and Organizations.
### User groups
To restrict AIP usage on user groups, platform administrators can select **Everyone**, given **User Groups**, or restrict usage by selecting **Nobody**.
Certain applications, such as AIP Logic, may need to first be enabled in **Control Panel > Application access** before they can be used.
### Organizations
To restrict AIP on Organizations, platform administrators can enable the **Restrict AIP To Organizations** option and select the desired Organizations from the dropdown. Keep in mind that this setting *restricts* AIP to the selected Organizations. As a result, AIP will be disabled for any Organizations that are not selected. Additionally, if AIP is not enabled for an enrollment, no Organizations will have access to AIP.
:::callout{theme="neutral"}
AIP is only considered enabled for a resource when AIP is enabled for **all** organization markings on the resource's project.
:::
## Enable LLMs
Enrollment administrators manage LLM usage under the **Model enablement** tab within the **AIP settings** extension of Control Panel. Enabling a model family includes accepting the applicable terms and conditions, including terms for the subprocessors that provide the models.
Enrollment administrators can also [control LLM data access with mandatory Markings](../control-llm-data-access-with-markings/index.md) in Control Panel.
### Understanding model states
Each model family in the Model enablement interface displays one of three states:
* **Enabled:** The model family is active and available for use by users and workflows. No further action is required.
* **Disabled:** The model family is available on your enrollment but has not been activated by administrators. To enable it, select **Manage** and accept the terms and conditions.
* **Disallowed:** The model family is restricted due to legal, geographical, or infrastructure constraints. Contact Palantir Support to discuss availability options.
Before initially enabling models from a subprocessor, an enrollment administrator must accept the applicable terms and conditions. Model families in a **disabled** state can be enabled directly through Control Panel, while **disallowed** models require manual configuration by Palantir Support before they can be used.
When a subprocessor is enabled, Palantir may enable additional model families that meet the eligibility requirements under the accepted terms and conditions. Enabling additional model families does not incur additional costs. A new subprocessor requires separate administrator acceptance. Enrollment administrators can review and disable model families in Control Panel.
Disabling a model family group will break workflows that rely on a model in that specific group.
[View a list of all supported models.](../supported-llms/index.md#available-llms)
[Learn how to bring your own model to run on the Palantir platform.](../bring-your-own-model/index.md)
Additionally, enrollment administrators can enable or disable model families at the organization level, allowing certain organizations within the same enrollment to access specific model families while restricting others.
In the example below, only the `Test1` organization in this enrollment has access to Amazon Bedrock Claude models.
### Experimental models
Usage of experimental models can be enabled and disabled by enrollment administrators. For an experimental model to be visible for use in workflows, the **Enable experimental models** toggle must be enabled as well as the [model family](#enable-llms) to which the experimental model belongs.
## Learn more
* [Available LLMs](../supported-llms/index.md#available-llms)
* [LLM availability prerequisites](../supported-llms/index.md#llm-availability-prerequisites)
* [LLM capacity management](../llm-capacity-management/index.md)
* [Georestriction of model availability](../supported-llms/index.md#llm-availability-by-geography)
***
Note: AIP feature availability is subject to change and may differ between customers.
*The "OpenAI" name and the “GPT” brands are property of OpenAI.*
*Jupyter®, JupyterLab®, and the Jupyter® logos are trademarks or registered trademarks of NumFOCUS.*
All third-party trademarks (including logos and icons) referenced remain the property of their respective owners. No affiliation or endorsement is implied.