Ability to apply process template after defining component properties

When a Project Area is created, if user uses Process Template (instead of process sharing) the permissions are not translated as-is from the template project.

For example: Suppose permissions to create artifact of artifact type X is permitted and artifact type Y is not permitted in template project. If process template from template project is used, then in the new project, permission to create artifact of type X and type Y both are not permitted
This is because the artifact types don't yet exist.

But after the project/component properties are defined, be it using Project/Component Template or inheriting project properties, there should be a way to re-apply/refresh process template so it can accurately reflect permissions using the project/component properties.

Right now, even after using Project/Component Template or inheriting project properties, permissions to create artifact of type X and type Y will still be not permitted. User needs to change this manually afterwards.

If users have the ability to refresh/re-apply Process Template, then users can create new projects with same project properties and permissions as a parent project, using templates instead of inheritance, which creates a dependency between the 2 projects. Over the course of time, they can modify permissions very differently in both projects and create a new template/inherit permissions to a new project from the project they want to use now.

Example:

Project Child is inheriting permissions by using process sharing from Project Parent

Over time Project Child's permissions were changed and so were Project Parent's. And user now wants to use Project Child's roles and permissions in another project. But they cannot, because if they change process sharing options, they loose permissions from Project Parent. If they create a Process Template from Project Child, they get the roles, but don't get the permissions at granular level same as Project Child.

But if they were able to create a Project New using Project Child's process template, then apply Project Child's project/component properties, then re-apply/refresh process template to accurately have permissions for defined artifact types, attribute types, workflows etc, then can successfully create a new project with same permissions as Project Child.

Right now the only way to create same permissions between 2 projects is by using process sharing and project properties inheritance. There is no way to do this using templates, which allows the 2 projects to be independent.