View access does not automatically include copy or download rights. Separate viewing, downloading, account and administrator policy, then request the specific permission from the document owner instead of trying to bypass the restriction.
The document opens, but the download option is missing. Copy does nothing. A browser extension cannot read the page either. It is tempting to blame the extension.
In practice, viewing a document and taking a copy are separate permissions. Identifying the layer that blocks the action is faster than reinstalling tools, and it avoids attempting to bypass an organization’s rules.
View access is not download access
Document platforms often separate view, comment, edit, copy, print and download. Permission to read a page does not automatically include permission to retain a file.
Common combinations include:
| What happens | Possible cause | Check first |
|---|---|---|
| Document opens, no download option | The role is view-only | The permission granted by the owner |
| Single downloads work, batch does not | Batch export is restricted | Account and folder permissions |
| Text copies, images fail | Images have separate access rules | Image permissions and network |
| Extension cannot read the page | Browser policy or page type | Web app, extension status |
| Everything fails after switching accounts | Organization or external tenant | Account, tenant and sharing scope |
Rule out ordinary account problems first
Before assuming a policy restriction, confirm three things: you are signed in with the intended account, the page is the Feishu web app, and the document is not available only in the desktop client.
Personal accounts, guest accounts and external contacts may receive different permissions. A link that opens from a chat message may not remain available after signing out or moving to another browser.
When a document belongs to another organization, its owner controls access. Switching accounts repeatedly will not change that. Ask the owner to confirm the sharing scope.
A browser extension still operates inside the original permission
An extension can organize content that the current page already allows you to see. It cannot bypass view-only controls, download restrictions or managed-browser policy, and it should not be used to evade them.
Reading page source is not the same as holding a server-side authorization. Content that the product does not expose to your account generally remains outside the extension’s legitimate scope.
The useful boundary is simple: the extension turns viewable content into local files. It is not a permission bypass.
What to do when export is blocked
- Record the document name, owner and permission shown to you.
- Test one non-sensitive document to see whether the restriction is broad or limited.
- Check the browser account, web-app URL and extension status.
- Ask the owner for download or backup access and explain the use case.
- Follow internal policy for enterprise restrictions instead of changing device settings.
Specific requests are easier to approve: archiving work you created, moving project material into an approved knowledge base, or retaining a document after a project closes.
Approaches to avoid
Do not disable security policy to reveal a button, upload a company document to an unknown online converter, or use another person’s account to export content you cannot access.
A screenshot may show text, but it loses formulas, links and attachments and is still governed by confidentiality rules. A different file format does not create a new permission.
When to use the platform’s native export
If a spreadsheet, presentation or attachment has a legitimate native download path, use it first. The native route understands the source format and leaves a clearer record of the action.
Use a browser extension for documents you can legitimately access and need to organize into Markdown. Its job is efficiency, not expanding access.
The key is to separate a technical symptom from an authorization fact. Confirm what you are entitled to access, request it through the right channel, and choose the tool that matches the permission you actually have.