Enable self-service management of custom libraries in Draw.io for Confluence Cloud using DRAWIOCONFIG.

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.

We actively promote a self-serve model across our organisation. We are heavy users of Confluence Cloud and extensively rely on custom libraries and templates in draw.io Diagrams.

Currently, development teams can self-manage custom templates using the DRAWIOCONFIG space, which works well. However, custom libraries cannot be managed in the same way. Managing libraries requires Confluence Administrator privileges, which creates a bottleneck between development teams and Confluence administrators.

As a result, development teams must raise tickets and wait for admin intervention whenever a library update is needed. This introduces delays and runs counter to our self-service approach. We would like draw.io Diagrams to support managing custom libraries in the same way custom templates are managed within the DRAWIOCONFIG space, allowing permission-based, self-serve access for development teams.

Describe the solution you'd like

To provide proper context, here is a comparison of the current state and the desired behaviour.

What we have today

• A dedicated DRAWIOCONFIG space used to host custom libraries and templates.

• The space contains the following folders by default:

  1. logs
  2. Configuration
  3. Libraries
  4. Templates

• Uploading a custom template to the Templates folder makes it automatically available when creating a new Draw.io diagram, reducing the need for repeated uploads.

• Uploading a custom library to the Libraries folder has no effect. (This is the issue we are trying to solve)

• Uploading custom libraries via Confluence Administration portal makes them available in new Draw.io diagrams, but:

  • This capability is restricted to Confluence Administrators.
  • Developers must submit requests and wait for manual processing.

What we need

• Uploading a custom template to the Templates folder should continue to make it available by default when creating a new Draw.io diagram.
• Uploading a custom library to the Libraries folder should also:
  • Automatically populate the library when creating a new Draw.io diagram.
  • Function in the same way as templates do today.

This approach would allow development teams to independently manage both templates and libraries, which evolve frequently due to changing requirements and new features.

Describe alternatives you've considered

Due to the current limitations around custom libraries:

• Confluence administrators manually upload libraries via the Confluence Administration portal for each request.
• Developers already have permissions to manage templates within the DRAWIOCONFIG space, which works well.
• However, granting Confluence Admin privileges to developers is not feasible, as permissions cannot be sufficiently scoped to only Draw.io configuration and would introduce unnecessary risk.

Additional context

For additional context, please find the screenshots of the configuration pages we are referring to below:

1. The DRAWIOCONFIG space

2. The configuration page to upload custom libraries

3. Managing libraries and templates within the DRAWIOCONFIG space (when this feature is released)

Start by tracing how the DRAWIOCONFIG space currently makes uploaded templates available and compare that flow with custom libraries managed through Confluence Administration. Confirm the required permission boundary and how new diagrams discover configuration content. Done means libraries uploaded to the Libraries folder behave like templates without requiring Confluence Administrator privileges.