Unify storage and ownership of team-related apps

[alimmroth]

Tip

Help move this idea forward

• Use the 👍 reaction to show support for this feature.
• Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
• Subscribe to receive notifications about status changes and new comments.

---

This is an overview ticket for unifying the storage and ownership of team-related apps

Proposal

The collaborative apps that are mostly used by teams should move closer together and be less user-bound. This involves:

• Allowing team-folders to be more tightly linked to a team
• Moving the data into a central, consolidated .appdata directory per team
• Allowing all collaborative resources to be owned by, or assigned to a team (like collectives are)
• Separating resources that are owned by a user, or a team

Pieces

Team-Space (Linking team-folders to teams)

At the moment, team folders aren't really linked to a team, other than te ability to give teams permissions to them. For team-resources to live in a team-folder, one (and only one) team-folder should be assigned to this team.

• Make team-folders actually linkable, or assignable to a team groupfolders#4909

Centralizing storage

Having the data in one place, like an .appdata directory inside a team-folder, the directory structure becomes more clear and quota get's manageable. Everything outside this hidden folder could be freely used by the team members.

• Store all team data in a team-folder circles#2637
• Allow a single team-folder to be assignet to a team as it's main storage circles#2643

Allow resources to be team-owned

Until now, Collectives and groupfolders arethe only apps that are designed to be completely team-oriented as they don't have an owner. Having other resources like decks, calendars, etc. be owned by users creates many problems in organisations, like the need to have functional accounts to prevent data getting stuck when employees are unavailable or have left the organisation.

Individual tickets for each app needed

• Deck
• Calendar
• Tables
• ...

Move user-owned data into their home directory

If a user, on the other hand, wants to have a collective for their own, it doesn't need to (and shouldn't) be stored outside the users home directory. At the moment, when a user creates a collective, or deck, they can circumvent their quota limit, which actually does create problems and uncertainty for administrators.

Data from apps that are owned by a user could be stored in a consolidated directory, mirroring the same structure as proposed for team-related data:

<User-Home>
	.appdata
		Collectives
		Deck

When a user transfers the ownership of this resource to a team, the folder could be moved into the .appdata folder of that team. This way, quota limits and ownership of files alway have clear boundaries.

[marcoambrosini]

Closing as the main overview issue for the Teams vision will be posted soon. Everything in here is already available in sub-issue, right @alimmroth ?

[alimmroth]

Closing as the main overview issue for the Teams vision will be posted soon. Everything in here is already available in sub-issue, right @alimmroth ?

Yes, correct :)