Hello Jenny,
Welcome to the Microsoft Community and thank you for reaching out with your inquiry.
Based on the details provided, I understand that you are using a SharePoint Online site (not connected to a Microsoft 365 Group) as a client portal for external guest users and this portal is currently configured to allow clients to access content via a one-time passcode (OTP).
Please find below a detailed response to your concerns:
1. Client Access to Individual Folders
You have successfully implemented a method whereby each client is granted access to their respective folder or individual documents through the client portal.
Important Notice: Microsoft is in the process of retiring one-time passcode sharing. Beginning July 1, 2025, OTP-based sharing links will cease functioning for external users. Further information regarding this change is available at SharePoint Online Dumps OTP Authentication for Sharing Links | Microsoft Community.
While OTP functionality may still be active at present, it is advisable to begin transitioning your clients to using Microsoft accounts for future access. This approach will likely provide a more consistent and secure user experience.
2. Document Submission Requests from Clients
You can facilitate this functionality without the need to create a separate site. SharePoint now offers a “Request Files” feature within document libraries.
- Select a folder and choose the Request Files option.
- SharePoint will generate a unique upload link.
- External guests can upload documents using this link without viewing folder contents or requiring a Microsoft account.
- You will receive a notification once a file is uploaded.
Note: This feature requires that “Anyone” links are enabled at the tenant level. If the option is not visible, your SharePoint or Microsoft 365 administrator may need to modify the external sharing settings.
For further reference, please see: How the Request Files Feature Works in SharePoint Online | Microsoft Community Hub.
3. Approval Requests for Clients
Based on your testing and message trace results, approval workflow emails are not being sent to external users—even if they have accessed shared content via OTP.
There is a known problem with this process for guest users with and approval requests without having MS account. Approval workflows typically require recipients to be authenticated users. OTP-based access does not meet this requirement, which likely explains why approval emails are not being triggered.
Here are some key considerations:
- SharePoint approval flows (e.g., those implemented using Power Automate) generally require the recipient to possess a Microsoft account in order to receive and act upon approval requests.
- Even if guests have folder access, approval emails may not be triggered if the user is not fully authenticated in Azure Active Directory (Azure AD).
- The absence of entries in the message trace suggests that these emails are not being generated at all, rather than being delayed or blocked.
You can learn about Approval workflows by accessing to documents below:
What you are looking for is possible but with some modifications. While access and file submissions via OTP are feasible in the short term, approval workflows should be redesigned to accommodate authenticated user interactions. This may involve implementing alternative methods of collecting approvals:
- Use Power Automate to issue a custom email notification to the guest with a direct link to a relevant form or document, instead of relying on the built-in approval action.
- Collect responses via Microsoft Forms or through a SharePoint list where external users can submit inputs.
- For formal approval processes, consider onboarding guests as Azure AD B2B users with full guest accounts, rather than relying on OTP-based access.
I hope my answer is helpful to you. Please feel free to reach out if you require further clarification or assistance.
Thank you once again for your inquiry, and I wish you continued success with your SharePoint implementation.
Best Regards,
Tamara-Hu- MSFT | Microsoft Community Support Specialist.