In the Admin Console, navigate to Settings > Privacy and Security > Authentication Settings.
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Deployment home
- K-12 Onboarding Wizard
- Simple setup
- Syncing Users
- Roster Sync K-12 (US)
- Key licensing concepts
- Deployment options
- Quick tips
- Approve Adobe apps in Google Admin Console
- Enable Adobe Express in Google Classroom
- Integration with Canvas LMS
- Integration with Blackboard Learn
- Configuring SSO for District Portals and LMSs
- Add users through Roster Sync
- Kivuto FAQ
- Primary and Secondary institution eligibility guidelines
- 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 users
- Overview
- Administrative roles
- User management strategies
- Assign licenses to a Teams user
- In-app user management for teams
- Add users with matching email domains
- 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
- Overview
- Manage products and entitlements
- Manage products and product profiles
- Manage products
- Buy products and licenses
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Entitle users to train Firefly custom models
- 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 products and product profiles
- Get started with Global Admin Console
- Adopt global administration
- Select your organization
- Manage organization hierarchy
- Manage product profiles
- Manage administrators
- Manage user groups
- Update organization policies
- Manage policy templates
- Allocate products to child organizations
- Execute pending jobs
- Explore insights
- Export or import organization structure
- Manage storage and assets
- Storage
- Manage projects
- 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
- Overview
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Manage your Teams account
- Renewals
- Manage contracts
- Reports & logs
- Get help
Applies to enterprise.
Manage your organization's security in the Adobe Admin Console. Select appropriate authentication policies, enable 2FA, and set location-based access for your users.
Password policies apply to all identity types supported on the Adobe admin console except the Federated ID type.
All accounts include a lockout mechanism. If the system detects a quick succession of multiple failed login attempts, the user account is temporarily unavailable to prevent brute force attacks.
To specify a password policy, do the following:
-
-
Choose a level of authentication for your users based on your ease of use and security requirements.
Selecting an option automatically selects and saves it.
Enable 2-step verification
To strengthen the security in their Adobe accounts, your users can set up 2-step verification. Once set up, your users require a verification code to sign in to their Adobe accounts before they enter their Adobe account passwords. This setup is done by each user in their Adobe account. Adobe users can normally turn 2-step verification on and off on depending on their security preferences.
As an admin, you have the option to enforce two-step verification. This ensures that users then do not have the options to turn it off.
Adobe highly recommends that you, as the admin, enforce two-step verification in your organization, and don’t leave this as optional for your users.
2-step verification (or 2FA) is available for Enterprise ID and Adobe ID users only. Note: 2FA may take up to 24 hours to apply to all the users in your organization.
This method does not apply to Federated ID users. However, you can enforce 2-step verification for Federated ID users from your identity provider.
When you turn on 2-step verification, the users in your organization will receive an email.
- After you've set up 2-step verification, the first time a user signs in, Adobe requires the collection of their phone number. This ensures that the user can recover their account in case they've lost the password.
- This policy will prevent users who have already set up 2-step verification from taking any action but from un-enrolling.
- Users who have not set up 2-step verification will be required to enroll in this service the next time they sign into their Adobe account. For details on how your users must enroll, see this article.
As a teams or enterprise admin, select the social login providers you want to allow for users in your organization. Existing Adobe ID users who log in with a disabled social provider will be forced to set a password on their next login. When disabled, we'll notify all your users via email.
Go to Admin Console Authentication settings and select the social options you want to allow for your users. Then Save.
If a user attempts to sign-in via a social login that you've disabled, we notify the user about its unavailability. We then prompt the user to create a password for their Adobe ID or Enterprise ID. Then, the user will sign in using these credentials.
This option is not available if you've set up Federated ID users. Federated ID users always use the configured single sign on provider.
You can enable or restrict your users' use of specific Adobe account profiles and their associated apps based on their IP address. This allows your organization to prevent users from accessing apps outside designated areas such as offices or institutes.
When you set specific IP addresses to the Allowed IP addresses list, it restricts users from:
- using an IP-restricted account profile
- switching profiles on web apps outside the set IP address range
Follow the steps below to enable location-based access in your Adobe Admin Console:
-
Go to Adobe Admin Console Settings section.
-
Select and expand Privacy and security in the selection menu and select Authentication setttings.
-
In the IP address restriction section, select Add IP address.
-
In the Add IP address window, enter the IP addresses you want to allow and Save. Use a comma to separate multiple IP addresses. Example: 192.168.0.0/16.
Add admin's IP address firstWe recommend that you start with adding your own IP address as an admin to avoid being blocked from the Adobe Admin Console.
Your IP addresses are added in a few minutes after entering and associated users will see the restriction when they try to sign in the next time.
You can also remove the IP addresses from the allow-list by selecting one or more IP addresses.
- If you're locked out of the Admin Console because you entered an invalid IP address, contact Adobe customer care.
- When location-based access is enabled, no forced logout occurs. Users are only impacted when they try to choose the restricted profile when signing in.
To control how long your users remain authenticated in Adobe apps, use the following Advanced settings:
- Max session life: Users need to reauthenticate after the duration you specify. The session life is effective on all user sessions of Adobe apps across devices.
- Max idle time: Adobe will automatically sign out users who do not interact with the account for a period more than the idle time that you specify. The idle time affects the following Adobe Web Applications:
- Creative Cloud Web
- Adobe Express
- Adobe Stock
- Adobe Color
- Adobe Font
- Creative Cloud Assets
- Behance/Portofolio
- Acrobat.com
If a user is a member of multiple organizations with advanced authentication policies, the most restrictive policies will apply to that user. For example, if one policy defines a Maximum session life as 12 days and another defines this setting as 9 days, the user is reauthenticated every 9 days.
We recommend that you do not set short session policies unless you require stricter security measures. Short session policies will require users to sign in more frequently. Leaving these policies at their default state is the right choice for most Adobe customers.