Enable user access to Knowledge Base

Last updated on Sep 28, 2026

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.

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-Studio 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 applicable Acrobat Shared Credits provisioning method
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

Credit consumption depends on the user's access type and the activity performed.

Studio-licensed users receive fair-use allowances with their Studio license, including 250 non-poolable generative credits per month for eligible metered activity. Depending on the activity and assigned access, additional usage can draw from the organization's shared-credit pool.

Non-Studio users do not receive the 250-credit individual allocation. Their eligible Knowledge Base activity draws from the applicable fair-use credit pool.

For current rates and detailed metering behavior, see Knowledge Base credit consumption.

Technical Account access

Technical Accounts provide access for supported API integrations and service-based workflows. They require the applicable Studio and credit access, and their usage is metered separately from individual user activity.

Create a Technical Account for Knowledge Base >

Choose the appropriate access

Administrators control who receives Knowledge Base access through Adobe Admin Console. 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 Studio users >

Enable access for non-Studio 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.

Enable access for non-Studio users >

Before you assign access

  • Administrators control Knowledge Base access through Adobe Admin Console.
  • Knowledge Base doesn't have a separate product SKU.
  • Your organization must have Acrobat Studio for Enterprise through an ETLA.
  • Studio and non-Studio users have different capabilities and credit-consumption models.
  • Non-Studio users can query shared knowledge but cannot create collections or ingest documents.
  • The 250 non-poolable monthly credits apply only to Studio-licensed users.
  • Slack and Microsoft Teams access also requires the corresponding chatbot integration to be enabled for the organization.
  • Review current credit consumption before providing access to large user populations.