-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Labels
Area: AuthAuthentication and access controlAuthentication and access controlWaiting for: ImplementationAdded to a milestone, will be resolved according to the milestone timeline.Added to a milestone, will be resolved according to the milestone timeline.
Milestone
Description
- There is a dummy
announcement.deletepermission.weblate/weblate/auth/permissions.py
Lines 530 to 531 in 6a5a25c
@register_perm("announcement.delete") def check_announcement_delete(user: User, permission: str, obj: Model):
I think that permission should either be merged with theannouncement.addpermission or converted to separate real permission.
It grants the permission based on the announcement scope, but the question is how much is that used. Anyway, component scoped team with the announcement.delete permission would work as replacement. It just needs to be documented, as this is not something we can easily handle in the migrations. So probably having a real announcement.delete permission is a way to go.
Make announcement.delete a real permission and add it to translation coordinator role.
Metadata
Metadata
Assignees
Labels
Area: AuthAuthentication and access controlAuthentication and access controlWaiting for: ImplementationAdded to a milestone, will be resolved according to the milestone timeline.Added to a milestone, will be resolved according to the milestone timeline.