Mar 24 2017 05:59 AM
I had an inquiry from a colleague asking if there is a way to restrict members of a plan to where they can't create buckets or move tasks around in different orders. I think there is an interest in having some members have read only access to look at the tasks in a plan and others who have access to create buckets and move tasks around. Is this possible or on the roadmap?
Mar 24 2017 06:20 AM
Mar 24 2017 06:40 AM
Mar 24 2017 07:19 AM
Thanks for the quick responses. It was a long shot on this request I realized.
Aug 18 2017 09:09 AM
Jul 30 2018 06:51 AM
Any further updates on this feature?
Also, any updates on access for only one bucket on a plan?
Jun 28 2019 11:00 AM
More than 2 years and this feature still not implemented? how come?
Jun 29 2019 05:00 AM
Jul 02 2019 01:09 PM
Jul 02 2019 01:18 PM
Jan 13 2020 08:53 PM
I found a solution to the read only situation!
If you make your plan public, you can simply send the url to someone and it will give them read only access. The only downside to making it a public plan is that anyone with the url can see the plan, but for us its a workable solution.
Mar 30 2020 08:18 PM
You're assuming I have administrative rights for the app itself. I only have control over my individual plans.
Jun 18 2020 12:13 PM
@Nick_V635 I was attempting this as I too share the same concern. I was able to close/Complete tasks. Could you share your process in doing this?
Oct 17 2020 03:28 AM
Feb 11 2021 05:57 AM - edited Feb 11 2021 05:57 AM
@ArekR88 I'm doing some alpha testing on it but it may be possible to set up restrictions by utilizing powerapps. you build your tasks through planner but present the tasks to the users using powerapps by using the planner connector in powerapps. from there you could provide which fields they have access to edit per task and delegate who has permissions to create tasks. Granted this will be a lot of work compared to other 3rd party solutions but it would be more flexible to getting exactly what you want.
Mar 17 2021 07:29 AM
@laminblake very interesting to read about this approach. Have you succeeded in your "alpha" tests?
Apr 01 2021 06:25 AM
@laminblake I'm interested in this approach as well. I need to create a method for users to submit a request (task) but not assign it or modify it once it is submitted.
Apr 01 2021 06:27 AM
@laminblake that's great but it's a workaround. They should be implementing this basic feature from the beginning.