Content modules
Install global workflows, agents, skills, and knowledge types from the module catalog.
Content modules
Content modules distribute global catalog resources — workflows, agents, skills, ticket views, knowledge types, labels, and optional custom actions — to projects through installable bundles.
ArxDeck Helper can search published modules and propose configuration for module-backed resources. It does not auto-install modules — admins install from the catalog or approve Helper proposals for manifests.
Built-in system module
ArxDeck Helper and its setup skills ship in the locked system content module arxdeck-system:
- Auto-installed and active on every project (including new projects)
- Cannot be deactivated or uninstalled (
installPolicy: locked) - Bundles the global agent ArxDeck Helper and the setup-helper skill
You do not install or activate Helper separately — see ArxDeck Helper.
Install and activate
Project admins:
- Install a published module to add its resources to the project
- Deactivate optional modules to hide resources from new-work pickers (historical references remain readable)
- Reactivate to restore pickers
- Set default workflow and optional default ticket view among selectable module resources
Superadmins create, publish, and archive modules under Platform → Modules.
Labels via modules
Global labels can ship in content modules. Installed module labels appear as read-only entries in the project label list with alias management. Project admins create additional project-local labels at Settings → Labels.
Custom actions
Modules may define actions — buttons that launch a conversation with a configured agent using a starting message and either starts immediately or awaits user input. Legacy actions without a non-empty starting message stay disabled until an operator remediates them through configuration proposals or platform settings. Launch requires an active module installation and chat create permission. Configuration proposals may reference pending module or agent creates with @ref:<alias> on moduleId and agentId; updating an action without description preserves the existing description. Module update proposals accept partial payloads — omitted metadata is preserved, and lifecycleAction: "publish" may be sent without resending name or category.
Capability requirements
Modules can declare required project capabilities (for example feedback or web_publish). Installation shows whether each capability is enabled; install does not auto-enable capabilities.
Project templates
Organization admins can create new projects from templates that pre-install content modules and set defaults. See Projects and create flow at /settings/org/projects/new.
Setup & configuration
- Open Project → Modules (under Data in the sidebar) to browse the catalog.
- Install modules your team needs (workflow packs, agent templates, knowledge type bundles).
- Set defaults via Settings hub entries for workflow and ticket views.
- Use module-backed settings pages — each lists Module resources at the bottom with read-only links to global definitions.
For new global module manifests, superadmins use Platform → Modules editor; project admins use Helper chat to propose changes when appropriate.