Managing Packages
After installing packages, you can see what they provisioned, take up newer versions, and uninstall packages you no longer need.
Viewing Installed Packages
Navigate to Settings > Packages > Installed to see all packages currently installed in your workspace. The list shows:
- Package name and version
- Installation date
- Update availability
- Resources provisioned (count of services, workflows, forms, etc.)
Click on a package to see its full resource inventory and configuration.
Updating Packages
Package maintainers release new versions that include new features, bug fixes, and improved workflows.
When a publisher releases a newer version of a package you have installed, Nembl shows an Update Available badge on it, with the version number and the publisher's changelog so you can see what changed.
Applying a newer version is not automatic. Nembl does not change or replace the resources already provisioned in your company, so anything you have edited stays exactly as you left it. To take up changes from a newer version, apply them yourself to the resources you want to change.
Because your installed resources are your own, customising them is safe. See Customising Add-on Workflows for the two ways to adapt an installed workflow and how to choose between them.
Uninstalling a Package
Uninstalling removes all resources that were provisioned by the package.
- Navigate to Settings > Packages > Installed.
- Click on the package to uninstall.
- Click Uninstall.
- Review the list of resources that will be removed:
- Services and offerings
- Workflows (draft and published)
- Forms
- Roles (only package-specific roles, not system roles)
- Agent configurations
- Choose how to handle in-flight work:
- Wait -- block uninstall until all active requests in package services are resolved.
- Archive -- close active requests and archive them for reference.
- Confirm the uninstall.
What Is Preserved After Uninstall
- Completed requests -- historical requests and their audit trails are retained.
- Audit logs -- all actions taken within the package's resources remain in the audit log.
- Data exports -- any data exported from the package's services is unaffected.
What Is Removed
- Services, offerings, and their configurations
- Workflows and their versions
- Forms and field definitions
- Package-specific roles (users who had these roles lose them)
- Agent configurations tied to the package
Package Inventory
For each installed package, the detail page provides a complete inventory:
| Section | What It Shows |
|---|---|
| Services | All services created by the package, with their offerings |
| Workflows | All workflows, their status (draft/published), and version number |
| Forms | Input forms and their field configurations |
| Roles | Roles created by the package and which users/groups have them |
| Agents | AI agent configurations and their current autonomy settings |
| Connectors | External connectors required by the package |
Best Practices
- Read the changelog. When a newer version is available, the publisher's changelog tells you what changed before you decide to take any of it up.
- Test on a copy. Before making a substantial change to an installed workflow, copy it and try the change there first.
- Document your customizations. Keep notes on what you changed from the original, so you can decide what to carry across when a newer version appears.
- Uninstall cleanly. Resolve or archive active work before uninstalling to avoid orphaned requests.
- Check role assignments after uninstall. Users who had package-specific roles may need replacement roles assigned.