Admin visibility, audit logs, and per export limit for KB site PDF downloads
under review
D
Dusk blue Perch
The KB site enforces a 500 MB daily limit for PDF downloads, but there is no visibility on the Admin side to track how much of this limit has been consumed or how much remains. The warning appears only after the limit is exceeded, which prevents proactive monitoring and planning.
There are currently no audit logs available for PDF exports from the KB site. Admins cannot see who initiated downloads, how much data was exported, or when the activity occurred. Audit logging should be added for transparency and tracking.
In addition, a per export size limit should be introduced. This will ensure that one large export does not exhaust the daily quota and impact other customers sharing the same environment.
Log In
D
D360 Product Management
Merged in a post:
Per-User Download Limit Instead of Global Limit
Uppili Srinivasan
PDF download limit is currently applied at the knowledge base level, meaning all users share a single daily download quota. 500 MB per day for all the end users.
- If multiple users download PDFs simultaneously, the shared limit may be exhausted. When this occurs:
- All users are blocked from further downloads.
- End users are unaware that the limit was consumed by other users.
Proposed Enhancement
-Replace the global KB-level download cap with a per-user download threshold, ensuring:
-Each user should have an independent daily download limit.
-One user’s activity does not block others.
D
D360 Product Management
Hi Uppili Srinivasan , Dynamic Dingo,
Merging this request with parent ticket with same context
D
D360 Product Management
marked this post as
under review
K
Kavya
Hi Dusk blue Perch,
Thank you for outlining these concerns in detail. We understand how the lack of visibility into the 500 MB daily PDF download limit, combined with the absence of audit logs and per-export size controls, can make monitoring and capacity planning difficult.
We’ll take this feedback into consideration and review the feasibility of:
Providing admin-side visibility into daily PDF download consumption
Introducing audit logs for KB site PDF exports (who initiated, when, and size exported)
Evaluating a per-export size limit to prevent a single large export from exhausting the daily quota
Since this touches quota management, analytics, and logging, it will require a broader review from the product and engineering teams. We’ll share an update once we have more clarity on feasibility and prioritization.
A
Acid green Rabbit
From a support perspective, export limits operate like a black box. We do not have access to usage logs, activity history, or quota reset details. Without this visibility, we cannot confidently explain system behavior.
J
Jambalaya Mouse
The issue is not the limit itself but the lack of transparency. If we had visibility into export usage and activity history, most escalations could be avoided.
I
Indigo Partridge
Customers often assume the feature is broken when they hit the export limit. Since we cannot see prior usage or activity details, we are unable to clearly confirm whether the behavior is expected.
S
Safflower Kangaroo
We currently have no visibility into export quota usage. When customers report that the limit is exceeded, we cannot see who triggered exports, how many were executed, or whether one large export consumed the quota. This leaves us responding without facts.
F
Fuzzy Narwhal
There are no audit logs showing who exported data or how much was exported. If the limit is exceeded, we cannot verify whether it was legitimate usage or a system issue. That creates risk for a customer facing feature.
G
Granite Crayfish
There is no way for us to verify export activity or quota consumption. We cannot confirm whether multiple small exports or a single large export caused the limit to be hit, which makes customer conversations difficult.
Load More
→