Deployment tokens are JSON Web Tokens (JWT) that restrict access to deployments at a user level. When authentication is enabled, users need their deployment token in order to access the inference service URL. When authentication is not enabled, users can access the inference service URL without a deployment token. Tokens are managed via the UI or CLI.

Deployment tokens control access to the inference service endpoint when authentication is enabled for a deployment. They are ideal for production environments due to their controlled access. Deployment tokens can be created and managed via the CLI or UI and can have a set expiration date and time.

Model tokens authenticate and interact with all inference services deployed by a specific model. They are particularly useful during development, as they remain valid with the packaged model even when deployments are created or deleted. Model tokens are generated via the CLI using aioli model token <MODEL_NAME> and do not expire. To learn how to create a model token, visit Interact with a deployment.

The following table outlines roles and their corresponding permissions for creating and managing deployment tokens.

Role	Description
Admin	Create, view, and manage deployment tokens for any user.
Maintainer	Create, view, and manage their own deployment tokens.
Viewer or Robot	View their own deployment tokens.