- Matthew Smith
- Jan 1, 2024
- 3 min read
Updated: Apr 14
NOTE: these changes are available from easyFBT 2024 onwards.
Start-Up, Create Data Source and Connect Data Source wizard folder and file permission validation
As security and virus concerns continue to grow, businesses are increasingly limiting user permissions and reducing their exposure. Many users are being shifted to cloud storage for their data (like Documents folders), which has sometimes unintentionally restricted access to files and folders.
To help identify access issues early, we’ve made the brute-force check in the wizard more visible. This process validates actions like creating folders, creating files, appending files, removing files, and deleting folders. If an error occurs during any of these steps, it typically indicates that the necessary permissions haven’t been granted.
Generally we complete the following steps during the check:
Create temp folder - users require the ability to create folders
Create test file - users require the ability to create/write files
Read test file - users require the ability to read files
Append test file - users require the ability to modify/write files
Remove test file - users require the ability to delete files
Remove test folder - users require the ability to delete folders
From easyFBT 2025 onwards, we have also provided quick access to this check via the Administration tab on the System Manager:
Validating OneDrive
NOTE: the following information has been provided by GROK AI
To ensure full read/write permissions for a user's Documents folder stored in OneDrive within a corporate environment PC, follow these steps:
1. Verify OneDrive Sync Setup:
Confirm that the OneDrive client is installed and the user is signed in with their corporate Microsoft 365 account.
Ensure the Documents folder is correctly synced to OneDrive (typically under "C:\Users\<Username>\OneDrive\Documents" or a custom path defined by IT).
2. Check Local File Permissions:
Right-click the Documents folder in File Explorer, select Properties, and go to the Security tab.
Verify that the user’s account (or their Active Directory group) has Full Control permissions.
If permissions are missing, click Edit, add the user’s account, and check Full Control. You may need admin rights to modify this.
3. Confirm OneDrive Permissions:
Log in to the OneDrive web portal ("https://onedrive.live.com" or corporate equivalent) using the user’s credentials.
Navigate to the Documents folder and click the Share or Manage Access option.
Ensure the user has Can edit permissions. In a corporate setup, this is typically automatic for the account owner, but verify no restrictive policies override it.
4. Check Group Policy/Intune Settings:
Corporate environments often use Microsoft Intune or Group Policy to manage OneDrive. Ask the IT admin to confirm that:
OneDrive Known Folder Move (KFM) is enabled, redirecting Documents to OneDrive.
No policies restrict read/write access to OneDrive folders.
File permissions for synced folders allow user modifications.
5. Test Read/Write Access:
Where possible, backup and remove the existing easyFBT Documents product year folder (typically under "C:\Users\<Username>\OneDrive\Documents\One Plus One Solutions Pty Limited\easyFBT 20XX" or a custom path defined by IT).
Depending on your situation, whether it's on the initial start or after some time using the software, launch easyFBT and follow one of these steps:
Complete the Start-Up Wizard (if prompted).
From the 2025 version onwards, open the System Manager, go to the Administration tab, and click the Validate permissions button to run the Folder and file Permissions test.
6. Validate with IT (if needed):
If the user lacks permissions, corporate restrictions (e.g., Conditional Access policies, MDM settings) might be in place. Contact the IT team to verify:
The user’s account has appropriate OneDrive storage and access rights.
No security policies block modifications to synced folders.
Note: In corporate environments, local folder permissions are often managed by OneDrive’s cloud sync, but IT policies may override settings. If you’re not the admin, involve the IT team to check backend configurations like Azure AD or Intune.
Important Considerations
Corporate Restrictions: In a managed environment, Group Policy, Intune, or Azure AD settings may override manual permission changes. If resets don’t stick, IT must review backend configurations.
Data Safety: Before resetting permissions or deleting cache files, ensure critical data is backed up, as missteps could cause sync conflicts or data loss.
Admin Access: Many steps require elevated privileges. If you’re not an admin, coordinate with the IT team.
OneDrive Quotas: Ensure the user’s OneDrive storage isn’t full, as this can mimic permission issues by preventing writes.
