Allow "admin" users to edit labels they don't own #1120

Open
opened 8 months ago by agichim · 6 comments
There is no content yet.
Owner

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?

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?
Poster

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":
image

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

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.

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": ![image](/attachments/d84104d3-cb13-48b0-b4f1-09cc26e746f9) Regular user can be given 3 types of access to a "List" ![image](/attachments/b43409e3-2f6c-45dc-89bf-8f54fa6f65cb) 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.
Owner

What is the different currently between Write and Admin permission?

Admins can edit the sharing options or the team itself, users with write rights only can edit or create new tasks.

> What is the different currently between Write and Admin permission? Admins can edit the sharing options or the team itself, users with write rights only can edit or create new tasks.
Poster

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?

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?
Owner

You mean instead of bundling the rights for a list or related items under "can write everything" allow setting them individually?

You mean instead of bundling the rights for a list or related items under "can write everything" allow setting them individually?
Poster

Nevermind, it was my fault. My colleague didn't make me admin of a Namespace.

Nevermind, it was my fault. My colleague didn't make me admin of a Namespace.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/api#1120
Loading…
There is no content yet.