This update of DocuWare Aura gives administrators control over how many Aura Credits their organization spends and a clear view of what has been used. A credit limit keeps the consumption within a set volume, an overview shows the credits used against the contract, and a new general-purpose LLM API makes the language model behind Aura available to your own applications.
Nothing has to be migrated or configured. The functions use the Aura configuration, the file cabinets, and the permissions your organization already has.
Components: New DocuWare Client, DocuWare Cloud, DocuWare Aura API
Credit limit for DocuWare Aura
Administrators can set a daily limit for Aura Credits per user, role, or group. The limit for a role or group applies to each member individually, not as a shared amount. The configuration is available in DocuWare Configurations > Aura.
Benefits
Control Aura usage per user, role, or group
See current usage and the daily limit that applies to each user
Give one user a different limit without changing anyone else's
Here's how
Open DocuWare Configurations > Aura and enter the limit under Aura Credit Limit. If a user has an individual limit, it applies; otherwise, the highest limit of the user's roles and groups applies. A limit of 0 credits blocks DocuWare Aura for a user, role, or group, in the same order. When a user reaches the limit, further questions are rejected, and a note above the question field says that no credits remain for the day and that they reset at midnight.
More information in DocuWare Aura configurations.
Consumption and contract overview
The Aura configuration now has a Consumption overview tab. It shows the credit packages your organization has purchased and their term, the credits consumed and remaining, and which Aura features and users consumed them.
Benefits
See at a glance how much of the contracted credit volume is left
Identify which Aura features consume the most credits, for example, Aura Chat, Aura API, or the LLM API
Review consumption per user and decide on a larger package based on actual use, not on estimates
Here's how
Open DocuWare Configurations > Aura and select the Consumption overview tab. The Orders section lists each purchased credit package with start date, end date, and quantity. Consumption Overview shows total, consumed, and remaining credits, with a bar that splits consumption by service: Aura Chat, Aura API, Aura Retrieval API, and LLM API. A note warns when a large share of the contracted credits has been consumed. Consumption per integration type lists requests and credits per service, and Consumption per user lists the users with the highest consumption. Consumption is tracked for the whole organization and deducted at the time of each request. The tab appears automatically for organization administrators of organizations with a paid contract; no configuration is needed. More capacity can be added at any time through your DocuWare contact.
More information in DocuWare Aura configurations.
General-purpose LLM API
The DocuWare Aura API now offers a general-purpose endpoint for Aura's language model. Your application sends text and a task, such as summarize, translate, classify, or rewrite, and receives the result. The request does not use DocuWare documents or document retrieval.
Benefits
Access DocuWare Aura's general AI language capabilities through an API
Works on any text your application sends, no DocuWare documents or file cabinet access needed
Integrate AI capabilities into custom applications and services
Here's how
The endpoint is part of the DocuWare Aura API and uses the same authentication as the other endpoints: a JWT bearer token from the DocuWare Identity Service. Developers find the full definition in the Swagger documentation of your Cloud domain under /DocuWare/aura/docs. There is no setting in the DocuWare user interface. Each request consumes Aura Credits and appears as LLM API in the Consumption overview of the Aura configuration.
More information in DocuWare Aura API and AI agent integration.