Skip to main content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Documents

Major.minor document versioning

Minor version updates no longer require everyone to sign the document again, saving re-signatures for changes that actually matter.

Major.minor document versioning screenshot

Until now, every document version was a major version. Publish a new version, everyone has to sign again. Even for a typo fix.

Documents now support major and minor versions. Publish a minor version and existing signatures stay valid. No re-signing needed. Save that for when the content actually changes in a meaningful way.

Major versions still work the same. Bump the major number and everyone goes through the approval and signature flow again. You decide which one fits.