You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, name groups and filters (/api/name_groups, /api/filters) can be edited (put, post, delete) by any logged-in users, without special edit permissions. I think this needs to change, the question is whether we use the same permissions as for primary objects, i.e. Contributors can add, Editors can edit and delete, or different ones. Custom filters are a special case as they are not specific to a tree but shared for an entire Gramps installation, stored in an XML in the config directory rather than the family tree database.
The text was updated successfully, but these errors were encountered:
DavidMStraub
added a commit
to DavidMStraub/gramps-webapi
that referenced
this issue
Mar 10, 2023
Currently, name groups and filters (
/api/name_groups
,/api/filters
) can be edited (put, post, delete) by any logged-in users, without special edit permissions. I think this needs to change, the question is whether we use the same permissions as for primary objects, i.e. Contributors can add, Editors can edit and delete, or different ones. Custom filters are a special case as they are not specific to a tree but shared for an entire Gramps installation, stored in an XML in the config directory rather than the family tree database.The text was updated successfully, but these errors were encountered: