DynamicForm Start free trial

Configuration document

Know what you have configured, in a PDF available at any point.

The System Configuration Document brings your application design together for review. DynamicForm by AG Studio Ventures builds it from the stored configuration, so the document reflects that version.

Employee Leave configuration document links source labels, screen views, diagrams and review details.
Review the application design and the source behind each statement in the same document.

Download at any step

Generate the document with a click from every AI Core step, starting with the first draft. Choose the full document for detailed review or the summary for an overview.

You do not need to wait until the application is finished to review its configuration. The document includes assumptions and open questions alongside the design, making unfinished decisions visible during review.

Use the summary to discuss the shape of the application. Use the full version to examine screens, permissions and rules together. Both come from the stored configuration at the selected step.

See the whole design

Read the application as a connected design, rather than reviewing screens without their rules or permissions. The document includes the following areas.

  • Summary and sources explain the proposed application and the material behind it. Assumptions and open questions remain visible.
  • Roles and hierarchy show responsibilities alongside permissions. Menus and lists describe how people reach their work.
  • The data model includes a diagram. Database and capacity information sit with the configuration they describe.
  • Every screen appears as it looks on the web and on the phone. User interface rules accompany the screen design.
  • Workflows appear as diagrams, with the rules catalogue available for review. Integrations show the configured connections.

These views help reviewers follow a process across its screens, decisions and access choices. Read the rules catalogue beside the workflow diagrams when checking how the application should behave.

Trace every statement

Every statement shows where it came from. You can distinguish an instruction from the requirement document from an assumption that still needs confirmation.

  • A requirement document reference includes its page.
  • A user's answer identifies information supplied during design.
  • An accepted AI suggestion shows a proposal your team accepted.
  • An assumption remains marked for confirmation.
  • Already provisioned information identifies configuration that has been put in place.

Use these source labels when reviewing a disputed or unclear detail. They help the team return to the relevant requirement, answer or assumption before deciding what should change.

Keep versions clear

The document carries a DRAFT watermark until approved. That marking keeps an unapproved design recognisable when the PDF is shared for review.

Earlier documents remain available to download. You can return to a previous document when discussing how the configuration developed. Approval does not remove that history.

Secrets appear by name only. Reviewers can see which named secret a configuration refers to without its value appearing in the document.

Trust the source

The document is built only from stored configuration and is never written by AI. The same configuration version always gives the same document.

AI may help during application design, but it does not write this account of the saved configuration. Source labels keep accepted suggestions distinct from user answers, document requirements and unconfirmed assumptions.

Illustrative screen: Configuration document controls show full and summary downloads, draft status and previous documents.
Choose a full document or summary, then review its draft status and available history.

Explore AI Core to see where the configuration develops. Book a demo / pilot to discuss reviewing your application design.

Updated 16 November 2026