Skip to main content

June Workshop #4 Recap (Core): Reports, Integrations, Documents & Launch Preparation

  • June 24, 2026
  • 1 reply
  • 9 views
Keren Ringel
Bobber

 

Hey everyone 👋

Thanks so much to everyone who joined our latest and last(!) Core Onboarding Workshop!
This session focused on three key areas: getting your reports ready for go-live, connecting your integrations, and ensuring a smooth launch process in Bob.

🎬 Click here to watch the full session Here 
 

Do not forget to register to our upcoming (and last) Q&A session!

 

Here’s a quick recap of what we covered in this workshop:

📊 1. Reports

- How to build and customize reports to track key metrics.
- Tips for sharing reports with managers and leadership.
- Scheduling reports and exporting data efficiently.
➡️ Learn more Here 

 

🔗 2. Integrations

- Overview of the most commonly used integrations.
- Troubleshooting and permission.
➡️ Learn more Here 

 

🔑 3. Documents

We showed how to organize and manage company documents, contracts, and templates in Bob — and how to share them securely with employees.
➡️ Learn more Here 

 

🚀 4. Launch Preparation

- Key steps to finalize before go-live — from data validation to permissions.
- Communication best practices for introducing Bob to your wider team.
- Resources and checklists to make your launch day smooth and stress-free.
➡️ Learn more Here 

 

🎯 What’s Next

- Make sure to clean sample data from your environment.
- Import your people’s data into Bob, and Invite your employees to join!
- Keep an eye on this space for updates on upcoming workshops and new feature releases.


🎥 Watch the full recording Here 

Good Luck with the Launch and let us know here if you have any follow-up questions or tips from your own setup (you may drop them below, or as a separate question in the Community Hub)

We need your feedback to keep improving! Please answer these few short questions about your experience!


 

    1 reply

    Keren Ringel
    Bobber
    • Keren Ringel
    • Author
    • Bobber
    • June 24, 2026

    Following the question that came up on the session, I checked and can confirm that when replacing files in Company Docs, the Date uploaded and Upload By fields do not update to reflect the current replacement date and user. This is the expected platform behavior, where the system retains the original metadata when documents are replaced. 

    Our Product team are aware of this gap and working to find a solution, but until then, I can suggest a couple of workarounds:

    Option 1: Delete and Re-upload Method
    Download the new document version, delete the existing document from the system, and upload the new document as a fresh file. This will update both the upload date and uploader information to reflect the current replacement.

    Option 2: Version Control Through Naming
    Include version information or last review dates directly in the document title or filename. For example, you could name files as "Policy_Document_v2_Jan2024" or "Handbook_Updated_20240115". This provides clear version tracking even when the system metadata doesn't update.

    Option 3: Archive and Upload New
    Keep the original document but rename it to include "Archived" or "Outdated" in the title, then upload the new version as a completely separate document. This maintains a clear audit trail of document versions.

    These approaches will help you maintain proper version control and make it easier to identify the most current documents and track when updates were made.

    I hope this helps

    Best

    Keren
     

    Terms & ConditionsAccessibility statement