make visibility configuration more clear #151

New issue

Closed

opened 2026-09-01 15:14:51 +02:00 by qwc · 0 comments

qwc commented

2026-09-01 15:14:51 +02:00

Owner

custom means, no one except defined in Group Mappings can access that (meaning also people in the global access (private) category cannot until defined)

redesign visibility configuration!!!
move group mappings into project administration

Global access should be renamed to "Private Access".
Group Mappings should be renamed to "Custom Access" or move to project administration.

created an access list, and the accesslist dropdown stays even if private or public is chosen.

prove codewise that group mappings can be replaced by access lists.
make access list name and description editable.

custom means, no one except defined in Group Mappings can access that (meaning also people in the global access (private) category cannot until defined) redesign visibility configuration!!! move group mappings into project administration Global access should be renamed to "Private Access". Group Mappings should be renamed to "Custom Access" or move to project administration. created an access list, and the accesslist dropdown stays even if private or public is chosen. prove codewise that group mappings can be replaced by access lists. make access list name and description editable.

qwc added the

Kind/Security

Kind/Feature

Compat/Breaking

labels

2026-09-01 15:14:51 +02:00

qwc referenced this issue from a commit

2026-09-01 19:20:03 +02:00

Add the unified access schema: orgs, groups, grants (#150, #151)

qwc referenced this issue from a commit

2026-09-01 19:20:03 +02:00

Translate the old access model into the new one, provably (#150, #151)