Feature Overview

The Automation Hub currently lacks the capability to create namespaces or private collections restricted to a specific team of users. This missing functionality cannot be mitigated by utilizing another Automation Hub, as only one credential type is permitted.

Moreover, relying on Source Code Management (SCM), such as GitLab, poses challenges because it necessitates granting the Git credential access to both the Ansible project repository and the repositories of referenced collections in the requirements.yml file.

In a broader context, promoting the use of Automation Hub would be more straightforward if the solution offered a unified interface for both the company's public collections and private ones.

The business impact of this absence is significant, as the client is subject to regulatory constraints in the banking sector. Some assets cannot be made public on the platform and require access control measures.