Yes! To confirm -

Team Drives feature should always be enabled on Chrome OS, but for users who do not have Team Drives, we should hide the root.

What about users that *do* have team drives enabled, but no team drives?
Should we show an empty root?

Interesting - I wonder if this use case is possible from a Team Drives configuration perspective? But, if so, we should hide the Team Drives root if the user is not a member of any Team Drives.

> Interesting - I wonder if this use case is possible from a Team Drives configuration perspective?

Enterprise users have Team Drives enabled by default, so I'm fairly sure the team drives root would appear in Google Drive (so you can create new team drives, for example) even though the user isn't a member of any team drives.

Got it, thanks. Let's hide it even in this case as it's odd to have am empty Team Drives root in Files app when we don't support the ability to manage/add Team Drives.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/47a3530af21aa843e9d3bc42cd027847c2dd6363

commit 47a3530af21aa843e9d3bc42cd027847c2dd6363
Author: Sasha Morrissey <sashab@chromium.org>
Date: Wed May 30 03:17:27 2018

Commented the code that hides the Team Drives root if there are no TDs

Commented the code that hides the Team Drives root if there are no Team
Drives in the Files app.

Bug:  843873 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I064f9e5ad558b87bf4d879bf16ec437fed563686
Reviewed-on: https://chromium-review.googlesource.com/1070013
Commit-Queue: Sasha Morrissey <sashab@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562717}
[modify] https://crrev.com/47a3530af21aa843e9d3bc42cd027847c2dd6363/ui/file_manager/file_manager/foreground/js/ui/directory_tree.js