In the Admin Console, navigate to the Overview tab.
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage products and entitlements
- Manage users
- Administrative roles
- User management techniques
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Manage products and product profiles
- Manage products
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage users
- Manage storage and assets
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
- About Creative Cloud Packager
- Creative Cloud Packager release notes
- Application packaging
- Create packages using Creative Cloud Packager
- Create named license packages
- Create packages with device licenses
- Create a license package
- Create packages with serial number licenses
- Packager automation
- Package non-Creative Cloud products
- Edit and save configurations
- Set locale at system level
- Manage your account
- Manage your Teams account
- Assign licenses to a Teams user
- Add products and licenses
- Automated expiration stages for ETLA contracts
- Switching contract types within an existing Adobe Admin Console
- Purchase Request compliance
- Value Incentive Plan (VIP) in China
- VIP Select help
- Reports & logs
- Get help
Manage API developers on the Admin Console
Adobe I/O is the platform for developers in your organization looking to integrate, extend, or create apps and experiences based on Adobe's products and technologies. It is a platform that developers use to build on top of Creative Cloud, Document Cloud, Experience Cloud, or other Adobe API products.
Your developers on Adobe I/O, build API credentials with Adobe API products. These API credentials are a pipeline from external apps and services to the Adobe API.
- First, you add developers (individually or in bulk) to product profiles of products that include API access on the Admin Console.
This provides your developers with the permissions to create API credentials.
- Next, your developers add the required API credentials on Adobe I/O.
- Finally, you add these API credentials to product profiles again on the Admin Console.
The Developer account type is only available for a specific set of Adobe products. A Developer account can be added to the Admin Console, only for products that allow this type of account, and the Developer account type is available on the Admin console.
As an administrator, the Admin Console enables you to create and manage developer accounts. When you add developers to product profiles on the Admin Console, you provide these developers with the access privileges to create API credentials (on Adobe I/O). Also, on Adobe I/O, developers can associate the API credentials they create with product profiles, but only the product profiles to which the developer has access.
When API calls are made from the API credentials that developer creates, these calls executed with the API credentials of the associated product profiles.
When you add developers to product profiles, these developers then have the required permissions to create API credentials on Adobe I/O.
For such an API credential to be used, it needs to be associated with one or more product profiles. This is required so that when API calls are made using an API credential, they execute with the permissions based on the associated product profile or profiles.
Administrators can manage the access granted to an application which uses an API credential by setting or changing the product profiles associated with said API credential.
For example, there might be two product profiles, Test and Production, which grant access and permissions consistent with testing an application and with running the application in a production environment, respectively. The developer could be granted access only to the Test product profile and the API credential is set up by the developer to use that product profile. Once the application is tested and ready for production use, a System or Product Profile admin on the Admin Console would remove the API credential from the Test profile and add it to the Production product profile. The developer no longer has the ability to manage the API credential from the adobe.io console once this change is made.
Usually, developers, are not given admin privileges on the Admin Console.