docs: split data_link and data_link_object permissions (Cloud)#1601
Open
georgi-seqera wants to merge 3 commits into
Open
docs: split data_link and data_link_object permissions (Cloud)#1601georgi-seqera wants to merge 3 commits into
georgi-seqera wants to merge 3 commits into
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
georgi-seqera
commented
Jun 22, 2026
| @@ -0,0 +1,11 @@ | |||
| --- | |||
| title: Seqera Cloud v26.2.0_cycle61 | |||
Contributor
Author
There was a problem hiding this comment.
@justinegeffen I'm not sure how release notes for Cloud are handled - whether there is something automatic, but am just adding this update for when I would expect the change to be effective in prod.
Let me know if there is some different process I should follow or if you have a preference for how engineers should contribute release note docs.
More details can be found here: https://github.com/seqeralabs/platform/pull/11461#issuecomment-4768592011
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
justinegeffen
added
the
additional work req.
justinegeffen
added
do not merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documents the Data Explorer permission split shipped in seqeralabs/platform#11461 (PLAT-5313).
Platform introduced a new
data_link_objectpermission noun to separate two concerns previously conflated underdata_link:data_link— operations on the data-link record (list, describe, create, edit, delete, hide/show)data_link_object— operations on the files the link points at (browse, download, sign, upload, delete)This is a permission broadening: reading object content is now a read-level capability, so workspace members with view, connect, or launch roles can now download files and generate/sign download URLs. Upload and delete file operations remain restricted to maintain and above. Custom roles will be automatically updated.
Changes (Cloud docs only)
orgs-and-teams/roles.md— Addeddata_link_object:read(all roles),data_link_object:write, anddata_link_object:delete(owner/admin/maintain) rows to the role permissions table.orgs-and-teams/custom-roles.md— Re-mapped the Data section so each operation sits under its correct grant:data_linknow covers only record operations; newdata_link_objectentries cover browse/download/sign, upload, and file deletion.changelog/seqera-cloud/v26.2.0_cycle61.md— New changelog entry under Data Explorer.Notes
m155) runs automatically on startup and backfills custom roles additively.