Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

This feature came to be based on a suggestion that was made in this comment. 

Currently the RBAC backend plugin has the ability to filter roles based on ownership through the use to the `isOwner` conditional rule. However, it has been pointed out that this can lead to some bad UX scenarios. Primarily, whenever a user (one who has the `isOwner` conditional rule applied to them) creates a role and assigns a different user to be owner of said role. The result is that they are no longer able to view this role due to the fact that they are not said owner.

That is why we are proposing another conditional rule `isAuthor` that will filter based on whether or not the user authored the role and permissions. This would then allow admins the ability to grant both rules and prevent the aforementioned scenario.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

Introduce an new rule for filtering roles based on authorship

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

Admins are able to create a role and include the new conditional rule `isAuthor` to limit access based on authorship

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>