Jack S.
🗑️It would be nice to have the option to prevent a given user from deleting anything.❌
.
Edwin Carrington
Is this still in progress? Seems to be very much getting left behind... this would be a major update that clearly many are eagerly waiting for.
How is this still "in progress" after nearly 2 years?
E
Edison Villamor
Any update?
Edwin Carrington
This has been "in progress" for way over half a year now – when can we expect this to be released? It's essential to our client management and having to give access to guests one item at a time is a real pain especially if you have a bunch of tasks lined up... Tony Pham
J
Jordan
This feature idea status is "In Progress" but I'm confusted...
Has there been some feedback, from the Upbase team, suggesting what these "Advanced Permissions" will be? Is there some open dialog somewhere, where customer needs are being discussed?
Jack S.
Jordan:
🤔
You can comment and submit ideas here.
Jack S.
You can also invoke Tony Pham from Upbase by typing @Tony Pham
K
Karim Mneimneh
Jordan: super low updates. Most new features aren't even essentials.. the dev team should seriously prioritize new features and fixing bug errors..
C
Chris Tucker
Tony Pham I understand and appreciate the simplicity ethos, but for any serious business to adopt this tool, Advanced Permissions are essential.
Jack S.
👍
C
Charles
This needs to be implemented and should be made a priority.
E
Edison Villamor
any updates on this?
M
Marcelo Oliveira
In a situation where each list/kanban is a project/client/department of the company and needs a team, I believe that a permissions system that would allow these roles would work very well in any type of business:
1-Admin - Business owner (does everything, manages workspaces, creates/invites users, creates/edits lists and defines the team of a list).
2.Admin - Assistant Manager (Business owner assistant, can't do everything, can't create workspaces, can't access My Settings/Workspace, can create/invite users, can create/edit lists and can set a list's team).
3-Member - Team Leader (Manages the list he was entered into, can create/edit/delete sections/tasks, can assign team members to tasks, will manage the team and ensure the project is completed successfully within the deadline, the leader cannot delete/archive the list).
4-Member - Team member (Will perform tasks and move them to the next step after completion, can check subtasks, can add information/comments to tasks but cannot edit or delete them, can be an employee in-house or a third-party virtual assistant).
5-Client/Guest (Can follow the process, without being able to change anything, can give information/feedback).
(*) Is it possible to block/suspend a member? Or just delete? If I withdraw or delete a member, what happens to what he has done up to that point?
D
Denis Dorigo
Marcelo Oliveira: https://upbase.canny.io/feature-requests/p/data-security-existing-data
K
Katerina Kuzi
Permissions are very important. This is why my client is not sure, if he should buy your SW. He needs 2 roles: 1. Admin (can do everything), 2. For employees: Can check / uncheck, comment, chat and move task between sections. He cannot edit or delete any task (including tags in it), project etc. So when my client give a task to his employee, employee can only view it, add comment and move it to another selection. Thanks.
Load More
→