From my testing, this is the only attribute that is required for me to be in the context of an organization and load up the entity. This raises a question that was not addressed or discussed in our planning with respect to filtering. To enable filtering of specific entities we would need to add more attributes here and enable Foreman auto complete search on the UI controller for the entity. I debated whether this should be included as part of this story, or if filtering options were another story all together - so I went the minimum route first. An example of what auto complete takes to achieve is:

https://github.com/Katello/katello/pull/3789/files

This leads to a bit of a design question given that there is impending work (https://github.com/Katello/katello/pull/3979) to remove/centralize resources to a single controller. This leads to two questions:

1. Can this generic controller introduced handle the auto complete search generically?
2. Should the index methods of the API controllers be what is handling this auto complete behavior? (this might require more work than there is time for).