Permission or restriction to linked resources for shared tables
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Hello!
So I'm working on a table to be used as a kind of overview of incoming, ongoing and finished project for a small team of freelancer. Column type Link is great for that as we can enter contacts, decks, collective pages and so on.
Now the thing is if for a example I enter a contact that only I have in any of my addressbook others won't be able to open it. Same goes for any other ressource.
So not being a developer I can imagine to solutions: restricting the available options in columns with the type link to certain ressources or automatically share a linked ressources with all users/groups the table is being shared with.
Maybe there are other solutions?
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
No files or tests are named. Start by tracing how Link columns resolve contacts and other resources, then inspect how shared tables and user or group permissions are handled. Define the intended behavior for inaccessible linked resources before determining what would count as complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100