Egnyte
See Cloud storage for the cross-provider comparison.
When to use Egnyte
Use Egnyte when the target or adviser already manages shared diligence material through Egnyte and the goal is to treat that folder as the project’s intake source.
The IT-managed shared folder becomes evidence
Real deal example: Egnyte as the source of truth
In teams that still rely on Egnyte as the operational file layer, connecting the project folder is the simplest way to start the Colabra pipeline without asking people to duplicate the folder in a second system.
Setup pattern
Connection happens once at the workspace level. The actual project folder is selected later from a project’s files empty state or from Project menu → Import.
Egnyte browsing starts from Shared.
What happens after import
- the initial folder contents are imported immediately
- Colabra performs background re-syncs for connected project folders
- upstream file changes are stored as new file versions rather than duplicate project files
The exact re-sync cadence is not currently exposed in product settings, so teams should treat it as automatic background sync rather than a user-configurable schedule.