Repository navigation
[FEATURE REQUEST] Sharing NG: List existing links #4956
Description
Listing links by fetching them from server
GET https://<url>/graph/v1beta1/drives/<drive-id>/items/<item-id>/permissions
(same as shares)
A list of links is available in the object values like:
{
"createdDateTime": "2026-08-19T11:55:13.45495517Z",
"hasPassword": true,
"id": "IAfiUVqqpslHpNK",
"link": {
"@libre.graph.displayName": "test",
"@libre.graph.quickLink": false,
"preventsDownload": false,
"type": "edit",
"webUrl": "https://<url>/s/ioRkTIB9VDNKzxy"
}
},
It should be displayed in the same way as the spaces' links
- Name of the link -> first row
Below:
- Permission
- Expiration date (only if exists)
On the right, the chain icon that shares the link
edit and remove, in the following issues.
Small issue to fix:
The warning under the PUBLIC LINKS header states:
Anyone with the link has access to the space
it should be
Anyone with the link has access to the file/folder
TASKS
- Research (if needed)
- Create branch feature/list_public_links_sharing_ng
- Development tasks
- Render public links in the Sharing NG panel
- Implement the chain icon for sharing the web url
- Adapt the warning message
- Refactor public links adapter and other classes used in spaces
- Implement unit tests (if needed)
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/list_public_links_sharing_ng into master
Activity
joragua commentedon Oct 14, 2026
Spec:
Problem
The Sharing NG flow does not display existing public links for files and folders, leaving users with no visibility over links that were previously created from any client. Additionally, the warning text under the PUBLIC LINKS section incorrectly refers to "the space" instead of the specific file or folder being shared.
Desired behavior
When a user opens the sharing panel for a file or folder, all existing public links for that item are retrieved from the server and displayed in a list. Each link shows its name, its permission level, its expiration date when one exists, and a share-link action. The warning text under the PUBLIC LINKS header correctly references the file or folder rather than the space.
User stories
Constraints
Acceptance criteria
Out of scope
Assumptions
The app already has a working integration with the Graph API permissions endpoint (used for shares), so public links can be fetched from the same response without an additional network call.
The spaces' links UI (issue [FEATURE REQUEST] List links over a space #4752) already exists and is reusable as a layout reference.
The item's
drive-idanditem-idare available in the sharing panel context.Links must be fetched from the Graph API endpoint: GET /graph/v1beta1/drives/<drive-id>/items/<item-id>/permissions (the same endpoint used for shares).
The Graph API permissions endpoint returns a
valuearray where public links are identified by the presence of alinkobject. The fields available on each link entry are:idStringcreatedDateTimeString(ISO 8601)expirationDateTimeString(ISO 8601)hasPasswordBooleanlink["@libre.graph.displayName"]Stringlink["@libre.graph.quickLink"]Booleanlink.typeStringeditdisplayed asCan edit.viewasCan view.createOnlyasSecret file droplink.preventsDownloadBooleanlink.webUrlStringMap response fields to UI:
link["@libre.graph.displayName"]→ link name,link.type→ permission label,expirationDateTime→ expiration date row (omit if absent),link.webUrl→ URL shared by the chain icon.hasPasswordis present in the response but out of scope for this issue; consider carrying it in the data model for use in a future edit flow.The warning text fix must be conditional on whether the target item is a file or a folder.
Implementation notes