Skip to content
Spaces

Document Spaces

Living documents, right beside the work they describe.

  • Comments, suggestions and approvals
  • Version history on every document
  • AI documentation saved alongside
Illustration of a SyncupHUB space: a BRD with functional requirements and acceptance criteria, a comment thread, version history and an approved status
Illustration from the SyncupHUB film

What are Document Spaces?

Document Spaces are collaborative documents inside SyncupHUB, organised into spaces for a product, programme or team. They support comments, suggestions, approvals and version history, and they sit next to the work they describe, so a BRD, a runbook or an architecture note is one click from the stories and decisions it governs.

How it works

  1. Write where the work is

    Create a space for a product, programme or team and keep its documents beside the backlog, rather than in a separate wiki.

  2. Review in place

    Reviewers comment and suggest edits on the text itself, and the author accepts or declines each suggestion.

  3. Approve and version

    A document moves through review to approval and every version is kept, so you can see what changed and who agreed to it.

  4. Keep generated knowledge

    Architecture, API and schema documentation produced from repository analysis can be saved into a space, next to the documents people wrote.

What’s included

  • Spaces for a product, programme or team
  • Comments and suggested edits
  • Review and approval
  • Version history
  • BRDs with numbered requirements and acceptance criteria
  • Export of BRDs to Word
  • AI documentation saved to Spaces
  • Attachments in S3-compatible storage you control

What it needs

Stated plainly, before a demo does.

  • AI-drafted content stays labelled separately from confirmed input.
  • Attachment storage uses an S3-compatible bucket you configure.

Questions about Document Spaces

How are Document Spaces different from a wiki?

A wiki sits beside the work; Document Spaces sit inside it. Each document lives in a space for a product, programme or team, next to the stories and decisions it describes, with comments, suggestions, approvals and version history built in rather than added on.

Can documents be approved and versioned?

Yes. A document moves through review to approval and every version is kept. A BRD is re-approved when its source changes, so the approved version is always the one the team is building against.

Can I export a BRD to Word?

Yes. Business Requirements Documents built in SyncupHUB, with objectives, scope, numbered requirements, acceptance criteria, journeys and open decisions, can be exported to Word for sign-off outside the workspace.

How do Spaces work with AI Documentation?

AI Documentation analyses a repository and produces source-linked architecture, API, schema and flow documentation. Teams can save it into a space, where it sits beside the documents people wrote and is reviewed the same way.

Related features

Visual Canvas

Sticky notes, flows and architecture on one board, with every shape linked to real work.

Learn more

Requirement to Code Traceability

Follow a requirement to the code that shipped it, and recover requirements from code that exists.

Learn more

QA Intelligence

AI-drafted test cases from acceptance criteria, approved by QA and traced to the requirement.

Learn more

See Document Spaces on your own delivery

A 30-minute walkthrough on your delivery model, not a generic demo.