This epic aims to capture the improvements and future opportunities for Job Token configuration that are not covered by https://gitlab.com/gitlab-org/gitlab/-/issues/415519+ and https://gitlab.com/gitlab-org/gitlab/-/issues/342842+. | :pencil: Issue | Notes | Workflow | |----------------|-------|----------| | [Allow users to add multiple groups or projects to the Job Token allowlist](https://gitlab.com/gitlab-org/gitlab/-/issues/459976/ "Allow users to add multiple groups or projects to the Job Token allowlist") | Replace the text input with a dropdown combobox in the Job Token allowlist. | | | [Quick action to allow CI_JOB_TOKEN access across groups](https://gitlab.com/gitlab-org/gitlab/-/issues/438248 "Quick action to allow CI_JOB_TOKEN access across groups") | One-click action for users to declare that all sub-groups inside that the group can access each other using their Job Token. | | | [Add sorting, filtering and search functionality to the Job Token allowlist](https://gitlab.com/gitlab-org/gitlab/-/issues/459978 "Add sorting, filtering and search functionality to the Job Token allowlist") | The allowlist can grow over time. Adding a sort functionality, search field and filter component will allow users to quickly filter and take action. | | | https://gitlab.com/groups/gitlab-org/-/epics/9844+ | Customers seek a centralized view for auditing, management capabilities, and traceability. | | | [CI job token: enable projects to know which allowlists they are on](https://gitlab.com/gitlab-org/gitlab/-/issues/452263) | Improve feature transparency and clarity by displaying a list of "granting projects" on the receiving projects. | |