Allow "admin" users to edit labels they don't own
#1120
Open
opened 1 year ago by agichim
·
6 comments
Loading…
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
Could you elaborate this a bit more? Currently, there's not even the concept of an admin user. Also, wouldn't this extend to other things as well like lists, tasks, etc?
Hi,
So I'm thinking there could be global settings/features that can be editable by any kind of user or users with specific permissions.
There is a concept of an admin user. Following are two screenshots:
Regular users can be made admin within a "Team":

Regular user can be given 3 types of access to a "List"

Currently, if a "non-admin" user creates a tag, me as an Admin user can't edit that tag, but I can edit comments posted by other users. In the latter case, I shouldn't be able, no one should be able to edit comments, those should be "non-editable 100%" by anyone save by the user that created/posted the comments.
What is the different currently between Write and Admin permission?
Yes, it could extend to other things as tasks, lists, etc. It's matter of mulling over what should be globally edited and what should not.
Admins can edit the sharing options or the team itself, users with write rights only can edit or create new tasks.
I'm thinking that when a Team is assigned to a list, anyone on that team can edit anything, except for comments and perhaps Namespaces, but the users or Team can be given the right to edit by the user who created the Namespace.
What do you think?
You mean instead of bundling the rights for a list or related items under "can write everything" allow setting them individually?
Nevermind, it was my fault. My colleague didn't make me admin of a Namespace.