generated from layer5io/layer5-repo-template
-
Notifications
You must be signed in to change notification settings - Fork 128
docs: update sharing and visibility sections for designs and workspaces #708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kirti763
wants to merge
6
commits into
layer5io:master
Choose a base branch
from
kirti763:update-sharing-visibility
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1af0f1d
docs: update sharing and visibility sections for designs and workspaces
kirti763 ec94a0f
Update content/en/kanvas/designer/sharing/index.md
zihanKuang d9e9bbf
alert box 1
kirti763 dea58e4
add 2nd alert box
kirti763 6f0f67d
Update content/en/kanvas/designer/sharing/index.md
zihanKuang 32e3ce8
clarify sharing options, fix link
kirti763 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,7 +21,13 @@ Designs have visibility statuses that defines who can access your designs. These | |
|
||
- **Private:** Designs with visibility status private define only you, the creator, and the user or team that have access based on granted access permission can view and edit the design. Other users cannot access it unless you explicitly share it with them.[^1] | ||
|
||
- **Public:** Making a design "Public" makes it accessible to anyone on the internet who has the link or discovers it through public channels. By default, users accessing a Public design are granted permissions to view, comment on, and edit the design. | ||
- **Public:** Making a design "Public" makes it accessible to anyone on the internet who has the link or discovers it through public channels. | ||
|
||
{{< alert title="When a design is Public" type="info" >}} | ||
- Viewers and commenters can view, download, print, and copy the design. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you please clarify what "print" refers to here? Is it an action, and if so, does it correspond to a specific button? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👀 |
||
- Editors can change permissions and share the design with others. | ||
- This permission model applies to all public designs in Layer5. | ||
zihanKuang marked this conversation as resolved.
Show resolved
Hide resolved
|
||
{{< /alert >}} | ||
|
||
{{< alert title="Why use public" type="info">}} | ||
Public status is useful for sharing designs broadly, for example, as open-source templates, public demonstrations, or for soliciting feedback from a wider community. If your goal is to share broadly only within your organization, consider using a combination of private designs shared with specific organization-wide teams or workspaces. | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The jump link is missing:
/kanvas/designer/publishing-designs/
Regarding the phrase "publish the design then create a link to share to people with access"—could you clarify this? My understanding is that a published design is accessible to everyone. What does "people with access" refer to in this context if it's already public?
Could you explain "When a design is published (made public)"? I've tested publishing designs that are set to private, and the outcome regarding their published status and permissions seems to be the same as publishing public designs. It appears the private/public setting doesn't affect the published state.