When using Auto Upload Enterprise Files, common questions usually focus on sync scope, local file handling, disk usage, and policy rollout; this FAQ includes 4 common questions and answers.
FAQ
Does auto upload sync every local file?
- No. It does not automatically sync every local file.
- It uploads files that users open and edit to enterprise cloud documents.
- Files that were not opened, or files that users downloaded for archiving, are not uploaded automatically.
Can local files be deleted after auto upload?
- It is recommended to confirm that the file has finished syncing successfully.
- Deleting a local file before sync is complete may affect file retention.
- It is safer to handle local cleanup after sync is complete.
Does auto upload use local disk space?
- Yes. It uses some local space for file cache and sync management.
- If local disk space is limited, plan file retention based on your organization policy.
- When many files are synced for the first time, reserve enough local space in advance.
What should be checked before enabling auto upload?
- Inform members in advance about the sync rules and the scope of effect.
- The first sync for large files may take longer, so a stable network is recommended.
- If some members need to be exempt, configure the whitelist in advance.
Glossary
| Term | Definition |
|---|---|
| Auto Upload | A capability that automatically syncs files users open and edit to enterprise cloud documents according to organization policy. |
| Member Scope | The range of users affected by the auto-upload rule. |
| Whitelist | A list of members who are excluded from the current auto-upload rule. |
| Forced Sync | A rule that requires document cloud sync to stay enabled and cannot be turned off manually by members. |