Pick a folder on a network share or a synced drive. P7 keeps its own files in a P7 Enterprise folder there and leaves your other files alone.
Working together in P7
Edit one schedule together, live, from a shared folder
P7 keeps a team's projects in a folder you pick, on a network drive or a synced folder. Everyone with the same project open sees the others' pointers, selections and changes as they work, with no Pathizer server in between.
Pick a shared folder in P7 in Chrome or Edge. Its folders are the EPS and each project is a file. People with the same project open see each other's changes live. When two change the same field, the later change wins, and each person undoes only their own changes.
Use P7 from Claude or Codex
Your AI app on your computer, your schedule in your browser.
Claude Desktop and Claude Code
Claude Desktop installs the connector from one downloaded file. Claude Code adds it with one terminal command.
Codex
Add the connector with one terminal command, or in ~/.codex/config.toml. Needs Node.js 20 or newer.
Setup
From one browser to a shared schedule
Pick the folder
In Chrome or Edge, open a shared folder from P7's File menu, on the drive your team already uses.
Bring projects in
Import .XER or .XML files, or copy the projects already in your browser into the folder.
Share the folder, not a link
Anyone who can open the folder can open its projects. There is no invite to send.
Work at the same time
Open the same project. On a network share, each person sees the others' pointers, selections and changes about once a second; on a synced drive, as fast as it syncs.
Undo your own work
Undo takes back your changes only. When two people change the same field, the later change wins for everyone.
Who It Is For
For scheduling teams on a shared drive
Scheduling teamsProject controls groupsSuperintendentsDrive administrators
What P7 Does
Folders are EPS nodes and each project is a file in its node's folder, so the whole team browses one EPS.
See each person's pointer and selection in their own colour, and their edits as they make them.
Access follows the folder's own permissions: a read-only folder shows a padlock, and its changes are turned off.
Files moved, renamed or added on the drive outside P7 show in P7 within seconds.
Each change is saved to the folder about a second after it settles. A save the drive does not answer is tried again by itself, and the header turns red until it goes through.
Definitions
Terms used on this page.
Shared folder
A folder on a network drive or a synced drive that P7 opens in Chrome or Edge to keep a team's projects in.
.p7-live
A folder P7 keeps inside the shared folder for live work. Each person's browser writes its own small files there and reads the others'.
More in the glossary: Enterprise project structure (EPS), P7 Free Scheduling, Schedule update, XER file.
Practical Outputs
What you get.
One EPS the whole team works in
Live edits, pointers and selections from everyone with a project open
Saves that follow the drive's permissions
Related Workflows
Related pages.
FAQ
Questions about working together
No. Each browser writes its own files in the shared folder and reads the others'. Pathizer runs no server for it and receives none of it.
The later change wins, for everyone. Each person can undo only their own changes.
Anyone who can open the shared folder, as with the files themselves. Someone with read-only access to the folder sees the others and cannot change the project.
Chrome and Edge. Firefox and Safari cannot open folders, so there P7 keeps projects in the browser.
Only when you delete that project in P7, after a confirm, or your AI deletes it. P7 never deletes a file it does not know, and keeps its own files in a P7 Enterprise folder.
P7 runs in your browser with no account, and your schedule stays on your device.
Open P7 Free Scheduling