Basic priviledges would allow or lock users out from editing, adding and deleting templates/groups.
Such edited/added/deleted templates/groups could then be marked as user's drafts and also EXPORT to auto-imported XML, so that the changes are not lost on startup for the user.
All the changes could be then imported to master profile who manages those templates (as per issue #419 ) -- hopefully without damaging the original content and only suggesting a deletion, an edit or an addition. Whatever then is confirmed or rejected gets auto-exported to related XMLs and on the next opening of the Thunderbird is imported to user's client.
Basic priviledges would allow or lock users out from editing, adding and deleting templates/groups.
Such edited/added/deleted templates/groups could then be marked as user's drafts and also EXPORT to auto-imported XML, so that the changes are not lost on startup for the user.
All the changes could be then imported to master profile who manages those templates (as per issue #419 ) -- hopefully without damaging the original content and only suggesting a deletion, an edit or an addition. Whatever then is confirmed or rejected gets auto-exported to related XMLs and on the next opening of the Thunderbird is imported to user's client.