Engagement

Scoped engagement

Custom modules for workflows the current product does not cover

For enterprises with an edge case, we work with you to scope a module for that use case. Examples on this page are illustrations, not a catalog of shipped products.

Who it is for

This path is for an enterprise whose records or workflow do not fit the current PersonalOS or BusinessOS modules. Zinits works with that organization to scope the module. It is not offered as generally available software.

How a module is scoped and delivered

The customer describes the edge case. We work with you to scope what the module would do, what it would not do, and how it would sit in the governed workspace. If that scope is agreed, Zinits designs and builds that module as an engagement. The customer reviews it before use. There is no public download and no self-serve catalog.

How it sits inside the governed platform

A custom module is planned to use the same workspace boundaries already described in the manual: tenant-scoped records, permissions, and approval before an external effect. It does not grant host access. Builder remains unavailable and is not the way these modules are offered.

Illustrative examples, not shipped products

  • A record type for an internal document the current modules do not represent.
  • An approval path that follows the customer’s own review chain.
  • A handoff that records work moving between the workspace and a system the customer already runs.

These are examples of what an engagement can discuss. They are not modules you can turn on, and they are not claims about work already delivered.

Contact

Talk to us

Start a custom-module conversation through the existing support contact. Do not include secrets or sensitive records in the first email.

Talk to us