Workspaces
Optional role-based operating environments that appear in the Metatility OS Workspaces menu after organizational activation.
Metatility Marketplace
Choose the operating capabilities your organization needs.
The Marketplace is where organizations discover and activate optional Workspaces, verified packages, modules and controlled connectors for Metatility OS.
MKT / 03METATILITY SYSTEM / ACTIVE
What you can activate
Activation extends Metatility OS—it does not install another application.
Activated Workspaces and packages inherit the organization, identity, permissions, canonical data model and audit history of Metatility OS. Connectors are reserved for legitimate external boundaries.
Vendor Packages
A manufacturer or supplier handoff containing products, SKUs, pricing, policies, documents, training, territories and support rules.
Industry Operating Packages
Terminology, entities, roles, workflows, rules and reporting that configure Metatility for a business or industry.
Capability Modules
Bounded native functionality added to an Engine or Workspace without creating a separate application or data model.
Workflow Packages
Preconfigured states, approvals, exception handling and operating sequences for repeatable work.
Intelligence Packages
Authorized rules, analysis, simulations and recommendations for a defined operating domain.
Connectors
Controlled boundaries to specialist external systems that must remain independent, such as accounting, banking or engineering platforms.
Workspace activation
From Marketplace listing to the OS Workspaces menu.
Availability is controlled at both the organization and user level. A company activates the capability; administrators decide who can see and use it.
01Select workspace
02Confirm terms + dependencies
03Activate for organization
04Assign authorized roles
05Workspace appears in OS menu
Package versus connector
Transfer operating knowledge where possible. Integrate only where necessary.
Becomes native to Metatility
- Structured product and business information
- Roles, rules and operating workflows
- Documents, training and policies
- Uses Metatility identity and governance
- Operates in native Workspaces
Controls an external boundary
- Used only when a specialist system remains independent
- Declares record ownership and data direction
- Validates every authorized exchange
- Handles failure and conflicting updates
- Preserves the transmission audit trail
Marketplace governance
Every publisher, scope, permission and dependency is verified before activation.
Identity + publisher verification
Data-scope disclosure
Permission boundaries
Version + dependency control
Policy + territory enforcement
Audit-ready activation
One governed environment