As your application portfolio grows, so does the variety within it. More customers, each with their own standards. More classes of application, each warranting its own treatment. The challenge is meeting that variety without multiplying the manual effort behind it. Until now, App Readiness used a single system-wide configuration, which meant manually reworking that shared setup whenever a different configuration was required. With Settings Groups, we’ve removed that constraint. You can now run multiple complete configurations side by side and choose the right one for each application as it’s added.
If you package for multiple customers, Settings Groups changes the economics of onboarding. If you run a single estate with applications that need different treatment, it adds precision without adding overhead. Either way, the principle is the same: build a settings group once, then apply it to an application with a single choice when adding it to Juriba App Readiness.
Built for Managed Service Providers
If you package for more than one customer, Settings Groups is the feature that scales with you. The model is straightforward: one Settings Group per customer. Each group holds that customer’s packaging identity, not just their output formats but their signing certificate, naming convention, PSADT template, AI repackaging preferences, and smoke-testing rules. When an application is added, you assign it to the right group, and that assignment remains attached to the application thereafter.
Onboarding a new customer used to mean assembling a configuration from scratch. Now it means cloning the group that most closely matches them and adjusting only the sections where the new customer genuinely differs. Minutes, not a from-scratch build. From that point, each customer’s application is assigned to their group as it’s added and retains that configuration for its lifetime. And because the Applications list shows the assigned group against every application and filters by it, you can confirm at a glance that each customer’s applications are running under the right standard.
See it in action: Settings Groups for MSPs .png?width=851&height=423&name=Settings%20Groups%20(1).png)
A Settings Group per customer: each one is a complete, independent configuration, with the assigned group visible and filterable across the Applications list.
Application Subscription: Now Without Compromise
This is where Settings Groups quietly change what automation can do.
Application Subscription has always been one of the most powerful capabilities in App Readiness: subscribe an application to the Juriba Knowledge Base, and when the vendor releases a new version, App Readiness creates and packages it automatically, smoke-testing it along the way if selected. No manual intervention, no missed updates.
Until now, that automation ran against a single set of Automation Settings. Every subscribed application, regardless of which customer it belonged to or how critical it was, was repackaged to the same output type and tested under the same rules. The capability was excellent, but one shared configuration limited how far it could stretch.
Settings Groups removes that ceiling. When you subscribe an application to new versions, it already carries the group you assigned it, and every new version inherits that same group automatically. That unlocks the payoff: fully automated version management across every customer at once, each held to the configuration you set for them, all running in parallel. One customer’s applications flow in as IntuneWin with automatic smoke testing, while another’s produce MSI and PSADT under entirely different rules, hands-free on every update.
For a managed service provider, that is hands-off updates across the entire customer base without a single compromise on per-customer configurations. For an enterprise, it means business-critical applications and routine utilities each follow the treatment they warrant, with no trade-off between automation and accuracy. Subscription automation that finally scales to the real shape of your portfolio.
Flexible for Enterprises Too
Settings Groups is just as useful inside a single organization that runs more than one standard. Different classes of applications call for different packaging treatments. Some warrant full repackaging to MSI or MSIX; others are best wrapped as PSADT; others still are fine running the vendor setup directly with a command line, no repackaging needed. With Settings Groups, each class can be represented by an optional settings group that produces the right output, selected at upload, so no application is forced down a packaging path that doesn’t suit it. This is entirely optional, and many enterprises will be well served by a single standard.
See it in action: Settings Groups for enterprises
What Settings Groups Mean for Your Team
Settings Groups turns configuration from something you maintain by hand into something that scales with your portfolio. For managed service providers, it means onboarding a new customer in minutes and running a fully automated, hands-off version management across every customer at once, each held to its own configuration. For enterprises, it means applying the right rigor to the right applications without adding overhead anywhere else. And for everyone, it means standards stay consistent, packagers stay fast, and configuration stays manageable as you grow.
Settings Groups is available now in App Readiness. To see how it fits your environment, whether you’re running packaging for multiple customers or a single estate with varied needs, book a demo, and we’ll walk you through it.
For a complete overview of setup, assignment behavior, and the worked onboarding scenarios, see the Settings Groups documentation. For the full list of what’s new in this release, please refer to the App Readiness v6.5 Release Notes.
Key takeaways
- Run multiple complete packaging configurations side by side from a single tenancy: one Settings Group per customer, or per class of application.
- Onboard a new customer in minutes by cloning the closest existing group and adjusting only the sections where they genuinely differ.
- Each application’s assigned group stays attached for its lifetime, and is visible and filterable across the Applications list.
- Application Subscription now inherits each application’s group, so fully automated, hands-off version management runs across every customer in parallel, each held to its own configuration, with no shared-configuration ceiling.
- Optional by design: App Readiness still works with a single group, and your existing configuration carries over automatically on upgrade.
Frequently asked questions
What are Settings Groups in App Readiness?
Settings Groups let you run multiple complete packaging configurations side by side within a single tenancy. Instead of a single system-wide setup, you can create a separate group for each customer or application class, then assign the appropriate group to an application when you add it to App Readiness.
What does a Settings Group contain?
Each group holds a complete, independent packaging identity: output formats, signing certificate, naming convention, PSADT template, AI repackaging preferences, and smoke-testing rules. The group you assign stays attached to the application for its lifetime.
How do Settings Groups help Managed Service Providers?
With one Settings Group per customer, onboarding a new customer means cloning the closest existing group and adjusting only what differs—minutes rather than a from-scratch build. The Applications list shows and filters by the assigned group, so you can confirm at a glance that each customer’s applications run under the right standard.
How do Settings Groups work with Application Subscription?
When you subscribe an application to new versions, it already carries its assigned group, and every new version inherits that group automatically. This enables fully automated version management for every customer at once, each with its own configuration and running in parallel. For example, one customer’s applications are produced as IntuneWin with automatic smoke testing, while another’s are produced as MSI and PSADT under different rules.
Can a single enterprise benefit from Settings Groups?
Yes. Within a single organization, different classes of applications often call for different treatment: full repackaging to MSI or MSIX, wrapping as PSADT, or running the vendor setup directly via the command line. An optional settings group can represent each class and produce the right output, selected at upload, so no application is forced down a packaging path that doesn’t suit it.
Do I have to use multiple Settings Groups?
No. Settings Groups is entirely optional. App Readiness still ships ready to use with a single group of product settings, and your existing configuration carries over automatically on upgrade. Additional groups are there only when distinct configurations are genuinely required.
Is Settings Groups available now?
Yes. Settings Groups is available now in App Readiness. You can book a demo for a walkthrough, or read the Settings Groups documentation for full setup and assignment details.
