How to Synchronise Sensitive Bank Records to SharePoint Online Without Exposing the Entire Site
Summary
This guide helps you troubleshoot and resolve: How to Synchronise Sensitive Bank Records to SharePoint Online Without Exposing the Entire Site. Follow the steps below to fix the issue.
Common Causes
Accountancy and bookkeeping practices frequently need to store digital bank statements, transaction logs, and BAS preparation files in SharePoint Online. Because these records are highly sensitive, they should not sit in a general document library where inherited permissions grant broad access to all staff. This article explains how to synchronise bank records from a local server or NAS to SharePoint Online and apply unique permissions to a dedicated document library so that only authorised users—such as the principal accountant—can view or edit financial data.
Quick Fix Steps
- Create a dedicated document library in SharePoint Online for banking records.
- Stop permission inheritance on the new library.
- Remove broad access groups and grant permissions only to authorised users.
- Configure ongoing synchronisation between the local NAS and SharePoint Online.
- Verify that unauthorised users cannot access the library using a test account.
Detailed Instructions
1. Create a Dedicated Document Library
- Open your SharePoint site in a web browser.
- Select Home from the left navigation, then choose New.
- Click Document library.
- Enter a clear name such as
Banking RecordsorClient Bank Statements. - Select Create.
Using a separate library rather than a folder inside a general library makes it easier to manage unique permissions and reduces the risk of accidental access.
2. Break Permission Inheritance
- Open the new
Banking Recordslibrary. - Select the Settings gear icon in the top-right corner, then choose Library settings.
- Under Permissions and Management, select Permissions for this document library.
- On the ribbon, select Stop Inheriting Permissions.
- When the confirmation prompt appears, select OK.
Breaking inheritance removes the library from the parent site permissions. Any users who previously had access through the site will no longer be able to enter this library unless you explicitly grant them access.
3. Remove Broad Access and Grant Authorised Users
- With the library permissions page open, select Grant Permissions.
- Enter the names or email addresses of users who require access, such as the principal accountant and senior bookkeeper.
- Choose the appropriate permission level—typically Edit or Full Control—then select Share.
- Review the list of existing users and groups. Select any broad groups such as
All Staff,Members, orVisitors, then choose Remove User Permissions. - Select OK to confirm removal.
Grant permissions to individual users or a dedicated security group rather than to Everyone except external users.
4. Configure Ongoing Synchronisation
- Install the OneDrive sync client on the workstation or server that hosts the local bank records.
- Sign in with an authorised account that has access to the
Banking Recordslibrary. - Navigate to the SharePoint
Banking Recordslibrary in your browser. - Select Sync from the command bar.
- Follow the prompts to synchronise the library to a local folder on the NAS or server.
- Move or copy bank statements and transaction logs into the local synced folder.
- Wait for the sync client to upload changes to SharePoint Online.
5. Verify Access Restrictions
- Sign in to a workstation using a non-admin test user account that should not have access to banking records.
- Navigate to the SharePoint site and attempt to open the
Banking Recordslibrary. - Confirm that the user receives an access denied message or cannot see the library.
- Sign in with an authorised account and confirm that the files open correctly.
Compliance Considerations for Bank Records
Storing sensitive financial data in SharePoint Online requires additional governance to meet accountancy compliance standards and BAS preparation requirements.
- Audit logs: Enable SharePoint audit logging to track who accesses, edits, or downloads bank records. Review the audit log regularly in the Microsoft Purview compliance portal.
- Retention policies: Apply a retention policy to the
Banking Recordslibrary to ensure financial records are kept for the required statutory period and disposed of securely when no longer needed. - Sensitivity labels: Apply a sensitivity label such as
Confidential - Financialto the library or individual files. Sensitivity labels can enforce encryption and restrict sharing outside the organisation.
Troubleshooting
Users Can Still Access the Library After Inheritance Is Broken
- Ensure you selected Stop Inheriting Permissions and confirmed the action.
- Check whether the user has direct permissions assigned to the library or is a member of a group with explicit access.
- Review the library’s Advanced permissions settings to see all granted users and groups.
Authorised Users Receive Access Denied
- Confirm the user was added after inheritance was broken.
- Verify the permission level assigned is sufficient—for example, Read allows viewing but not editing.
- Check if the user’s account is synced correctly from your on-premises Active Directory to Microsoft Entra ID.
Synchronisation Paused or Failing
- Check the OneDrive sync client status icon in the system tray.
- Sign out and sign back into the sync client with the authorised account.
- Ensure the local NAS folder path does not exceed Windows path length limits.
- Verify that the account has sufficient storage licence allocation in SharePoint Online.
- Check for file names containing unsupported characters such as
#or%.
Files Do Not Appear After Synchronisation
- Refresh the SharePoint library page.
- Check the OneDrive sync client for upload errors.
- Verify the file size does not exceed SharePoint Online limits.
- Ensure the local folder is still selected for synchronisation in the OneDrive client settings.
If you need assistance configuring permissions or synchronisation for your banking records, Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket