Understand the access options, entitlements, capabilities, and credit usage to consider before provisioning users for Knowledge Base.
Administrators can provide access to Knowledge Base in Acrobat for Studio-licensed users who create and manage knowledge and for non-Studio users who query knowledge shared with them. Access is managed through Adobe Admin Console and depends on the products, product profiles, and services assigned to each user.
Knowledge Base does not have a separate product SKU. Your organization must have Acrobat Studio for Enterprise, and administrators use the Acrobat Studio for Enterprise and Acrobat Shared Credits products to control access and usage.
Before you begin
To provide access to Knowledge Base:
- Your organization must have Acrobat Studio for Enterprise through an Enterprise Term License Agreement (ETLA).
- You must be a system administrator or product administrator in Adobe Admin Console to configure access.
- Adobe provisions the Acrobat Shared Credits offer as part of account setup. You don't need to make the offer available before assigning users to it.
Understand the access model
The access a user receives depends primarily on whether the user has an individual Acrobat Studio for Enterprise license.
| Studio-licensed user | Non-licensed user | |
| License | Individually licensed for Acrobat Studio for Enterprise | The organization has Acrobat Studio for Enterprise, but the individual user does not |
| Knowledge Base access | Enabled through the Knowledge Base service in the applicable Acrobat Studio for Enterprise product profile | Provided through the supported non-Studio access configuration |
| Create and manage collections | Yes | No |
| Ingest documents | Yes, when the required credit access is available | No |
| Query collections | Yes | Yes |
| Administrator action | Enable Knowledge Base for the applicable product profile | Provide non-Studio access through the supported Admin Console provisioning method |
Understand credit usage
The user's access type determines how Knowledge Base activity is metered.
Studio-licensed users
Studio users receive:
- A fair-use allowance for supported AI Assistant queries.
- 250 non-poolable generative credits per month for eligible metered activity.
- Access to the organization's shared-credit pool when the applicable Acrobat Shared Credits access is assigned.
Current metered activities include:
- AI Assistant queries: 50 generative credits per metered query.
- Slack and Microsoft Teams queries: 50 generative credits per action.
- Document ingestion: 150 generative credits per document.
Studio users can use available individual allowances before eligible usage draws from the organization's shared-credit pool.
Non-Studio users
Non-Studio users don't receive an individual Studio credit allocation.
Their supported Knowledge Base activity draws from the applicable fair-use credit pool:
- AI Assistant queries: 50 generative credits per metered query.
- Slack and Microsoft Teams queries: 50 generative credits per query.
- Document ingestion isn't available.
For current rates and detailed metering behavior, see Knowledge Base credit consumption.
Understand the shared-credit pool
Shared Credits provide pooled capacity for eligible Knowledge Base activity.
- New Acrobat Studio for Enterprise ETLA customers receive an included pool of 1 million Shared Credits per year.
- Existing Studio customers don't automatically receive this included pool. They use Shared Credits already available through other offers or purchase additional pooled credits.
- Additional Shared Credits can be purchased when usage exceeds the available pool.
- Unused Shared Credits don't roll over.
- Applicable overages are settled through true-up at the contract anniversary.
Review expected usage before extending access broadly.
Understand Technical Account access
Technical Accounts provide access for supported API integrations and service-based workflows.
A Technical Account requires:
- An Acrobat Studio for Enterprise seat.
- Access to Shared Credits.
Developers can use the credentials associated with the Technical Account for supported integrations rather than creating separate Technical Account credentials for each developer.
Technical Account activity can include:
- API queries at 50 generative credits per query.
- Document ingestion at 150 generative credits per action.
Usage performed with the Technical Account is metered against that account.
Control who can use Knowledge Base
Access is not automatically provided to every user in the organization.
Use product profiles in Adobe Admin Console to determine which users receive the required entitlements. For example, you can assign access only to a specific department or group rather than making Knowledge Base available throughout the organization.
Plan these assignments carefully so that access aligns with the users who need to create or query organizational knowledge.
Choose the appropriate access
Before provisioning access, determine what the user or integration needs to do:
- Studio access — Use for users who need to create collections, manage knowledge, ingest content, or query collections with an individual Studio license.
- Studio access with Shared Credits — Use when Studio users also need eligible activity backed by the organization's shared-credit pool.
- Non-Studio access — Use for users who only need to query knowledge created and maintained by others.
- Technical Account access — Use for supported API integrations and service-based workflows.
Then use the appropriate provisioning procedure in Adobe Admin Console.
Enable access for Studio licensed users
Studio users receive Knowledge Base access through their Acrobat Studio for Enterprise product profile.
Enable the Knowledge Base service for the product profile containing the users who need access.
Studio users can:
- Create and manage collections.
- Add supported content to collections.
- Query collections using the AI Assistant.
- Use supported Slack and Microsoft Teams chatbot experiences when the applicable integrations and credit access are available.
Studio users receive usage allowances with their Acrobat Studio for Enterprise license. Supported AI Assistant queries use the applicable fair-use allowance. Each Studio seat also includes 250 non-poolable generative credits per month for eligible metered activity.
When additional eligible activity requires pooled credits, assign the user access to the organization's Acrobat Shared Credits pool.
Enable access for non-Studio licensed users
Non-Studio users don't have an individual Acrobat Studio for Enterprise license. They receive query-only access to knowledge shared with them and cannot create collections or ingest documents.
Depending on your organization's configuration, administrators can provide non-Studio access through supported Adobe Admin Console provisioning methods, including direct assignment or an automatic assignment rule.
After access is granted, users can query Knowledge Base through supported experiences, including:
- Knowledge Base on the web.
- Slack.
- Microsoft Teams.
Non-Studio users do not receive the 250 non-poolable monthly credits included with a Studio license. Their eligible Knowledge Base usage draws from the applicable fair-use credit pool.
A user's first sign-in must occur through knowledgebase.adobe.com or a supported Adobe application, such as Acrobat. First-time authentication directly from Slack or Microsoft Teams isn't supported.
Before you assign access
- Administrators control access through the Adobe Admin Console product profiles and user assignments.
- Studio users receive included usage with their license. Assign access to the organization's shared-credit pool when they need additional metered usage beyond their individual allocation.
- Non-Studio users can query knowledge made available to them, but cannot create collections or add content to collections.
- Chatbot access also depends on the applicable Slack or Microsoft Teams integration being enabled for the organization.
- Review credit consumption before extending access to large user populations.
