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
Governance

Task activity: see what changed on a task

Task details now include an activity tab that lists every field-level change newest-first, so you can see which edits were made, by whom, and when without combing through audit logs.

Task activity: see what changed on a task screenshot

Trying to figure out how a task got to its current state usually meant paging through audit logs and cross-referencing timestamps yourself. That is gone.

Task details now have an activity tab that lists field-level changes newest-first. Each entry shows which field changed and who made the edit, so you can see the path a task took without jumping elsewhere. The same list is available from GraphQL, MCP, the CLI, and n8n, so the history shows up wherever you already work.

When a task is the record of who did what inside an organization, an edit trail is not a nicety. It is how you answer “why did this change” in a governance review. Now you can, in one place.