In Adobe Admin Console, go to Products > All products and services.
Acrobat Studio for Enterprise.
Organization administrators control Knowledge Base access through the applicable Acrobat Studio for Enterprise product profile in Adobe Admin Console. New Studio customers have Knowledge Base enabled by default. Existing customers may need to enable it, depending on their existing product-profile settings.
In Adobe Admin Console, go to Products > All products and services.
Acrobat Studio for Enterprise.
Select the Acrobat Studio for Enterprise product link.
Select the profile's View Details icon to open the default configuration panel.
Enable the Knowledge Base service toggle.
Click outside the configuration panel to save the settings.
For ongoing administration, user groups provide a more scalable way to manage access than assigning users individually. After you associate a user group with the applicable product profile, membership in the group determines who receives access. Administrators can then manage the group population rather than maintaining individual assignments within the product profile.
In the Admin console, navigate to Users > User groups.
Select New user group.
Provide a descriptive group name and optional expanded description.
Select Save when completed.
The new group is visible on the User groups page.
Select the Group name link to open the entitlement profile.
Select the Product & Roles tab.
Select the ellipsis in the Products section, and select Assign from the dropdown menu.
Select Acrobat Studio for Enterprise from the list of products.
Selecting the product updates the panel to expose the roles that can be assigned to the users in the group.
Select Apply without checking any roles.
The users added to this user group are licensed users, and have all of the access that licensing provides.
Take a moment to review the credit consumption chart to help understand how licensing impacts access for users.
Create a second group using the same process for the Acrobat Shared Credits service.
Acrobat Shared Credits gives users access to the organization’s pooled generative credits for metered activity, including document ingestion and Slack or Microsoft Teams queries. Add users who need these capabilities to the Shared Credits group.
Adobe provisions the Acrobat Shared Credits offer as part of your Enterprise Term License Agreement (ETLA). You don't need to configure the offer in Adobe Admin Console before assigning access.
For customers who already had Acrobat Studio for Enterprise when Knowledge Base launched, Adobe sets the initial Knowledge Base state once for each product profile based on the existing Acrobat AI and PDF Services settings.
| Acrobat AI | PDF Services | Knowledge Base |
|---|---|---|
| On | On | On |
| Off | Any state | Off |
| Any state | Off | Off |
If the resulting Knowledge Base setting is off, enable it for any product profile whose users require access.
For new customers, the Knowledge Base toggle is enabled by default in all product profiles. No additional configuration is required unless you want to disable access.
Assigning a user an Acrobat Studio for Enterprise seat with Knowledge Base enabled provides:
A Studio-licensed user therefore has functional access to Knowledge Base without being assigned to the Acrobat Shared Credits product.
Assign the Acrobat Shared Credits product only to users who need usage beyond the included fair-use and personal-credit allowances.
Users aren't assigned to Acrobat Shared Credits automatically. Assignment is a separate administrator action.
After a delegated user's individual credits are exhausted, additional eligible usage draws from the organization's shared credit pool. The pool is shared by all delegated users and can't be divided or capped by user in Adobe Admin Console.
For new customers, the brief specifies a pooled allowance of 1 million credits per year. Existing customers use their purchased shared-credit pool.
Administrators can monitor Knowledge Base activity using two reporting surfaces:
Users who don't have an individual Acrobat Studio for Enterprise license use a different provisioning workflow. They can query shared Knowledge Base collections using the organization's shared credits but can't ingest documents.