I think it is super critical that there is an ability to manage members at the account level as well as at the organization and project levels.
The main reason is if a member is part of mulitple 'organizations' it would be very tedious to go in and remove the person from every organization and/or project one by one. If a person is no longer with the company, it should be easy to go to an Admin Panel and just 'remove' the member, and your software should automatically remove them from shared tasks, and create a new 'Project' called 'Previous User <email address' that contains all their tasks which were not shared with others so nothing gets lost.
If this feature already exists please let me know how it works. If it does not exist, please make this a high priority item. For corporate security, it is critical to make it easy to manage users and permissions globally across all organizations and projects they are involved within the company.
If this feature already exists please let me know how it works. If it does not exist, please make this a high priority item. For corporate security it is critical to make it easy to manage users and permissions globally across all organizations and projects they are involved within the company.
There is a very popular task manager alternative that Quire offers migration from that has this kind of set up so users can be added and removed easily and tasks are automatically preserved.
Bulk reassign of tasks in the case of corporate restructuring is also critical so please recommend how to bulk reassign tasks and projects from one person to another.
Thank you.
Thank you. I appreciate the suggestions. I would highly recommend the same methodology as the other company I mentioned that is one of your psuedo competitors. They have very efficient bulk reassign methods and also a systme where if someone gets deleted all of there tasks get migrated to a project under their name - previous user John Doe tasks for example.
Steve Davis, May 8, 2019
Hi Steve, Thanks for your feedback. I think your suggestion of manage members at the account level makes sense, I will pass it to our team.
I have also mentioned below in your Getting Started comment: The best way to set up when you want to manage at the overall company level would be having one organization and creating multiple projects underneath. Then you could choose to add members to the organization level or the project level. If you want the member to see all the projects in one specific organization, you could just add the member in the organization level as āLimited+ā. Hereās a blog post to help you understand more about our roles and permissions. Hope this helps. https://quire.io/blog/p/Roles-&-Permissions-in-Quire.html
FYI, just a little tip, you can multiple select (press Shift and select tasks) and assign tasks at once, but this only works when in one project, it couldnāt be done cross projects.
Peggy, May 7, 2019
Yes, that would be good, but another additional important method is to somehow 'park' the tasks as dumping them all on another member would overwhelm and stress out the other member. What one of Quire's competitors does which is great is as follows. If you delete a member, automatically all that memmbers tasks get placed in a new project called '<first name last name> previously assigned tasks so that no tasks are lost and they can be reassigned as needed to other team members. Another key point and benefit of this other software tool is that tasks can be associated with multiple projects so in the case above for example... if a deleted member had a task in the 'marketing' project, it will still be in the 'marketing project' after deletion of the member; but would also appear in 'Bob Jones previously assigned tasks' project as well. Its a great solution and one that Quire should definitely adopt.
Steve Davis, May 9, 2019
Hi Steve, thanks, what if having a feature: after removing a member from an Organization, there will be an option for the user to reassign all the tasks of that member to one new assignee. Will this be helpful in this case? š
Peggy, May 8, 2019