When you create another link for the same document, it is easy to expect it to behave like the previous one. The document and owner are the same, so the settings may feel as though they should be the same too. Distribution problems, however, do not come only from unfamiliar features. They also occur when a team assumes that old conditions still apply without checking the new link’s actual state.
The safe operating principle is not to memorize that settings “always inherit” or “never inherit.” It is to match the purpose of this link with the sharing settings currently shown for it.
Write the distribution purpose before creating the link
Record the audience and use case before naming the link. A limited investor review, a public introduction on a website, gated material that collects contact information, and recipient-specific tracking can use the same document but require different operating conditions. The purpose statement should answer: who needs access, for how long, and what should they be able to do?
Only then decide whether downloads are allowed, whether an access window is needed, whether notifications are useful, and whether an email allow-list or password should be used. Choosing settings first and adding a rationale later encourages teams to repeat an old link by habit.
Keep internal permissions separate from external link settings
FeatPaper folder permissions determine which teammates can find and manage a document in the dashboard. External viewers follow the settings of the specific sharing link. A change on one side does not verify the other.
Link-level sharing settings can include viewer type, PDF download, viewing period, document-view notification, and access restrictions. Access restrictions include an email allow-list and a password. The official guide states that the email allow-list and password apply to that link and do not carry over to other links. Do not generalize that narrow rule into an unsupported claim about every setting. Read the value currently displayed for each new link.
Treat download and viewing period as distribution conditions
Allowing downloads changes the boundary between online viewing and retaining a file. When download is disabled, a viewer using that link can view the document but cannot download the original PDF from the viewer. The control is available on Pro plans and above, so confirm whether the current plan can change it.
A viewing period limits when the link can be opened. After the period ends, the link no longer opens and an expiration notice appears. Changing download settings later does not recall a PDF already saved elsewhere. That is why “download disabled” must not be described as complete prevention of unauthorized sharing or a guarantee of confidentiality.
Assign an owner for notifications and access restrictions
When deciding whether to enable view notifications, also name the team that will receive them and how often the queue will be reviewed. An enabled switch does not create an owner. Space-level rules such as an interest threshold and cooldown may also affect notifications, so compare the link settings with the team’s notification policy.
If you enable an email allow-list or password, decide how recipients will receive instructions and who will handle failed access. A password does not replace recipient verification, delivery-path decisions, access periods, or closing procedures.
Define the deactivation trigger before distribution
If the team does not decide when a link stops being useful, it may remain open by inertia after a review ends. Choose which event triggers a deactivation review: project completion, recipient change, misdelivery, or replacement with a new version.
FeatPaper distinguishes disabling or re-enabling a particular link from stopping sharing for the document as a whole. Accumulated analytics remain when a link is disabled. A person must choose the appropriate scope for the event; do not assume that every external link closes automatically.
Record proof of checking, not just planned values
Each link register row can include the document, link name, audience, purpose, download rule, viewing period, notification rule, access restriction, distribution date, deactivation trigger, and owner. Add a verifier and verification time so the register becomes evidence that the settings were actually checked.
Immediately before distribution, an authorized editor reads the sharing values on screen and compares them with the register. If needed, test an allowed and a disallowed path separately. Do not turn this record into a claim of certification, completed audit, or legal compliance.
Managing new links well does not mean selecting the same boxes every time. It means deciding conditions for this audience and purpose, checking the current settings and closing responsibility, and only then distributing the link. Treat each new link as a small distribution approval, and settings drift becomes a verifiable operating problem rather than a guess.
