Skip to main content

Templates

Templates package reusable workflow patterns so teams can start faster with governed execution.

What this means​

Templates provide an operational starting point with structure, controls, and expected evidence patterns.

Why it matters​

Teams often repeat similar processes with small variants. Templates reduce setup time while improving consistency.

How Subbasis handles it​

Template assets can carry:

  • workflow shape
  • required connectors
  • skill guidance
  • evidence expectations
  • approval pattern defaults
  • model resource hints

Template content​

  • Workflow shape
  • Required connectors
  • Skill guidance
  • Evidence expectations
  • Approval pattern defaults

Example scenario​

Support triage template:

  • intake classification
  • severity-based routing
  • approval for sensitive customer actions
  • connector integration with ticketing system
  • evidence events at each escalation

What to configure​

  • organization-specific policy rules
  • connector credentials and scope
  • role assignment
  • approval owners
  • plan-aware limits

Limits and deployment notes​

  • Template availability and depth may depend on marketplace/deployment context.
  • Templates accelerate rollout but still require governance validation.

Explore Marketplace assets.