Understand how Knowledge Base in Acrobat usage is measured for Studio users, non-Studio users, and Technical Accounts.
Knowledge Base uses different usage models depending on the user's access and the action performed. Some Studio queries count against a Fair Use Policy (FUP) allocation, while document ingestion, Slack and Microsoft Teams queries, non-Studio queries, and API activity consume Shared Credits.
Understand FUP and Shared Credits
Knowledge Base uses two separate usage measures: FUP queries and Shared Credits.
Fair Use Policy (FUP) is an allocation of 1,000 Knowledge Base queries per Studio user each month.
Supported queries from the Knowledge Base AI Assistant and PDF Spaces count against the user’s FUP allocation.
Shared Credits are consumed by other metered Knowledge Base activities. The number of credits consumed depends on the action and the user's access.
FUP queries and Shared Credits are measured separately. An FUP query counts against the user's monthly query allocation; it does not represent a fixed number of Shared Credits.
Understand Shared Credit rates
The following activities consume Shared Credits when performed through the applicable access model:
| Activity | Credit consumption |
|---|---|
| Document ingestion | 150 credits per document |
| Slack or Microsoft Teams query | 50 credits per query |
| Non-Studio AI Assistant query | 50 credits per query |
| API document ingestion | 150 credits per document |
| API query | 50 credits per query |
How those charges are applied depends on the user's access.
Compare access and consumption
Use the following table to identify which capabilities and consumption model apply to each access type.
| Access type | FUP queries | Document ingestion | Studio queries (AI Assistant and PDF Spaces) | Slack/Teams | Charges applied to |
| Studio user with Shared Credits | 1,000 per user/month | 150 credits/document | FUP — 1,000 queries/user/month | 50 credits/query | User's FUP and Shared Credit pool, depending on activity |
| Studio user without Shared Credits | 1,000 per user/month | Not available | FUP — 1,000 queries/user/month | 50 credits/query | FUP for Studio queries; collection owner's Shared Credits for Slack/Teams |
| Non-Studio user without direct Shared Credits | Not applicable | Not available | 50 credits/query | 50 credits/query | Collection owner's access to Shared Credits |
| Non-Studio user with direct Shared Credits | Not applicable | Not available | 50 credits/query | 50 credits/query | User's access to Shared Credits |
| Technical Account | Not applicable | 150 credits/document through API | 50 credits/query through API | 50 credits/query through API | Technical Account owner's access to Shared Credits |
Studio users with access to Shared Credits
A user with an Acrobat Studio for Enterprise seat and access to Shared Credits can:
- Create and manage collections.
- Create connectors.
- Configure Slack and Microsoft Teams chatbots.
- Ingest documents.
- Query using the AI Assistant.
- Query through Slack and Microsoft Teams.
Usage is metered as follows:
| Activity | Usage | Charged against |
| Queries from Studio experiences, including PDF Spaces and the Knowledge Base AI Assistant | Up to 1,000 queries per user each month | User's FUP allocation |
| Document ingestion | 150 credits per document | Shared Credit pool |
| Slack and Microsoft Teams queries | 50 credits per query | Shared Credit pool |
Document ingestion does not count as an FUP query. It is a Shared Credit transaction.
Studio users without access to Shared Credits
A user with an Acrobat Studio for Enterprise seat but without direct access to Shared Credits can use supported Studio query experiences and query through Slack and Microsoft Teams.
These users can:
- Query using the Knowledge Base AI Assistant.
- Query through PDF Spaces.
- Query through Slack and Microsoft Teams.
They cannot:
- Ingest documents.
Queries from the Knowledge Base AI Assistant and PDF Spaces count against the user's FUP allocation of 1,000 Knowledge Base queries per month.
Slack and Microsoft Teams queries consume 50 Shared Credits per query. Because Shared Credits aren't assigned directly to the user, this consumption is charged against the collection owner's access to the Shared Credit pool.
Non-Studio users with direct access to Shared Credits
A non-Studio user can also receive direct access to Shared Credits, including through a just-in-time (JIT) assignment rule.
These users can:
- Query using the AI Assistant.
- Query through Slack and Microsoft Teams.
They cannot:
- Create or manage collections.
- Create connectors.
- Configure Slack or Microsoft Teams chatbots.
- Ingest documents.
Each AI Assistant, Slack, or Microsoft Teams query consumes 50 Shared Credits.
Because the user has direct access to Shared Credits, consumption is charged against that user's access to the Shared Credit pool.
Non-Studio users without direct access to Shared Credits
A non-Studio user can query content without having direct access to Shared Credits.
These users can:
- Query using the AI Assistant.
- Query through Slack and Microsoft Teams.
They cannot:
- Create or manage collections.
- Create connectors.
- Configure Slack or Microsoft Teams chatbots.
- Ingest documents.
Each AI Assistant, Slack, or Microsoft Teams query consumes 50 Shared Credits.
Because Shared Credits aren't assigned directly to the user, the consumption is charged against the collection owner's access to the Shared Credit pool.
Technical Account consumption
A Technical Account requires:
- An Acrobat Studio for Enterprise seat.
- Access to Shared Credits.
Technical Accounts support collection management, document ingestion, and query operations through supported API workflows.
API activity is metered as follows:
| Activity | Credit consumption | Charged against |
| Document ingestion through the API | 150 credits per document | Technical Account owner's access to the Shared Credit pool |
| API query | 50 credits per query | Technical Account owner's access to the Shared Credit pool |
All supported API usage performed through the Technical Account is metered against the Shared Credits available to the Technical Account owner.
Credit consumption considerations
- FUP applies to supported Studio queries and is measured in queries rather than Shared Credits.
- Each Studio user receives an FUP allocation of 1,000 Knowledge Base queries per month.
- Document ingestion requires access to Shared Credits and consumes 150 credits per document.
- Slack and Microsoft Teams queries consume 50 Shared Credits per query.
- Non-Studio users don't receive an FUP allocation.
- Non-Studio users cannot ingest documents or create and manage collections.
- For non-Studio users without direct Shared Credits access, query consumption is charged against the collection owner's access to Shared Credits.
- Technical Account API activity is charged against the Technical Account owner's access to Shared Credits.
