Users often need a way to access their files, manage uploads/downloads, use drag and drop functionality, and copy/paste files. Since our platform was built to make your workflow as simple as possible, we aim to provide flexibility when it comes to managing your files on Frame.
Browsing your files¶
There are different methods to browse through your files and folders on the Frame platform. The different methods, as well as their pros and cons, are outlined below:
Frame Explorer is an option for file management that works similarly to Windows Explorer.
Alternative file browsers¶
If you would like to use something other than Frame Explorer, you have options. Feel free to use alternative file management software such as Cubic Explorer. Install and onboard these alternatives as you would a normal Windows application.
If you are comfortable with your users having full desktop access, you can enable desktop mode. In desktop mode, users can use the native Windows File Browser (explorer.exe) to access and work with their files. You can reference our documentation about desktop mode here.
In general, we don’t recommend the use of Windows Explorer because it is tightly tied to the full Windows environment in the session (e.g. start menu). Starting explorer.exe can interfere with the Frame session and potentially cause issues. If you require the use of explorer.exe, the steps listed below will show you how to configure it to prevent any issues for your users needing to access it from their Launchpad:
Connect to your account’s Sandbox.
Navigate to the C: drive and locate explorer.exe file in “Windows” folder. Make a copy of explorer. exe and rename the copy to anything other than “explorer.exe.” For example, you could rename it to “explorer2.exe.”
Place the newly renamed file anywhere within the C: folder.
Right-click the renamed explorer and select “Onboard to Frame.”
Go back to the Dashboard and rename the onboarded copy of explorer to your desired application name.
Publish your changes to make Windows Explorer available to your Production users.
Windows Explorer can only be launched as a secondary application. Attempting to launch Windows Explorer as the first application from the Launchpad will result in a failed session.
Why does this work?
Launching explorer.exe under a different name will prevent Windows from initializing the native desktop environment (desktop icons, start bar, etc.).