Allow admins of a team to create / attach team folders

[alimmroth]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Feature

• There should be a button in the team-settings-page to create and attach team-folders to this team
• When adding the first team-folder there should be an info box alerting the user that the team-folder will become this teams main team-folder. This team folder is created with a hidden .appdata folder inside, where team-resources (like deck, collectives) will live in.

Main team-folder vs. "additional", or "attached" team-folders

For team-admins, it should be allowed to create any number of team-folders attached to the team

It should be allowed for admins, as it is right now, to give teams permissions for any team folder. Those are also showing up in the teams resource overview as additional / attached team-folders.

Related Tickets

• Allow a single team-folder to be assignet to a team as it's main storage #2643
• Team-owned resources across Nextcloud #2644
• Store all team-related app-data in a team-folder #2637
• Create team-folder when creating a team #2661

[marcoambrosini]

I don't think we should allow more than one team folder per team. Why do you think that would be necessary @alimmroth ?
If the reason is difference in access rights, I would suggest that the user create another team.

[alimmroth]

We have discussed this in the meantime and have come to the conclusion that for backwards compatibility and preservation of existing structures it should still be allowed to give a team permissions to several team- or group-folders (however they will be called in the future)

This would also allow to create folders that are shared storage for both teams and classical groups.

I don't think anymore, that this should be allowed to be done from the team-page itself, or by team-admins, so basically this issue could be closed.