Configure an App

Open an app and use its Configure sections to connect the resources it needs. Each section only appears when it is relevant to the app or already has configured data.

Access and members

Use Members to share an app with people in the Airlock tenant. Use Access to control which app capabilities are available to administrators, members, or the public.

Tenant roles govern platform-wide actions. App membership governs what each person can do with a particular app.

Credentials and integrations

Use Connections for configured credentials and external services. Use MCP Servers to connect remote MCP capabilities, and Environment for app-specific environment values.

Credentials remain in Airlock’s encrypted storage. App containers receive only the bindings they need.

Triggers and routes

Use Webhooks for verified inbound HTTP events and Schedules for recurring or one-time work. Use Routes for custom app HTTP endpoints on the app subdomain.

Use Siblings when an app should call capabilities exposed by another Airlock app.

Runtime capabilities

Use Tools to inspect the capabilities the app registers for AI use. Use Models to override the platform model defaults for this app. Use Exec Endpoints when the app needs to run commands on a registered remote endpoint.

Configuration actions follow the app’s access rules and are recorded in its activity history.