You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Access control for share links (restrict to specific people / org / repo collaborators)
#1543
Hi! This is one of my first times posting a suggestion to someone else's repository, so if this isn't the right place or format for this kind of request, please let me know and I'll adjust.
Problem
Today whiteboard share produces a link that anyone can read. Per docs/privacy.md, the shared copy includes document text, full trace conversations, and the referenced source lines. For whiteboards built on private repositories, this means proprietary code and internal discussion are exposed to anyone the link reaches (forwarded chats, pasted into the wrong channel, browser history, etc.). share revoke helps after the fact, but there's no way to limit who can open a link in the first place.
Because of this, we hesitate to use sharing for work on private company repositories, even though it's exactly where it would be most useful for code review and design discussion within the team.
Proposal
Add access levels to shares, similar to Google Drive's model, so a share can be limited to specific people. For example:
Anyone with the link (current behavior, could stay the default)
Restricted to specific people, identified in whichever way fits the product best, e.g.:
GitHub-based: users who can read the pinned repository, members of a GitHub org, or a list of GitHub logins
Email-based: a list of email addresses
I don't have a strong opinion on GitHub vs. email. Either would solve the problem for us, and GitHub-based might fit naturally since recipients already fetch the pinned commits with their own GitHub access.
It would also help to be able to change the access level (and see who has access) for an existing share, not only revoke it.
Alternatives considered
Revoking links quickly after use: this only shortens how long the link is exposed.
Sending exported Markdown/files through internal channels instead: this loses the canvas, software maps, and traces that make shares valuable.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi! This is one of my first times posting a suggestion to someone else's repository, so if this isn't the right place or format for this kind of request, please let me know and I'll adjust.
Problem
Today
whiteboard shareproduces a link that anyone can read. Per docs/privacy.md, the shared copy includes document text, full trace conversations, and the referenced source lines. For whiteboards built on private repositories, this means proprietary code and internal discussion are exposed to anyone the link reaches (forwarded chats, pasted into the wrong channel, browser history, etc.).share revokehelps after the fact, but there's no way to limit who can open a link in the first place.Because of this, we hesitate to use sharing for work on private company repositories, even though it's exactly where it would be most useful for code review and design discussion within the team.
Proposal
Add access levels to shares, similar to Google Drive's model, so a share can be limited to specific people. For example:
I don't have a strong opinion on GitHub vs. email. Either would solve the problem for us, and GitHub-based might fit naturally since recipients already fetch the pinned commits with their own GitHub access.
It would also help to be able to change the access level (and see who has access) for an existing share, not only revoke it.
Alternatives considered
Thanks for building Whiteboard!
All reactions