View a knowledge-library document¶
A knowledge-library view opens one accepted document version for one person in one organization. It uses a short-lived viewing session, separate from the ordinary document viewer used by Records and other work areas.
The shared viewing capability is implemented. The complete library screens and connected journey are still being verified. This page explains access, expiry and recovery; the library's verified task guide will provide its screen sequence. See document admission for how a transferred file becomes an accepted library document.
Administrator preview and member viewing¶
| Purpose | Who needs access | What the view means |
|---|---|---|
| Administrator preview | A person authorized to manage the organization's knowledge library | Inspect the selected accepted document as part of library management |
| Member view | A current member with the required HiveAI access and permission to read that source | Read the selected document through the library's member experience |
These views have different permissions and cannot replace one another. A management preview does not publish the document or prove that members can read it. Member access still depends on the library's current publication and eligibility rules. Knowing a document reference or having someone else's viewing link does not grant access.
The upload must have been accepted for use by the library before this shared view can be issued. Reaching full upload progress, or passing admission while the library handoff is still pending, is not enough. The selected file, version and saved library document must agree.
Five-minute access to the selected version¶
A new knowledge view has an expiry five minutes after creation; access can end earlier if its other requirements no longer hold. A retry of the same request retains the original session and expiry; it does not restart the clock. If the view expires, return to the library and open the document again through the supported action so access can be checked afresh.
Stay in the same organization and use your own session. A changed user, document version or viewing purpose can make an old session invalid. A newly selected version needs its own valid context; the previous version's link is not a shortcut.
The shared service supplies the original file and its original type. A Word document is not automatically converted into a PDF for this view merely because admission rendered it to count pages. The connected application still needs to support displaying the file type. An inability to display a file is different from a failed upload or a missing library document.
View-only scope¶
These sessions authorize viewing. They do not authorize signing, editing, publishing or a separate download action. Use the appropriate library or business action for those operations when it is supported and permitted. Ordinary document-view links are not a fallback for a knowledge-library session.
The system verifies the stored file before returning it and checks access and expiry during delivery. Those checks do not promise immediate detection of every permission or publication change elsewhere in the platform. Stopping a view cannot undo content already delivered or read. Library access changes and removal must follow the source's supported controls.
Recover when a document will not open¶
| What you encounter | What to do |
|---|---|
| The session expired | Return to the library and open the intended document again |
| Your organization or signed-in identity changed | Select the correct organization and reopen using your own access |
| Access is denied | Ask the appropriate administrator to check your current permission and the document's member availability |
| The file is still being accepted | Check the library entry's saved result; full transfer progress alone is not a viewing guarantee |
| The document version is unavailable | Refresh the entry and choose its currently available version through the library |
| Delivery stops or an integrity error appears | Reopen through the source; if it recurs, give support the entry, version, time and visible error |
| The application cannot display the file type | Treat this as a display limitation; do not assume the file must be uploaded again |
Do not share session credentials or attempt to repair a failed view by changing file references. A new upload should follow a confirmed document/version need, not merely a failed viewer response.
For managers and executives, issuing a session or delivering file bytes is not evidence that someone read, understood or approved the document. Preview counts are also not publication counts. Support and operators should distinguish permission, source availability, expiry, integrity and display failures before choosing a recovery action.
The private engineering reference records how these checks are composed and what remains unverified. Initial reader review and the connected library walkthrough are still pending.