Reduced downgraded and modified guest account as a customer account - some CRM and collabaration with customers

Christmas wish :-)

maybe most of these things are already possible? I do not know .... as a newbee. So please excuse the long descritpion of the use case...

If we use nextcloud for our business for internal stuff, the internal work and so on, every user gets an account,e verything is fine.

Some thigns might be worth sharing with customers, and it would be

• time saving
• look professional
• add to our processes
  if it would be possible to create an account, like the guest account, but absoutely isolated from other users, except definde ones, and not just a group. So he would be able only to share and see infromation with his defined customer service representative, and maybe some related other accounts (his Spouse and kids i.e.).

We work on documents, and collect documents, notes and todos that relate to our customers.
We would like to have a customer account that makes it possible to

• share only his data with him, and that he can not see any other contact or data
• he can see a calendar that only contains the appontments we had and plan with him
• tasks Todo list, with todos he has to complete
• tasks we do for him, so he can see progress
• deck/decks for bigger projects we do for him/with him so that he can see progress and the goals
• talk to make the communication possible
• mutiple Chats, to seperate issues, and with the option to close a chat finally and to set an alarm time on it
  The appearance of the account should be as simple as possible, and most things should only be readable, NOT editable. Onyl file-upload wourld be needed and writing in talk/chats

If the customer would

• log in
• upload something
• write in a chat
  there should be an email notification to us and a notification on the advisors dashboard

It should be easy for the customer to use the deck app and other apps, or ... a new customer app, heavily reduced in functions, with a nice and handy user experience.

No files, tests, or entry points are named. Start by reviewing the existing guest-account behavior and identifying which requested capabilities are already supported. A complete outcome is not defined; the isolation, read-only access, notifications, and app integrations need separate acceptance criteria before implementation.