FileVault overview

What FileVault is

FileVault is the project file area. It gives users a predictable place for diagrams, requirements, notes, uploads, exports, generated documents, and other artifacts that should stay attached to the project.

What belongs in FileVault

Use FileVault for files that help explain, shape, review, or preserve project work.

• Requirements, briefs, diagrams, screenshots, and references.
• Draw files and exported diagrams.
• Generated documents or review packages.
• Customer-provided material that the project team should use.

How to use it

Start by adding the minimum useful context. Create simple folders only when they make review easier. Keep names descriptive enough that a future reviewer can understand what the file is without opening every item.

• Upload source material before the project planning step when possible.
• Keep diagrams and exported assets in the same project context.
• Save generated review material so the next phase can find it.

Draw files

Draw boards should be saved in FileVault so diagrams stay connected to the project. That makes it easier to move from a visual workflow into requirements, review notes, or build tasks.

Generated files

When Kaidera creates documents, exports, diagrams, or review packages, users should be able to save the final useful version into FileVault. The goal is to preserve the artifact that matters, not every intermediate draft.

Reviewing files

Before approving work, check whether the important files are present, named clearly, and linked to the right project. If a file is missing, ask the project team to attach it before moving on.

What not to upload

Do not upload secrets, private credentials, sensitive personal data, or material the project team is not authorised to use. If sensitive material is required, it should be handled through the approved enterprise process.

What can go wrong

Common FileVault issues include uploading too much unrelated material, using vague file names, placing sensitive material in a general project folder, or reviewing work from an outdated file. Keep the project file area simple and current.

Expected result

A project reviewer should be able to open FileVault and understand the important project artifacts without searching through chat history or local folders.

Read next

Read the Draw guide when the project needs diagrams. Read Workbench when the question is how files connect to active work and review gates.