Packs are starting points, not automatic integrations
An industry pack can supply available agent definitions, prompts or workflow starting points for a domain. Inspect exactly what the selected pack installs. Its presence does not provision external accounts, certify a workflow or guarantee a business outcome.
The Industry Packs screen is administrator-oriented. Department users work through permitted agents, workflows and role-specific dashboards after configuration.
Use a pack responsibly
- Choose a pack aligned with a real process and accountable owner.
- Inspect the agents, tools, prompts, dependencies and intended outputs.
- Review installed/created candidates in the correct company context.
- Configure model credentials and required business connectors separately.
- Replace example procedures with approved, current content.
- Test with synthetic data and explicit refusal scenarios.
- Promote only the tested components needed for your pilot.
If a pack or template names an unconfigured provider, it is not ready to run. A template's confidence setting is not measured accuracy.
Department workspaces
| Workspace | Typical work | Human boundary |
|---|---|---|
| Finance/CFO | AP/AR, reconciliation, treasury, expenses, close and analysis | Posting, release and financial sign-off require the configured authority |
| HR/CHRO | Onboarding, recruiting, learning, payroll preparation | Employment and payroll decisions remain authorized human processes |
| Marketing/CMO | Research, content, campaigns and CRM follow-up | Publishing, spend and customer communication need explicit permissions |
| Operations/COO | Support, contracts, vendors and IT exceptions | System changes and contractual actions need review |
| Partner/company workspaces | Multi-company operations and client context | Company selection never bypasses tenant isolation |
Dashboard visibility is role-based. A missing menu can be expected permission behavior. Metrics describe the screen's data and reporting window; do not treat every summary as a full-day live total.
BFSI configuration examples
Bank onboarding can use governed cases with reviewed evidence providers and decision authority. Insurance assistance can use a custom document-review agent plus OCR and workflow approvals. Reconciliation can use finance definitions with a bank's approved ledger/export interface. These are explained in the BFSI playbooks, not presented as universally installed bank products.
Maintain the business layer
Assign prompt and policy owners, an approval backup, connector operations and a training owner. Review pack changes before updating deployed candidates. Measure task quality against human-reviewed cases rather than counting how many agents were installed.
Next: Create agents, Adoption checklist.