Idea ID: 2871858

Restrict "manage content pack" permissions to individual content-packs

Status : Waiting for Votes

Hello Community

As we extend the usage of OO, we find it a problem that flow authors/developers with "manage content Pack" entitlement/permission can manage any content pack.

This is especially troublesome in production environments.

The proposed "promotion process" suggested by microfocus relies on a central team that manually does these deployments. I find that solution out-dated and not aligned with the now more predominant devops/agile principles.

I've seen other teams develop solutions using CI/CD but to me that is the other end of the spectrum, and not all developers will be able to adopt it.

Asking for a way to "restrict" permissions so that manage content pack can be granted but probably then restricted to specific content packs through an allow or deny flag.


OO - Platform