Feature Request working with multiple nextcloud users and multi tenant

[GVLLIFESTYLE]

Possibility to manage multiple Companies and allow users to read, access, change, write (permission modell) the data.

[SafetyIng]

1. you have account systems (companies or similar); these could be selected at the top where the overview is currently displayed
   
   or would be displayed one below the other as in NCmail (I would prefer the 1st option).

2. Account systems should ideally be created and managed via an admin page, as these may affect multiple and changing users. If employee/user XY leaves, it is unfavorable if the account is also deleted.

3. Access rights could then also be managed accordingly via the account system.
   This would be useful here:

• View allowed
• Input allowed
• Modify data/full write permissions

[SafetyIng]

An additional train of thought: You could also bind these elements to a group in the future, for example, and thus use a corresponding storage location for the attachments of a multi-element via the "groupfolders" app (compare here #43)

[powerpaul17]

What I get from this feature request is having multiple "ledgers", right? That would make sense (point 1).

Point 2 also makes sense, it should be possible to create ledgers as an admin (just like group folders) which cannot be deleted by a user.

[GVLLIFESTYLE]

Yes thats what I mean :) -------- Ursprüngliche Nachricht --------Von: Paul Tirk ***@***.***> Datum: 09.12.23 21:30 (GMT+01:00) An: powerpaul17/nc_money ***@***.***> Cc: GVL ***@***.***>, Author ***@***.***> Betreff: Re: [powerpaul17/nc_money] Feature Request working with multiple nextcloud users and multi tenant (Issue #42) What I get from this feature request is having multiple "ledgers", right? That would make sense (point 1). Point 2 also makes sense, it should be possible to create ledgers as an admin (just like group folders) which cannot be deleted by a user. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>