Description:

We are currently using Harness Module Registry at the project level. However, users with account-level permissions can create or modify registries across projects, even when selecting project-level repositories. We need:

A mechanism to restrict users so they can only manage registries within their own project.

An approval workflow or gate during module creation to ensure governance and review before modules are registered.