Skip to content

GoVisually User Manual

Audience: CPG teams — designers, marketing, Regulatory Affairs (RA), R&D, and print/pre-press.

This manual describes the product as it ships today. Every screen name and button label is quoted from the real interface.


Which sections apply to my role

Your role Read these first Also useful
Graphic designer 03 Uploading proofs and versions, 06 Comparison modes, 09 PDF readiness 04 Review and approval, 10 GIA Chat
Marketing 02 Projects and sections, 04 Review and approval, 05 Sharing 01 Getting started, 12 Smartnotes
Regulatory Affairs (RA) 07 AI Playbooks and Knowledge Base, 08 Running agents and outputs, 04 Review and approval Appendix: checks by category, 10 GIA Chat
R&D 07 AI Playbooks and Knowledge Base (Product Spec files), 08 Running agents and outputs 04 Review and approval
Print / pre-press 09 PDF readiness, 06 Comparison modes, 03 Uploading proofs and versions 05 Sharing (download settings)
Workspace admin 11 Workspace administration, 05 Sharing All chapters

Table of contents

  1. Getting started
  2. Projects and sections
  3. Uploading proofs and versions
  4. Review and approval
  5. Sharing
  6. Comparison modes
  7. AI Playbooks and Knowledge Base
  8. Running agents and outputs
  9. PDF readiness
  10. GIA Chat
  11. Workspace administration
  12. Smartnotes
  13. Appendix: Example checks by product category
  14. Glossary

How this manual is written

  • Button labels and screen names appear in bold quotes: select "Approve".
  • Every procedure uses numbered steps.
  • Screenshot placeholders look like this: ![SCREENSHOT: description]().
  • Terms are used consistently. The glossary defines each term once.
  • In this manual, one uploaded file iteration is called a version. Some screens use the word "revision" for the same thing. The two words mean the same thing in GoVisually.
  • The company account is called a workspace in this manual. Some screens call it a "Team". The two words mean the same thing in GoVisually.

Notes for translators (Korean, Thai)

  • The product interface is in English. Do not translate button labels or screen names. Keep them in English, in bold quotes.
  • Translate all other text.
  • Use the translations in the glossary for product terms. Use the same translation every time.
  • All Korean and Thai glossary entries are proposed translations. They are marked [NEEDS TRANSLATION] until a native speaker confirms them.

Version

This manual is based on GoVisually 1.38.13 (2026-07-06) · Backend 1.93.6 · AI engine 0.1.0 (2026-07-01). When the product changes, this manual is re-verified against the live app before the version note here is updated.