We often do have an identity in Salesforce in form of a Community User login, such as a Partner or Customer – but we don’t want to manage and provide dedicated Microsoft credentials on our tenant just to be able to share files and documents – Q!365 will take care of that.
A 1-minute video insight:
Let’s assume we do have a specified Document Library on Microsoft 365, dedicated for all Community users. For each new Community User, Q!365 will automatically create a folder structure based on a given ruleset – this could be their name, or email address, incl. a given set of subfolders.
For the top-level folder, we create a relationship to the Community user’s profile or contact record.
On top of that, Q!365 automatically takes care of the external sharing based on the user’s email address, and then sets up either read-only or edit permissions.
Now we include the Q!365 in the Community user’s interface, running on behalf of a service user and limited to just show the user’s associated folder, and provide the upload capability, so that the user is able to share files within the Community.