Support & Downloads

Izymes builds easy-to-use apps for Atlassian applications that boost your productivity, free you from performing repetitive tasks inside Confluence, Jira and Bitbucket and enable you to use your time for what you do best – YOUR job.

Book a Demo

Interested in a 1-on-1 demonstration of Izymes’s products?
Here we will walk you through;

• All features and benefits of the product you are interested in trying.
• How to set up the account and configure the settings.
• Other tips, tricks and best practices.

It will also give us time to answer any questions you may have, or perhaps you just want to have a chat, we love a good chat.
You can schedule a time on the Calendly link below. Talk soon!

Contact Info
HQ Southport
Queensland, Australia
[email protected]
Follow Us
Use Case - Workzone Cloud

FDA-Grade Pull Request Compliance with Verified Digital Signatures

Ensure non-repudiable, audit-ready approvals aligned with CFR Part 11 and ISO standards — built directly into your Bitbucket workflow.

Use Case

FDA-Grade Pull Request Compliance with Verified Digital Signatures

For enterprises in regulated sectors — such as medical devices, pharma, aerospace, or financial services — source code changes are treated like official records, requiring traceable, auditable approval from designated individuals or roles. Unfortunately, Bitbucket’s default pull request approvals don’t meet these standards: there’s no way to uniquely identify a reviewer’s authenticated sign-off, and no compliance-grade audit trail.

Workzone’s Digital Signatures fill this critical gap, enabling reviewers to approve pull requests with a secure, personal signature token — akin to signing an official document. This turns each code approval into a verified, non-repudiable action, fully aligned with frameworks like FDA CFR Part 11, ISO 27001, or internal GxP standards.

Here’s how enterprise teams use it:

  • When a pull request is created on a controlled branch (e.g. develop → release/*), Workzone checks for the required digital signature quota before allowing a merge.
  • Reviewers like Thomas (Release Manager) and Ulrich (QA Lead) must each approve using their unique, one-time-generated and revokable signature token — verifiable and stored securely.
  • Merge conditions are only satisfied once all required digital signatures are present — ensuring no merge can occur without explicit, traceable approval.

Workzone also supports role-based digital signatures, where specific roles (e.g. “Tech Rep,” “Quality Rep”, “Test Rep”) must each be represented by a signatory. The system enforces that only one reviewer representing a certain rol can sign, and tracks who signed on behalf of which role, making audits effortless.

This is far more than just approval metadata. Unlike Bitbucket’s built-in approval system:

  • Each signature is individually attributable and cryptographically tied to the reviewer.
  • Workzone maintains a complete audit trail of all signatures and their associated metadata (who, when, for what, on behalf of which group).
  • It blocks merges until required signatures are received, removing any room for manual error or policy violations.

For enterprises subject to internal or external audits, Workzone’s Digital Signatures offer peace of mind — making compliance a native part of the development workflow, not an afterthought

Use Cases

Explore More Use Cases...

Learn how enterprise teams streamline workflows, boost compliance, and drive productivity with Izymes apps