UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10452.74.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.137 Safari/537.36
Platform: 10452.74.0 (Official Build) stable-channel eve

Steps to reproduce the problem:
1. Open FilesApp
2. You'll see you're "Downloads" folder

What is the expected behavior?
I'd love to see a function in the Chrome/Chromium OS FilesApp which allows me to set a folder as default to open on startup of the file manager.

My idea would look something like this: A new menu option in the overflow menu (three dots in the top right corner), that allows me to set the current folder as an entry point to open on startup. If the folder doesn't exist / isn't available anymore (File System Provider e.g SFTP shut it down etc.) the FilesApp would simply go back to Downloads as usual.

Main purpose: To enable users to directly "land" e.g. in their My Drive. Since according to the Chrome OS support page, the system deletes files from Downloads if it's low on space, so I wouldn't leave this "temporary folder" as the forced default entry point to the File Manager.

What went wrong?
The default entry point in the File Manager is a temporary downloads folder, which the OS deletes if there isn't enough space available on the user's device.

Did this work before? No 

Chrome version: 66.0.3359.137  Channel: stable
OS Version: 10452.74.0
Flash Version: