Assign task to Organization Member without becoming Plan Member
When you assign a Task to an organization member it becomes part of the Plan/Group.
We should be able to assign Tasks to people but to limit their view to that task only.
Damon Betlow commented
Is this still an issue? Unable to reproduce...
This is a must have functionality.
Diego Valverde commented
Any news about this topic?
The planner needs this functionality urgently!
Ahmed Maamoun commented
plan manager should assign the group members modification abilities whether they can or can't modify tasks assigned to them.
I had plans to implement planner in my organisation, but for security reasons I can´t because an accidental delegation of a task to someone outside of the Team would give this someone full access to everything within the Team.
For me, to deploy planner in my organisation, I need to be able to do one of two things:
1. The person who receives the delegated task will not automatically get full access to the Team
2. Tasks can only be delegated to persons within the Team. If I must delegate a task to someone outside the Team I will have to manually add that person to the Team first.
Hoping for an option to solve this as planner is a great tool I really want to use
Wil van Dijsseldonk commented
Yes please. With this feature planner will be a perfect tool to delegate tasks between teams, departments,etc etc
We really need this as well. Several teams are not supporting the product because of this functionality. Barron's comment is spot on.
Currently only the O365 Group Admin can assign task to anyone in the organisation. Group member can only assign task to any group member. The admin user UI could have a warning pop up in the case when task is assinged to a person who is not member of the group. The pop up warning should inform the owner that the person the task is asinged will be given member access to the entire group/Team
Barron Fuentes commented
Consider this use case:
Software development team is finishing up development on a project and is ready for QA. Software development manager assigns the QA task in the project planner to the QA team resource. QA resource completes their task and marks as complete. Software manager has visibility that the project has passed QA and can proceed to the next steps.
The QA resource only ever sees their QA task for the project and doesn't have access to all of the software development team documentation / planners.
Software development manager does not see the QA resource as a permanent team member when assigning tasks & reviewing resource allocation.
Alex Ramirez commented
I find Planner to be very powerful, but I feel very limited when wanting to assign someone a misc. task that is part of the bigger picture and the only way to do it is to give them full view to stuff that they don't need to have access to.
Billy Towers commented
I'm in agreement with all the comments posted here. If adding assignees to a planner task, I'd think either one ought not be able to add people who are not group or team members, or if doing so would add these other people as team members automatically, a warning should occur. Best is to be able to add assignees without them having access to other tasks.
Catherine Hardie commented
Please correct this issue, if you want someone to be a member if the Team, you should do the actual add member
We have a group for a management board and obviously management can assign tasks to any employee of the company. Due to confidentiality of some tasks and due to confidential documents in this group, it's important to assign tasks without granting any other permissions for this Plan/Group.
There could be an option in Planner that new members can be added only in Groups settings. In this case assiging a tasks to non-members won't lead to adding them as Plan members.
Yes please activate this. It is unnecessary that the task assignee becomes part of the team. Especially if they are outside the organization.. e.g an electrician booked for an office fitout does not need to be involved in the whole collaboration.
Agree. This cannot be working as intended! You should never be able to add a member to a Team (or Planner group) "accidentally," i.e. without *knowing* that you are adding a member! Our teams stay small, but they're matrixed, so all Teams used shared resources and shared services, which requires assigning planner tasks to people outside their Team. It is not practical to have a planner for INSIDE and a planner for OUTSIDE the team.
Aniele Pereira Pires commented
It would be perfect to be able to assign tasks for any outlook user and not only for plan members. Reason: secrecy of plan information.