Skip to main content

Configure your organization to use apps

An organization admin must complete the steps in the following sections to make sure their organization is ready to use the AI app builder.

Configure self-hosted instance

The new app builder was first released to self-hosted instances on version 4.0 stable and is available on all subsequent versions.

  • For new deployments: Retool recommends using a Terraform blueprint to automatically provision all required infrastructure (VPC, EKS cluster, RDS, S3, load balancer, ACM certificate) and deploy Retool via Helm.
  • For existing deployments: Upgrade to version 4.0. New services are disabled by default, so you can upgrade the Helm chart first and enable them when ready. Some deployment configurations require migration before upgrading.

Enable the app builder

To ensure that builders in your organization can build apps, navigate to Settings > AI. Toggle on the Updated App Builder.

Configure access to the app builder

Organization admins on the Business and Enterprise plans can use Retool's role-based access controls to configure access to the app builder.

By default, when Updated App Builder is enabled, all users are added to a role that gives them access to the app builder. Admins can update this role to restrict access to a particular group or individual using the following steps:

  1. Navigate to Settings > Roles.
  2. Select the App Builder Role. This role was created for you automatically, and includes the Build apps in the AI-powered app builder permission. You can add or edit permissions here as necessary.
  3. Switch to the Assignment tab. The role was automatically assigned to the All Users group. To restrict access, remove the All Users group and click Add group assignment to provide access ot another user group or individual user.
  4. Click Save changes.

You can also create new roles or update existing roles in order to grant Build apps in the AI-powered app builder permission to different groups of users.

Configure AI resources

Organization admins must configure one or more AI resources before builders can write prompts to create or edit apps. The following list outlines the key points of what Retool supports for AI app building:

note

Custom AI providers are not supported in apps. Use one of the dedicated provider resources instead.

The following diagram outlines your different options for configuring AI resources.

Loading diagram...

Configure resource permissions

For users to be able to prompt AI to create apps using the AI resources you set up, they need Use access to each resource.

Add all builders to an existing or new permission group, and configure the permission group to have Use access to each relevant AI resource.

(Optional) Configure AI proxy

important

The following section is required only if you bring your own key and utilize an AI proxy service.

Configure a proxy

If you use a proxy to make calls to LLM providers (such as LiteLLM or LLM Proxy Server), you must configure the proxy to support models that you want to be available to your builders.

  1. In your proxy, configure the LLM provider that you want builders to be able to use.
  2. Ensure the proxy is configured to support each model that you want builders to be able to use.
  3. In Retool, navigate to the Resources page and open the resource corresponding to your model provider. Update the Base URL setting to point to your proxy endpoint. Repeat for any additional model providers.

Set preferred AI resource and model

Once you configure the supported AI resources that are available for building apps, you can configure your preferred resource and model. While builders have the ability to choose from any of the providers you configured, your selection will be the default for new threads.

  1. Navigate to Settings > AI.
  2. In the Apps section, configure the Preferred resource and Preferred model.
note

If you choose not to select a preferred resource or model, Retool automatically uses the latest Anthropic Claude Opus model.

Configure firewall

If your organization makes use of firewall rules, you must include retool.app in its allowlist. This allows your deployment to connect to Retool's user authentication and usage reporting services.

This step is required because published apps are served at retool.app, using the following URL structure: <orgSubdomain>--<app-name-slug>.retool.app. For example, an example app URL could be exampleOrg--overtime-requests.retool.app.

Configure environment variables for Retool-managed keys

important

The following section is required only if you use Retool-managed keys.

To enable AI app building on self-hosted deployments using a Retool-managed key, set the following environment variables.

Environment variableValue
LICENSE_KEYYour self-hosted Retool license key.
OPENAI_PROXY_HOSTSet to https://ai-proxy.retool.com.
OPENAI_PROXY_API_TOKENContact your Retool account manager (or support@retool.com if you don't have an account manager) to generate a Retool-provided token.
OPENAI_SECRET_KEYSet to an empty string.
note

For OPENAI_PROXY_API_TOKEN, contact your Retool account manager (or support@retool.com if you don't have an account manager) to generate a Retool-provided token. Keys provided by Retool are subject to restrictive rate limits and are not suitable for production use cases. If the rate limiting is an issue, bring your own key and set it from the Settings > AI resource page.

While this environment variable includes OPENAI in the title, you can use it for any available provider.

Track AI credit usage

Retool's AI-powered features use organization-level monthly AI credits. Your organization's plan determines how many credits you receive each month. Credits renew on the first day of your plan’s billing cycle and do not roll over.

Organization admins can monitor AI credit usage in Settings > Plans & Billing under the AI Credits tab. Select Usage to view credit consumption over time, broken down by product.

For more information about usage and billing, refer to the AI credits documentation.