Help regarding permissions on sharing a deck card. The tag field is grayed out.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Hi to all you good people out there. Sorry if my English spelling is bad I never had a teacher :).
I need help regarding deck sharing. I came to an idea that our bookkeeping office can use the deck option for the problem my company is facing. We need some sort of sharing a received invoice with engineers on field that can confirm that the shipment of goods form an invoice is correct and to give us the date for paying.
The sharing system from deck is awesome, but I would like to make it more secure with locking the features that they don’t need so they can’t make a mess and delete or change name or archive the card shared to them to review. So when I share a board with colleague I purposely don’t check the can edit field (see attachment no.1) . Instead I only need them to see attached file, give a comment and change tag from undone to done. The problem I am facing is that when I disable can edit options the TAG field is greyed out. Can you somehow help me resolve this and only unlock the tag field for the user that has shared card (see attachment no.2).
It would also help (not necessary) if I could have an option to print the attached document with comments given on the second page or somewhere in the header or footer. Again it’s not necessary.
I want to thank you for your spent time reading this topic and hope that its possible to set this form me. Wish you all the best. Momcilo from Serbia.
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 the deck sharing permission behavior described in the issue and compare the Admin and User screenshots. Determine whether users without edit access can be allowed to change tags and add comments without renaming, archiving, or deleting cards. Done means the requested permission separation is defined and verified, including its effect on shared cards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100