Adding client tagging to file management system

The situation

The user needs to organize files by client, but the current file management system lacks this feature. The system already supports storing per-file metadata, which can be used to add a client field. The user's file collection is currently empty, but they want to be able to assign a client to each file and filter files by client. The system's existing file facts can be used to store a client value for each file, and the user-facing path to edit and filter it can be made clear.

What they weighed

• Use generic file fact for client tagging

• Add dedicated client field and controls

• Expose client as file fact in workflow

  Chosen

What they decided

Expose client as file fact in workflow

Why

The existing file facts already store per-file metadata and are described as visible and filterable, so using them to store a client value directly serves the user's request. This approach also takes the smallest route supported by the account's current file capability. It is a straightforward way to meet the user's needs without adding unnecessary complexity. By using the existing file facts, the user can easily assign a client to a file and filter files by client, making it a practical solution.

The first step

Make client tagging accessible in the live screen and verify the result

How they would know it worked

User can assign a client to a file and filter by client

How it turned out

Not known yet. The result is added here when it comes in.