The elegance and power of tools like quire are really due to the endless nesting. So really the features of a project and task should be combined so that no matter what level you are in the nested outline you can do the same things. For example I’m a 4th level deep in a task string. I would still like to decide if I want to who can and can’t access that level and share that level with others. Any level could inherit the members and permissions of the level above it but could be overridden if needed. Every node should have all the features of a project and a task. This is the main bueuty and magic of the endless nested node model. My opinion is that a single “project” level just doesn’t cut it for complex goals.
Hi Steve, If you want to members to access a certain level of task but can’t access the others, you could probably check out our “External Team” feature. (This is normally for assigning teams that are outside of your projects) For example: If I added someone as an external team on one of my 4th level task, he/she only has access to that particular task, and the subtasks you added underneath that task (5th level and so on). Note: once the member is added as an external team in a project, he/she couldn’t be assigned tasks in that project as a normal member. Here are the instructions on how to create an external team. Hope this helps. Thanks.
Peggy, May 9, 2019
Hi Peggy, Yes, I should have perhaps called it 'Nested Projects' The idea is that you could have projects within projects within projects... so you could really for example start off with a project called 'Marketing' and have many projects underneath it for different marketing initiatives. The features of projects like setting or changing permissions, sharing, and so on would all be available, This is the way the outline structure should work so you could have endless levels that all have similar project style features as well as the task features combined. All subitems and subprojects under the main project could start off inheriting the parent project permission but could be overridden at the sub-project level.
Steve Davis, May 14, 2019
Hi Steve, to my understanding, please correct me if I am wrong, basically, you would like permission control to the task level. I will pass your suggestions to our team and we will discuss more on this. Thanks. 👍
Peggy, May 14, 2019
Hi Peggy. What about if I just want to assign different internal members to different “task” level projects? 99% of the time it would just be different internal team members for different task level projects. It’s ok if lll tasks inherit the main project level permissions but I’d like to override with specific member permissions in some cases.
Steve Davis, May 9, 2019