Tags

A tag is a type plus a value. The member must hold it. all means every type. any means one type.

Owners create and retire tag types. A type has a name unique in the organization, a description, and an optional list of allowed values. An empty list allows any value. Any member may list types, including retired ones. A retired type cannot be changed. Retiring a type blocks a new application. Tags already stored still match.

An owner replaces the tags on a member. A member may list their own tags. Listing another member’s tags is owner-only. Joining a drive does not grant tags.

An editor applies one type-plus-value they already hold to a directory or a file they may change. A value you do not hold is refused. The message is You do not hold that tag. The object stays as it was.

Match

Tags on a directory or a file are requirements. The inspector calls the setting Match. Every type requires each type on that object. One type requires a single type. A new directory and a new file require every type. The same person who can apply a tag sets the match on its own.

  • Within a type, you hold one of the values.
  • Extra tags you hold change nothing.
  • No tags on that object means no tag requirement from that object.
  • A single type makes Every type and One type the same match.

The chain allows only when every directory on it allows. A file allows only when its parent chain allows and its own match allows. One type on a child does not loosen a parent. Children do not store a copy of their ancestors’ tags. A move changes which ancestors apply. It does not copy tags onto children.

Switching one object from Every type to One type loosens only that object’s own tags.

A short example

Maria holds team:finance. The March close directory requires team:finance. Maria can see it. Daniel does not hold that tag, so the directory is absent for him and for his agent. The name is not shown.