Status
Understand how users can request Adobe products and how administrators manage those requests.
Product access requests let users obtain Adobe products directly in the app. Administrators review and approve these requests in the Admin Console.
This reduces administrative overhead while giving users faster access. It also provides administrators with visibility into product demand across their organization.
Product requests process
Users: A request includes the product they need and a business justification. See Request access to an Adobe product.
System Administrators: You receive an email for each new request and can approve or deny it from the email or in the Admin Console.
Products > Product access automation > Product requests.
For each request, you can see available licenses and applicable product profiles. Approve the request, or deny it with a reason. You must select a reason when you deny. To decide later, close the review window; the request stays in the queue. For step-by-step instructions and notification settings, see Manage access requests.
Reviewing requests requires the System Administrator role. To see which roles can do what, see Admin roles and hierarchy.
Request statuses
|
|
What it means |
What happens next |
|---|---|---|
|
Pending |
Waiting for administrator review, for up to 60 days |
The user is reminded at 30 days and can’t submit the same request again while it’s pending. All System Administrators are notified of requests expiring within 30 days. |
|
Approved |
Approved by an administrator or automatically |
The license is added to the user’s account and they receive an email. An administrator may approve a different product than the one requested. |
|
Denied |
An administrator denied the request and selected a reason |
The user receives the reason by email and can request again with a more detailed justification. |
|
Expired |
No administrator action within 60 days |
The user can resubmit with an updated justification. |
The Admin Console queue shows requests from the last 60 days. Requests that were answered or expired in the last 90 days appear in the audit log.
Where users can request access
Users can request a product from the Creative Cloud desktop app, Creative Cloud on the web (desktop only), Adobe Stock, Adobe Acrobat Sign, Adobe Express, Adobe Firefly, Developer Console, and Adobe Acrobat (AI Assistant only).
For products that don’t support in-app requests, such as Adobe Analytics, create an automatic assignment rule to generate a Product Access URL and then share it with your users.
Eligible users who open the URL gain access right away, without administrator review.
Availability and eligibility
Product requests are enabled by default for organizations that use Adobe storage for business. The feature is available to Enterprise, Teams, and eligible Education organizations.
The setting applies to the whole organization. You can’t limit requests to specific products. To give users automatic access to specific products instead, use automatic assignment rules.
System Administrators can enable or disable product requests at any time. In the Admin Console, go to Products > Product access automation > Product requests, select Edit settings, and use the Request access toggle. When requests are off, users can’t submit new ones, but you can still respond to existing requests, and users can’t request to join your organization through domain matching.
Requests for unavailable products
Users can request any Adobe product shown in the app they’re using, whether or not your organization owns licenses for it. These requests show an indicator in the Admin Console so you can see unmet demand. For options, including adding licenses, see Manage access requests.
Relationship to automatic assignment rules
Automatic assignment rules and product requests work together. Rules grant immediate access based on criteria such as domain or group membership. Requests allow users to request access with administrator approval. When a user qualifies for a rule, the rule takes precedence and grants access without administrator review.
Multiple requests and bundling
When one user has several pending requests, the Admin Console groups them into a single queue item. You can approve some requests and leave others in the queue.
Troubleshoot pending requests
|
Problem |
Possible cause |
Guidance |
|---|---|---|
|
You don’t receive request emails or can’t open the queue. |
You don’t have the System Administrator role, or notifications are set to a lower frequency. |
Check your role. On the Product requests page, select Edit settings and review the notification frequency. |
|
A user says they requested a product, but nothing is in the queue. |
Product requests are off, the request expired, the user sent it from a profile tied to a different organization, or the user qualified for an automatic assignment rule. |
Check the Request access toggle. Search the audit log for the last 90 days. Ask which profile the user signed in with. Review your automatic assignment rules. |
|
A request has been pending for a long time. |
It’s still waiting for review, and requests stay in the queue for up to 60 days. |
Review it now, or close the window and return later. It expires after 60 days. |
|
A user can’t find the Request access option. |
Product requests are off for the organization or for the profile they signed in with. |
Confirm the setting. See Request access to an Adobe product. |