Application Composition

The composition of applications has changed since the Sunflower release. As we continue to split up the original “mega” applications into more appropriately sized and logical groupings, new applications have been introduced. Modules have been moved from places like app-platform-complete into these new applications. For a full list of modules and which application they live in (for both Sunflower and Trillium), please refer to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix See also https://github.com/folio-org/platform-lsp/blob/R1-2026-GA/platform-descriptor.json.

What does this mean for me?

For end users, application composition changes will probably only be visible/have an impact of those who are managing roles. When creating or editing a role, applications are selected, which controls which capabilities are shown on the create/edit form. The refinement of application composition will mean more applications to choose from, but also finer granularity. This means you’ll have more control over which capabilities are shown, potentially reducing the number of irrelevant capabilities shown for the roles you’re managing.

For system operators, there will be new applications to register and enable, but beyond that the impact of this should be minimal.