Instead, I think I’ve encountered a work-in-progress for the future of the Files app. If I’ve discovered some sort of flaw in Chrome OS security that allows access to two separate accounts through the GUI, that would be concerning, but I highly doubt it – even in Canary.

fmp access from the front doorīug: swa file access Chromium Repositories

I did some research and while I’m still new to scouring the Chromium Repositories, I found one report that states that someone was able to use Files SWA to access the file management protocol via the “front door”. Okay, so let’s play devil’s advocate for a moment and say that this is just a bug. The fact that the OS’s camera can be used as a website just goes to show how far the web has come. Many of the Chrome OS system apps are being transitioned from a locally installed program to websites with identical styling. System Web Apps (SWA) have made an appearance in the OS before – namely with the camera app and Explore. With chrome://flags/#files-swa enabled, my Files app essentially becomes a progressive web app or PWA. Over this past month, I’ve been running into some interesting behavior in Chrome OS 87-89 Canary where I have two separate user sessions utilizing multi-account login with my Pixelbook Go and while using one of them, I can access my Drive files for the other via the first one’s Files app! Accessing any data from accounts that you’ve subsequently signed in to during that session are relegated to the web browser or Google Play apps where you can switch between them. The Chrome OS Files app has always only ever allowed you to see your Google Drive files for the account that you’re actively signed into the Chromebook with.

Switching google drive users