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.
Browsing by Category
Packages are organized into domain categories:
| Category | Example Packages |
|---|---|
| Software Development | Agile Replacement, Code Review, Release Management |
| IT Operations | Incident Management, Change Management, Asset Tracking |
| Human Resources | Employee Onboarding, PTO Requests, Performance Reviews |
| Sales | Lead Management, Quote-to-Cash, Customer Onboarding |
| General | Approval Workflows, Document Management, Feedback Collection |
Use the search bar to find packages by name or keyword. Filter by category, popularity, or rating.
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.