Diagrams that go through review, not around it

A status that means something

A diagram moves through defined states rather than living in someone’s idea of “done”. Each transition records who made it, when, and the note they left, so the history answers why a model is in the state it is in.

• Named reviewers and an inbox of what is waiting on you
• A full transition history, newest first
• Notes captured at the point of transition, not reconstructed later

Validation gates before submission

Submitting for review runs the model validator first. Blocking errors stop the submission and say what they are, so a reviewer is never handed a model that fails its own standards. Critical non-functional violations are counted separately and gate submission in the same way.

An audit log for the whole workspace

Beyond a single diagram, the audit log records what happened across the workspace. Combined with version history and branches, the question “who changed this and when” has an answer that does not depend on anyone remembering.

What this covers in the product

Every capability below is part of this area of Yantra Studio.

• Approval workflow
• Audit log
• Validate Model
• Team & collaborators

Questions

Related capabilities

• Standards that are enforced, not published

  Define naming standards, validate the model against them, produce a health report, and enforce the same rules in CI so violations fail the build.

• Diagrams in Git, on branches, with history

  Store diagrams in your own GitHub repository, work on branches, browse version history and merge diagrams — the same workflow your code already uses.

• Access control that goes down to the row

  Single sign-on with OIDC, multi-factor authentication, session policy, workspace roles and row-level access control on every record.

See all 21 feature areas →