Team setting: enable/disable sharing of team resources
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Is your feature request related to a problem? Please describe.
When a team owns resources, like a team folder, collective, deck or others, it would be good to have the option to ensure all access is 100% mediated through team membership. This simplifies the task of keeping a clear overview of access rights. Many larger organizations have arranged their access control along team lines.
Describe the solution you'd like
At a team level, you can disable sharing of team resources outside the team. This should be split out for:
- internal shares
- federated shares
- public link shares
Discussion
Of course, a follow-up will be: can we allow resharing only for team owners/admins? For this, see #2646 - team member roles (read/write, (re)sharing).
I suppose that for the Team it would just be a flag, while apps then have to respect that. Maybe the unified sharing can play a role here.
When you restrict sharing of any of the options, what do we do? Options:
- Check if any of the Team's owned resources are currently shared. If they are, give a warning and don't allow disabling the sharing.
- Follow what ACL's do - all existing shares stop working if you disallow sharing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how team-owned resources and unified sharing are represented, then read the related discussion in #2646 about team member roles. Done means a team can independently control internal, federated, and public-link sharing for its resources, with the handling of existing shares decided and enforced consistently by affected apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100