Document Control overview
Document Control gives every controlled document a lifecycle: draft, review, release, retire. You sign approvals with a one-time password, and every version is kept along with the reason it changed. The documents live in Confluence, which is where you work on them.
Document control has one job. The people who need a document must reach the current approved version, and must not reach an obsolete one by accident. Document Control does that by keeping approved documents in a separate read-only space, routing every change through approval, and putting a next review date on each release.
What you can do
Create from templates
Start a new controlled document or template with a wizard that captures the title, type, and affected products.
Approve with e-signatures
Route documents to reviewers and record each approval against a one-time password sent to the approver’s email.
Track every version
Every version keeps its number, its content, and the reason it changed. A diff view compares any two of them.
Modify, copy, and retire
Revise a released document into a new version, clone one as the basis for another, and obsolete the ones you no longer use.
Where it runs
Document Control is a set of Confluence macros backed by Jira. Every other Qity app puts the work in Jira and turns it into documentation in Confluence. Document Control is the deliberate exception, because a controlled document is itself a Confluence page. Creating, reviewing, approving, and reading documents all happen in Confluence, and for most people it is the only tool they open. Jira holds the metadata behind each document, and only QA and administrators need to go there directly. See How Qity works.
Start with Key concepts to learn the building blocks, then follow Create a document to make your first one.