Repository navigation
Description
Our current ways to manage, organize and distribute file templates is a wild mix of old code and not very accessible to admins and end users.
The server provides the possibility for a user defined directory but there is no option to change it or see which folder that is.
Additionally templates that we ship are only copied on user creation, so existing users will not get updated or new templates.
Collabora has additionally a separate config option for a user template directory and an admin Ui where admins can define instance wide templates:
Especially in larger organizations, defining and updating templates on the admin level is quite important, but also for us shipping new templates regularly this would be better way as currently those templates only reach new users.
My proposal to clean this up would be:
- Add a folder picker to the files settings modal so users can have a fixed way to set, update which folder is used as their personal template directory
- Add a special icon to show for the folder that is the current user template directory
- Add an admin settings section where admins can upload and manage template files that are exposed to all users in the template picker dialog
- Remove the Collabora settings as they get obsolete with the server ones
- That way other apps like text can also make use of this
Open questions:
- Should users be able to opt out of admin defined templates?
- How do we want to handle our default templates?
- It probably makes sense to add them as system wide templates
- However then users cannot adjust them on their own unless there is an opt out
- Admins might still want to remove them, maybe it is the best to just have a checkbox to include shipped templates or not?
@nextcloud/designers for feedback
FYI @sorbaugh as it touches the area of files
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fields🧭 Planning evaluation (don't pick)
- StatusShow more project fields🧭 Planning evaluation / ideas
- StatusShow more project fieldsBacklog
Activity
juliusknorr commentedon Jul 31, 2024
To be evaluated additonally:
juliusknorr commentedon Oct 17, 2024
From discussion with @jancborchardt
Would be covered by the above
Can be handled by admin delegation
Could be done by an extra Templates folder for each collective/groupfolder but as a next step.
jancborchardt commentedon Oct 23, 2024
Just talked about this a bit with @nimishavijay and there are 2 specific issues we came across:
joshtrichards commentedon Nov 23, 2024
Good stuff! Sounds like this work will effectively cover #38198 and #25358 (including most of the follow-on comments therein).
User-level templates would still be derived from a user owned/controlled folder in the proposed design. At the admin-level, they'd manage (upload/etc) templates via Admin settings. And users don't need to be able to edit the system provided templates.
I'm not sure how we'd handle folder specific templates, unless we started classifying folders... Wait, maybe we could associate templates with certain tags?... That would create the affiliation desired. Then the New button would activate for templates tagged the same as the folder the user is in.
7 remaining items
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
fix: Hide "Create templates folder" option if templates are disabled …
juliusknorr commentedon Sep 24, 2026
I started two pull requests in that regard: