Publish a module: the module check

What the module check looks at before a module goes live, what must be fixed and what's only advice.

Copy page for AIUpdated November 9, 2026

Every module goes through the module check before it goes live, whether it was made with the Module Builder, your AI assistant or the command line. It keeps a mistake in one module from reaching your data, your people or anyone else's workspace.

Publish from the Module Builder

  1. In the Module Builder, try the preview, then click Publish and confirm.
  2. Watch the progress: loading the files, checking and scanning them, checking the libraries and the AI review, saving the version, then installing it and restarting your workspace's modules. Closing the window doesn't stop it.

When it passes: Published, with the version, and the module is in the sidebar. When it doesn't: Not published, with the reasons. The builder already has them and fixes them in the chat; publish again when it says the check passes.

What the check looks at

  • The module's own description (its manifest): that it's complete and correct.
  • A security scan of its code.
  • The libraries it uses, against the public lists of known vulnerabilities.
  • An AI review against the platform's eleven rules.

Must fix, or advice

Must fix stops the publish. These protect your data:

RuleIn plain words
Data through the platform onlyA module reads and writes records only the platform's way, never around it.
One action, one transactionA change either happens completely or not at all.
Who may see a record is checked on the serverHiding a button isn't enough; the server checks too.
Every entry point has a permissionNothing can be reached without the right role.
Safe screens and linksScreens can't be tricked into running someone else's code.
Secrets and data leaving the workspaceKeys stay secret, and data goes out only where the module says it does.

Serious security findings, and libraries with a known serious vulnerability, also must be fixed.

Advice doesn't stop the publish but makes the module better: using other modules only through their published services, searching and paging in the database, letting the assistant and the help drive every task, and doing what its description says.

Good to know

  • The same build isn't checked twice. A version that passed when you previewed it passes at publish without waiting.
  • Think a finding is wrong? It can be sent to Data Visions for a person to look at; if they agree, that exact build is approved.
  • Changed files need a new version number. The builder raises it for you.

Can't find what you need? Contact support.