Drive, directory, tag
Three layers. A drive is the share. A directory is the tree. A tag is a mark.
An organization owns the users, the tag types, and the files. A user belongs to one organization. The organization pays for storage, including each member’s personal drive.
Inside the organization, access has three layers. Each one can only narrow.
Drive
The drive is the share. You work in one drive at a time.
A personal drive belongs to one member. A shared drive belongs to the organization. Members are assigned to it with a drive role. A request names one drive. The drives page has the roles.
Directory
A directory is the tree inside a drive. Creating a drive creates a root directory. The root has no parent, and it cannot be renamed, moved, or deleted. Every other directory has one parent in that drive. Its name is unique among its siblings. A file sits in one directory.
The name a person sees is the directory path and the file name. A rename leaves the file in place.
A directory may list the drive members who can see its subtree. An empty list adds no extra restriction. A restriction applies to everything under it. The files page covers the tree, deletion protection, notes, and shortcuts.
Tag
A tag is a type plus a value, such as team:finance or confidential. The type belongs to the organization, so people can list it and reuse it. A tag on a directory or a file can only narrow further. Tags are not a second tree, and they are not a second drive.
A member’s tags live on the user. The read compares the tags on the directories and the file with the tags on that user. The tags page is the match.
One decision
Lists, downloads, search, and SQL use that same decision. Access is the rule. Storage is where the bytes go after the file row exists.
In this section