S
Simpleasyty
Help Center — Controlled Document
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

SCHEMA TEMPLATES

Controlled Document

Use one document record across teams to make approvals and review dates traceable even outside a specific framework.

Controlled documents need more than a file name: readers need to know which revision applies and who approved it. This general-purpose template supplies those checkpoints across policies, procedures and standards without tying the record to one framework.

Fields

Before relying on a controlled document, readers need to know whether they have the right version and whether it has been approved. This structure makes those checks straightforward.

FieldTypeWhat it captures
Document IDRequired · IndexedTextStable identifier for the controlled document.
Document typeRequired · IndexedSingle choiceCategory such as policy, procedure, standard or record.Choices: Policy, Procedure, Standard, Guideline, Record
OwnerRequired · IndexedConfluence userPerson responsible for this risk, policy or document record.
StatusRequired · IndexedSingle choiceCurrent stage of the record's workflow or lifecycle.Choices: Draft, In Review, Approved, Retired
ApproverConfluence userPerson who reviews and signs off the document or policy.
VersionTextRevision identifier of the document; separate from page version history.
Effective dateIndexedDateDate from which the approved document or policy applies.
Review dateIndexedDateDate planned for the next review of the risk, document or decision.