User Story

User Story

As a user I want my initial RBAC setup to be more seamless than requiring an organizational admin so that I can get up and running sooner.

As an application on the platform I want to make use of the latest RBAC features so that we can offer the best initial user experience.

UX Requirements

Will UX need to have some guidance for the user to move over to RBAC

UI Requirements

• Does the UI require a API contract with the backend so that UI could be developed prior to completing the API work?

Documentation Requirements

• Document the new default RBAC setup – could potentially link to a generic RBAC doc on managing roles

Backend Requirements

• We’ll likely have some RBAC config setup to associate this role with the default group???
• https://github.com/RedHatInsights/rbac-config
• We need to understand if this will stay on the roadmap for RBAC – so there’s work on our end to ask/sync with RBAC team to coordinate on this.

QE Requirements

• Update to QE rbac tests?

Additional Information and Assumptions

• This is dependent on this feature being built out by the platform RBAC team.

Acceptance Criteria

• The Cost Administrator RBAC role is part of the Default Admin RBAC Group

Dependency

• Talk to RBAC team: We need to understand if this will stay on the roadmap for RBAC – so there’s work on our end to ask/sync with RBAC team to coordinate on this.