A shared document link should not automatically grant the knowledge assistant access. Resolve the source system’s actual sharing semantics and the current user’s authority before retrieving or previewing its contents.
Links can represent different capabilities
A link may identify a resource, require authentication, grant a bounded sharing capability, or expose public content. Those meanings depend on the source system and configuration. A familiar URL shape does not establish the policy.
For a proposed connector, classify supported link types through the provider’s documented behaviour. Keep the original resource identity, sharing scope, expiry where applicable, and trusted user context. Do not use a broad ingestion credential to open anything a user pastes.
Source permission and external-fetch controls are separate. A user-provided URL can also point outside the approved company systems. The application needs supported destination and retrieval rules rather than unrestricted network access.
Test a fictional forwarded project link
A project member sends an employee a restricted document link. If the source still requires project membership, the assistant should not retrieve it for the employee through its service account. It can explain the access limit and approved request path.
A different link deliberately grants a time-limited permitted share. The integration should honour its documented scope without treating it as permanent access to the entire folder or client collection.
| Link condition | Expected handling |
|---|---|
| Authenticated restricted resource | Current user permission enforced |
| Supported bounded share | Exact documented scope respected |
| Expired or revoked link | No cached continuation beyond policy |
| External unsupported destination | Controlled rejection or approved path |
| Link to another tenant | No account-scope bypass |
Inspect snippets, titles, previews, and logs as well as full content. A denied body request can still leak the resource through metadata returned earlier in the flow.
Keep shared-link evidence minimal
Some links contain secret-like capability tokens. Avoid placing them in broad diagnostics, analytics, or agent handoffs unnecessarily. Use controlled resource references where the architecture supports them.
Supporting many sharing modes improves convenience but increases policy complexity. Start with the actual source systems and documented link types needed for the pilot. Test revocation and expiry rather than inferring them from a successful initial fetch.
This connector design is proposed. The voice integration case study describes related retrieval work without claiming specific sharing guarantees. Pair it with citation access checks.
Shared-link FAQ
Does possession of a link prove permission?
Only under the source system’s explicit supported sharing semantics, not as a universal rule.
Can the assistant open a link with administrator credentials?
Not to bypass the current user’s authorised scope.
What should be tested?
Verify link type, expiry, revocation, tenant scope, metadata exposure, caches, and destination controls with fictional resources.