-
Setup and onboarding
- Explore Adobe Admin Console
- Sign-in and access
-
Licensing
- Licensing overview
- Licensing types
-
Identity and SSO
- Set up identity
- Integrate with Microsoft Entra
- Integrate with Google Sync
- Integrate with other SSO providers
- Troubleshoot
-
Directories, domains, and access
-
Directories and domains
- Create a directory for SAML identity providers
- Verify domain ownership
- Set up domains for directory authentication
- Move domains across directories
- Encrypted and trusted directory domain transfers
- Move directories between Admin Consoles
- Delete directories and domains
- Automatic account creation overview
- Enable automatic account creation
- Automatic federated account creation FAQ
- Domain enforcement
- Directory trusting
-
Directories and domains
-
Settings
- Asset settings
- Manage encryption
-
User management
- Understand user management
- Manage users and groups
- Manage admins
- Manage user roles
- Migrate users
-
Products and entitlements
- Manage products
- Manage product profiles
- Special programs plans
- Manage entitlements
- Manage automatic assignment
- Manage product access
- Manage self-service policies
- Manage app integrations
- Frame.io integration
- Manage product permissions
- Manage storage and assets
-
Manage services
- Configure services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
-
Deploy apps and updates
- Prepare for deployment
- Manage pre-generated packages
- Create packages
- Customize end-user experience
- Deploy packages
- Use third-party deployment tools
-
Manage Shared Device Licensing (SDL)
- Shared Device Licensing overview
- Deploy Shared Device Licensing
- Manage SDL profiles and user access
- Activate shared device licenses
- Use the Shared Device Licensing toolkit
- Recover shared device licenses
- Shared Device Licensing identity FAQ
- Shared Device Licensing deployment FAQ
- Shared Device Licensing access FAQ
- Known issues in Shared Device Licensing
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Contracts and renewals
- Reports and logs
-
Get started with Global Admin Console
- Get started
- Manage your organization
- Reports audit
-
Get help
- Support options
-
General troubleshooting
- Microsoft Purview Information Protection support in Acrobat
- Use the Creative Cloud Cleaner tool to fix installation issues
- Fix app launch errors on Shared Device Licensing machines
- Technical support boundaries for virtualized or server-based environments
- Resolve trial and license expired errors
- Migrating to OAuth Server-to-Server Credentials
- Manage device authentication for Creative Cloud and Acrobat Pro
Content Credentials for enterprise content
Understand how metadata transparency helps verify content origin and authorship in your organization.
When your team creates content using Adobe tools, Content Credentials help verify authenticity and origin by embedding trusted metadata that shows how the content was created, who created it, and which tools were used.
Content Credentials use an industry-standard approach to show content transparency. They serve as metadata capturing creation details and may include the creator's identity information. The metadata persists with the content when published online, allowing viewers to verify its origin and creation process using verification tools.
Content Credentials functionality
Content Credentials attach to files as durable metadata. They include details about the creation process, such as which Adobe applications were used and what edits were applied. Invisible watermarking and digital fingerprinting protect this metadata from removal or tampering.
When content with Content Credentials is published to supporting platforms or shared online, anyone viewing it can access the embedded information. Adobe provides free verification tools, including the Inspect tool and the Adobe Content Authenticity Chrome browser extension, which reveal the metadata to viewers.
Identity information management
Beyond documenting the creation process, Content Credentials can include personal identity information about the creator. When enabled, users can link their identity to content they produce, helping them maintain attribution as their work circulates online. The identity component is managed through Adobe's Connected Identities system. Users can decide what personal information is included in their credentials and remain in control of what they share.
Organizations control whether users can apply Content Credentials and whether they can include identity information, which is managed separately in the Admin Console under Settings > Asset Settings > Content Credentials.
- Access to Content Credentials: It governs general access to Content Credentials features. Users can manage and apply Content Credentials in Adobe apps only when the feature is turned on. When turned off, preferences are hidden, and credentials cannot be managed.
- Access to Content Credentials individual identity information: This setting only functions when general Content Credentials access is already enabled. When turned on, users can include personal identity information from their Connected Identities profile when applying credentials. When turned off, users can still apply Content Credentials documenting the creation process, but those credentials won't include personal identity information.
Generative AI integration
Content created with Adobe Firefly, whether via the web or the API, automatically receives Content Credentials. These credentials document the use of generative AI in the creation process.
By default, the credentials don't include personal identity information. If you’ve enabled identity access and a user adds personal details to Content Credentials, the credentials display both generative AI use and the user’s identity.
Organizational responsibility
As an organization, you own and are responsible for content produced by your users. This includes any content that may contain Content Credentials with identity information. The metadata is designed to stay with the content as it's shared online.
Consider your organization's content policies, privacy requirements, and attribution practices when deciding whether to enable Content Credentials and the use of identity information. Some organizations value transparency and attribution benefits, while others prefer to limit the disclosure of identity information in exported content for privacy or competitive reasons.