Browsing & Installing Packages
Packages are curated add-ons that install pre-built services, workflows, forms, roles, and AI agent configurations into your Nembl workspace. They provide ready-to-use process templates for common business functions so you can get started without building everything from scratch.
Package Marketplace
Navigate to Settings > Packages > Marketplace to browse available packages. The marketplace shows packages maintained by Nembl and, in the future, packages published by other companies.
Available Packages
Nembl currently ships 12 curated packages in two tiers. Department packages are broad end-to-end bundles for a function; business-process packages are focused single-process installs you can combine.
Department Packages — $2,900/mo
| Package | Workflows | AI Agents | Roles |
|---|---|---|---|
| Software Development | 8 (bug, feature, release, incident, code review, etc.) | 4 | 8 |
| Human Resources | 5 (onboarding, PTO, performance review, offboarding, recruiting) | 3 | 6 |
| Sales | 4 (lead qualification, pipeline, contract approval, handoff) | 2 | 5 |
| Marketing | 3 (content calendar, campaign approval, event planning) | 1 | 4 |
| IT Operations | 5 (incident, change, access request, asset, provisioning) | 3 | 5 |
| Customer Support | 4 (ticket triage, escalation, knowledge base, CSAT) | 3 | 5 |
Business-Process Packages — $1,900/mo each
Focused single-process packages for teams that don't need a full department bundle.
| Package | What it includes |
|---|---|
| SWOT Analysis | 1 workflow, 3 roles, 1 AI agent (prompts the team, synthesizes notes into a matrix) |
| OKR Tracking | 2 workflows (set, review), 4 roles, 1 AI agent (progress summarizer) |
| Bug Triage | 1 workflow, 4 roles, 1 AI classifier (severity + component assignment) |
| Content Approval | 2-stage approval, 5 roles, 1 AI agent (draft review, brand-voice check) |
| Expense Approval | 3-tier routing by amount, 5 roles, 1 AI validator (receipt check, policy compliance) |
| RFP/Proposal Review | 1 workflow, 5 roles, 1 AI ranker (scores proposals against criteria) |
Use the search bar to find packages by name or keyword. Filter by category, price, or install count.
Package Detail Page
Click on a package to view its detail page, which includes:
- Description -- what the package does and which use cases it covers.
- What Gets Installed -- a breakdown of all resources the package will create.
- Version History -- changelog of updates and improvements.
- Requirements -- minimum plan tier, required connectors, or other dependencies.
- Pricing -- included with your plan or available for an additional monthly fee.
What Gets Provisioned
When you install a package, Nembl creates the following resources in your workspace:
| Resource Type | Example |
|---|---|
| Services | "IT Support" service with pre-configured offerings |
| Service Offerings | "Hardware Request", "Software Access", "VPN Setup" |
| Workflows | Multi-phase workflows attached to each offering |
| Forms | Input forms for request submission with appropriate fields |
| Roles | Package-specific roles (e.g., "IT Support Manager", "Incident Commander") |
| AI Agent Configs | Pre-configured agent prompts and autonomy settings for intake and triage |
| Tags | Standard tags for categorizing resources (e.g., priority, severity) |
All provisioned resources belong to your company and can be customized after installation.
Installing a Package
- Navigate to the package detail page in the marketplace.
- Review the list of resources that will be created.
- Click Install.
- Select the target organization where the package's services and teams will be created.
- Choose the installation mode:
- Managed -- Nembl maintains the package. You receive updates automatically (with approval). Customizations are limited to configuration, not structure.
- Self-Managed -- full ownership. You can modify anything, but you manage updates manually.
- Review and confirm.
- The package installs and provisioned resources appear in your workspace.
Installation typically completes in a few seconds. Workflows are created in draft mode so you can review and publish them when ready.
Post-Installation Steps
After installing a package:
- Review provisioned workflows. Open each workflow in the builder to understand its phases and transitions.
- Assign teams. Map the package's services to the teams that will handle them.
- Configure agents. Review the AI agent configurations and adjust autonomy levels for your comfort.
- Customize forms. Modify the input forms to match your company's terminology and required fields.
- Publish workflows. Once reviewed, publish the workflows to make them active.
- Assign roles. Add the package's roles to appropriate groups or users.
Package Requirements
Some packages have prerequisites:
- Plan tier -- certain packages require Starter, Growth, or Business plans.
- Connectors -- a package may require a Slack or GitHub connector to be installed and authenticated. See Connectors.
- Dependencies -- a package may depend on another package being installed first (e.g., Incident Management depends on the base IT Operations package).
The marketplace shows unmet requirements with a warning before installation.
Best Practices
- Start with one package. Install a package that matches your most pressing need, learn how it works, then add more.
- Use Self-Managed mode for heavy customization. If you plan to significantly modify the workflows, choose Self-Managed to avoid conflicts with future updates.
- Use Managed mode if you want updates. Managed packages receive improvements and fixes from the package maintainer.
- Review before publishing. Packages install workflows in draft mode intentionally. Use this to adapt the process to your team before going live.