Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

What problem/issue/behavior are you having trouble with?  What do you expect to see?

Within the 'Product and Repositories'  RBAC Resource type, there are options to view, create, edit, destroy and sync products. However there do not seem to be any controls to allow the same actions for repositories. 

We are permissioning users and teams to their own Product. We want to allow users to be able to CREATE their own repositories in this product but DENY them the ability to CREATE products.

(Products / Repositories seem to share the same permissions?).

I want to see the:

view_repositories
create_repositories
edit_repositories
destroy_repositories

Permissions so that users can create / modify repositories they have access to but be denied the ability to create more products.

Per 6.3 planning, moving out non acked bugs to the backlog

Created redmine issue http://projects.theforeman.org/issues/18133 from this bug

*** This bug has been marked as a duplicate of bug 1410916 ***