Cash Flow
You can share a plan with a colleague and read what kind of share each one is.
**Share** in the rail hands the plan to someone else. The Cash Flow Plans manager then shows what has been shared, with whom and when, in its **Shared** column — its tooltip lists User, Share Type and Date, or *Never shared*.
| Kind | What the other person gets | | --------------------------- | ------------------------------------------------------ | | **Snapshot share** | the plan as it is now; later changes do not reach them | | **Auto-updating share** | the plan, kept current as you change it | | **Shared with edit access** | the plan, and the ability to change it |
**Snapshot** is the one to reach for when a plan is going outside the production — to a bank, a fund, a financier. What they received stays what they received, which is what you want on record.
**Auto-updating** suits a colleague who should always see the current position.
**Edit access** is for someone genuinely working on it with you.
A cash flow plan holds almost nothing itself — it reads a budget and a financing plan. Sharing one shares a view onto those.
That is worth a thought before sharing outside the production: the plan exposes the shape of your budget and your financing, in more detail than a printed summary would. **For an external recipient, a printed PDF is often the more appropriate artefact** — see [print a cash flow plan](/kb/article/print-a-cash-flow-plan).
The manager's **Server** column says whether what you are sharing has reached the server. *Not on the server yet* or *Upload failed* means the recipient will not see your latest work.
Check it before telling someone the plan is waiting for them — see [manage and copy cash flow plans](/kb/article/manage-and-copy-cash-flow-plans).
Markdown