cwtv
/
portier
3
0
Fork 0
Code Issues 8 Pull Requests Packages Projects Releases Activity

feature: Permissions #9

New Issue
Open
opened 2024-03-03 21:35:44 +01:00 by thunfisch · 0 comments
thunfisch commented 2024-03-03 21:35:44 +01:00
Owner
Copy Link

Currently, everyone that creates some config also owns it.

It would be cool to be able to share configs with other people. The Guardian Backend can in theory already do this, but it's not at all exposed anywhere in the system.

Think about being able to "invite" some other user to have control over some config object.

Should we differentiate between read and write access?

Can we delegate permissions to a "team"?

Currently, everyone that creates some config also owns it. It would be cool to be able to share configs with other people. The Guardian Backend can in theory already do this, but it's not at all exposed anywhere in the system. Think about being able to "invite" some other user to have control over some config object. Should we differentiate between read and write access? Can we delegate permissions to a "team"?
thunfisch added this to the Utility milestone 2024-03-03 21:38:02 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
wip/thunfisch
wip/vue-material
v0.8.0
v0.7.2
v0.7.1
0.7.0
0.6.2
0.6.1
0.6.0
0.5.0
0.4.0
0.3.1
0.3.0
0.2.0
0.1.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Utility
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtv/portier#9
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?