Account management
Last updated: Apr-20-2026
There are several ways to manage the usage and behavior of your Cloudinary account.
Some of these options determine behavior across your entire account, and others are specific to each product environment in your account.
Console settings
From the Cloudinary Console Settings pages, you can define a variety of options, some of which apply to the currently active product environment, and should be set for each product environment separately, and other configurations that apply to the entire account.
Account settings
From the Account settings, you can manage your plan, product environments, user and group definitions, and account security information. That section also includes the My Profile page where each individual user can set personal account details, as well as display preferences that apply for all product environments they can access in the account.
Other account-level settings
From the Billing page, you can view your plan details, upgrade your plan, and manage account information, billing address, and invoice settings. From the Add-ons page, you can register for features that offer unique transformation and customization, optimization and delivery, or asset management and analysis capabilities.
Product environment settings
From the Product environment settings, you can manage settings specific to the current product environment, including API keys, upload behavior, backup, optimization, webhook notifications, security, and more.
User provisioning
If your account has multiple users, you can use user roles to control access and permissions within the Console in line with your data and asset governance policy.
You can provision and configure users and groups manually in the Console, programmatically via the Provisioning API, or using your organization's SAML-based SSO IdP.
The user who creates a Cloudinary account is automatically a root user, with full permissions across all product environments. You can then grant roles to other users based on their responsibilities and required access level. The roles available depend on your permissions system. See Roles and Permissions vs. legacy for a comparison.
Developers usually get the Admin or Tech Admin system roles (Roles and Permissions) or Admin or Technical admin roles (legacy), which provide access to API keys and other developer resources. Additional roles are available for billing, reporting, Assets users, and Assets administrators.