Skip to content
Interface language: English
Design / Signal

“Anyone with the link” is also a design decision

Design a sharing flow that makes recipients, roles, expiry and revocation understandable.

Article language: English

Two people beside a table in front of a large circular structure overlooking a landscape.
In this article

“Copied.” That reports the clipboard. It does not explain whether the recipient can open the file, must request access or whether forwarding the address lets another person see it. The button works correctly, yet the user still does not know the effect of the decision.

A sharing design should show that effect before confirmation. Giving a route to material and changing the set of authorised recipients have different effects. In daily work both fit under “send”. The interface should distinguish them without a lecture on authorisation systems.

Three intentions behind one button

Consider a hypothetical exhibition-design studio. Natalia wants to send an approved drawing to a manufacturer. At another time she gives a colleague the address of a document both already access. Later she prepares a public preview of an arrangement for event participants. These are three different audiences, although a link can be pasted into a message each time.

First establish which actions the product supports. Passing an address to people with existing access should not suggest new permission was granted. Inviting a specific person requires identifying them. An option available to any link holder must explain that the address can be forwarded. This distinction helps users; actually enforcing it remains the system's job.

Microsoft distinguishes a link for people with existing access, which changes no permissions, from one for selected recipients. In the latter case forwarding does not give a new person access unless they already had permission. This is an example of different meanings of copying an address in SharePoint and OneDrive.

Our portal might name an action “Copy address for people with access”. For a file without recipients, “Other people will request access” helps if the implemented path actually behaves that way. Do not automatically turn the action into public sharing merely to reduce later questions. That would solve an opening problem by changing access rules.

Also define when a change is saved. Does choosing “Anyone with the link” apply it immediately or only after “Apply”? If Natalia closes the window, she should know whether the previous state remains. A pending-change summary and clear confirmation button can help. If the interface saves immediately, it needs confirmation after the system responds and a predictable way to reverse the change. Copying should not conceal an undescribed mode change.

“Anyone with the link” should describe recipients in an ordinary sentence: “Anyone who receives this address can open the document, including if it is forwarded.” If an account in a particular organisation is required, say so. “Anyone” without that distinction can promise access to an external manufacturer who cannot obtain it.

Google Drive help describes restricted access and an anyone-with-the-link option that opens without Google account sign-in. It also notes that an organisation may restrict external sharing. This example does not mean every application must provide identical modes. The user-facing name should match the product's actual rules.

Show recipient and role together

For an invitation show the address, not just a friendly contact name. Two people can share a first name; one person can have personal and company accounts. After selecting a suggestion Natalia should still see which address receives access. The recipient list supports checking the decision, not merely faster typing.

Show the role beside the person or clearly beside the entire specified group. “Can view” and “Can edit” describe different capabilities. If commenting exists too, name it separately. Explain actions particular to the product: whether editing concerns drawing content, changing the file description or only adding notes.

The selected role describes the permission granted in this operation. The recipient may already have broader access through another route, such as a group or folder. If the system can determine their actual access, show it and the source of any broader permissions within the limits of what may be disclosed. If it cannot, do not assure the user that the selected viewing role is the recipient’s only permission.

The initial role should fit the path's purpose. In the approved-drawing example, the manufacturer needs viewing. Do not give editing simply because the last invited colleague had that role. If the product remembers a prior choice, show it clearly before confirmation. A user may share for different purposes; convenient repetition should not hide a new recipient capability.

When inviting several people, do not hide role differences in “Added 4 people”. The manufacturer may need viewing while a colleague can add comments. A shared setting is convenient when genuinely shared. After an individual role change, the summary must show the exception before confirmation.

If groups are allowed, show that a group is the recipient. Do not present its name as one person. A material owner may know the team name but not current membership. Depending on the system, a way to inspect members or an explanation of who manages the list may be needed. Do not show an apparently exact count when the product lacks current membership data.

Sending a notification is another separate action. Access may be granted even when no message was sent, or a message may not arrive. “Save access” is more honest than “Send” if the screen sends no invitation. Conversely, after sending, do not show “Recipient read it” when only acceptance for sending was confirmed.

Aeneia conceptual photography

For a partial result preserve the recipient distinction. Suppose the manufacturer got viewing access, but the colleague's invitation was rejected by an organisation rule. Instead of a general “Could not share”, show both outcomes. Retry only the unfinished step if the system supports it. Natalia should not guess whether she must set every role again. Preserve entered addresses and chosen settings so correcting one error does not rebuild the entire decision. For another login, design return to an unfinished action after session expiry (in Polish). On return, show the confirmed change scope before another confirmation.

The recipient route should fit an invitation to collaborate and account choice (in Polish). The recipient may open a link in a browser signed into a different account. Instead of a generic “You do not have permission”, show which address was granted access if disclosure is allowed in that state. Allow account change without losing the invitation's destination.

When someone cannot share material, explain the available route. They may ask the owner to change recipients or copy an address for already authorised people. A grey button without explanation does not distinguish an organisation rule from a page error. The right next step reduces accidental copying of a file elsewhere.

These relationships can be mapped when designing a portal and messages with Aeneia Design. Start with actual roles and a material-flow example. That supports a summary of who can open the material, what they can do and whether the change is in effect.

An access end date needs its scope. Does one address expire, one person's temporary role, or the whole preview? “Until Friday” is brief, but across time zones a recognisable date and end rule are clearer. If the system sets only a day, do not invent a precise hour.

Google Workspace describes a case where inherited folder access remains after a temporary file role expires. Someone can, for example, lose editing while retaining viewing. Do not generalise that behaviour to every product. It shows why “the permission expired” and “the person has no access at all” require different messages.

In our example Natalia may revoke one manufacturer link while that person still belongs to a group with access to the whole project. The panel should reveal the distinction within the information made available to the owner. After link removal, do not show “The manufacturer has no access” if the system confirmed only removal of one entry route.

Moving material can also change its permission environment. Choosing a folder and sharing when moving files (in Polish) should therefore align with the sharing screen. The user should not receive an assurance of restricted access in one place, then move material into wider circulation without recognisable information about the effect.

When revoking sharing, show the change's scope before confirmation and the result after the system response. If the operation fails, retain the previous confirmed state. Do not remove a recipient from the list as though the change already applied and show a small error only later. The owner could close the panel believing access had ended.

Revoking access to the original does not automatically delete previously downloaded copies. If the portal allowed download, the message should concern access through that portal. Do not assure users that “The document disappeared from all recipients”. In an ordinary drawing flow, clearly identifying the current version and which copy was withdrawn is more useful. It lets a team respond without attributing remote control over another person's device to the interface.

Accept-test the whole flow, including forwarding

Prepare a neutral file and separate test accounts. An owner cannot test recipient access by opening an address in their ordinary session. Record the account used and expected result. A screenshot of an open document does not explain whether the intended recipient, another employee or an anonymous person saw it.

Follow the route from settings to the first opening. Then forward the same link to another account not selected as a recipient and compare the result with the chosen mode. Also check what a user sees after expiry or revocation. This is acceptance of an agreed configuration and communication, not proof of all security properties.

The file must remain recognisable as the right material. Name, version and use described in a download centre (in Polish) help the recipient assess what was opened. Correct access to an outdated drawing does not solve Natalia's task. The flow needs both the correct recipients and correct content.

Establish what happens after the drawing is updated. One link may always lead to the current version, while another preview may preserve an approved edition. In the fictional studio, the manufacturer should know whether yesterday's address will show today's correction. Name the option according to actual behaviour and put a version marker beside the content. “Shared” alone does not decide whether the recipient should follow later changes or work on a specific approved item.

When an address leads to another service, preserve predictable link opening and a route back (in Polish). The recipient should not confuse login to an external service with signing back into the portal. The destination's name and brief account requirement are more useful than a new-tab icon alone.

Finally return to the message after copying. “Address copied. The specified people with viewing permission can open the document” confirms a different decision from “Link copied for anyone holding the address”. Natalia should understand the difference before pasting it into a message. The clipboard need not be especially talkative; it merely must not omit a change in recipients.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear