Clients and files
Two levels of organization, and that's it: clients hold files.
Clients
A client is the workspace for one solution, usually one customer or one project. It holds the files, the uploads, the logs, the board, the discussions, and the AI connections for that solution. Different customers belong in different clients; nothing crosses between them, in the portal or through the AI.
Files
A file in FM Fathom mirrors a FileMaker file. Single-file solution, single file entry. Multi-file solution, one entry per FileMaker file, each with its own export uploaded, linked through External Data Sources and the client's solution map so cross-file references resolve.
Two upload behaviors worth knowing cold:
- A new XML upload replaces that file's parsed data. The catalog reflects the latest export, full stop. To hold two versions side by side, use two files and version comparison.
- Log uploads add. Logs accumulate into the file's history; coverage grows with each bundle.
Board items and discussions survive XML re-uploads; your tracked work carries forward to the matching objects in the new version.
Sharing is per client, and total
Everyone granted a client sees the same thing: the same catalog, the same board, the same discussions. There is no per-user visibility inside a client, and an upload changes the file for every member at once. If some people shouldn't see a solution, the boundary to use is client access itself.
The demo client
Every beta account includes a shared demo client, a small inventory solution with no real data, there so you can explore before uploading anything. It's shared with all testers and can't be deleted. Its scripts don't call each other, so its call chain views are empty by design, and it has no server logs; judge those features on your own solution.
Deleting things
- A file's logs: removable on their own, without touching the parsed solution.
- A file: removes its parsed data and history.
- A client: removable by whoever created it, or an admin.
- Your account: see Accounts.