Library and sharing
The Library keeps the questions, reports, and decisions your team needs to revisit. Use it to preserve the evidence behind a forecast call, a renewal decision, or an account review.
Save the work that will come up again
Save an answer when it contains a number, finding, or explanation the team will need later. The saved item retains the supporting records and the date of the result. When someone asks where a conclusion came from, the team can open the original work instead of rebuilding it.
You can ask the same question again against current information. The earlier version remains available, making it easier to compare what changed between two reviews.
Keep a useful history
Each revision creates a version. This matters for recurring revenue work: a weekly account brief, a forecast report, or a saved answer can show both the current position and what the team saw last time.
Organize only as much as your team needs. A few folders by topic or operating rhythm are usually enough. Search is better than maintaining a deep filing structure.
Share with care
Use a private link for a specific person or group. Use a public page only when the item is intended for anyone who can reach the link. Shared items are read-only, and sharing an item does not provide access to the underlying connected systems.
Read an item before sending it. A shared answer can include figures the sender is allowed to see, so it deserves the same review as a spreadsheet or a slide.
Remove a share when the audience no longer needs it.
What belongs in the Library
- Forecast and renewal reviews the team will revisit
- Answers that took time to validate
- Numbers that will be used in a meeting or decision document
- Reports that explain what changed and what the team decided
For a recurring, structured review, use Reports. For the forecast workflow itself, see Revenue Intelligence.