Goal:

As part of the new Jobs to be Done (JTBD) framework adopted by CCS, this must express the JOB that the customer needs to accomplish because of this Engineering epic.

Improve security, allow customers to use different credentials for different services, security and flexibiity
RHOSO admin

In other words, I need the answer the WHY associated with this job of work first.
Then I need to answer the WHAT and HOW questions, for example: As a <User/Actor>, I Want <to Achieve Some Goal>, so that <Some Reason/Context>.

Acceptance Criteria:

Documentation accepted by the PIDONE DFG

Mini content journey:

This must be completed as part of the refinement process

Reviewers: 

• Technical: Luca
• Peer: [Writer name] 
• QE: [name] 

Is this feature fully supported or technical preview? 

• Full support: ** 

Does the procedural content need to be tested by QE? 

• Yes: QE needs to create a doc testing ticket per How-to Jira with the docs team  

Does the documentation epic need a release note in addition to the feature? 

• No: The engineering feature or epic might still need a release note. Engineers need to follow the guidance set in How-to Jira with the docs team. 

What stage of the user journey are you targeting? 

• Adopt: Adoption or Greenfield feature (Early stage customer use) 
• Expand: Customizations, day 2 operations, troubleshooting, add features to control plane or data plane 

Who is your target persona? 

• RHOSO admin: Platform Engineer 

What type of information does the user need to know in order to use the feature? 

• Procedures to implement or enable the feature 
• Procedures to customize or configure the feature after installation 

Does the content need to be included in any of the following guides? 

• Planning guide: Are there prerequisites or planning decisions to add to the Planning guide? 
• Deployment/Customization guide: Does the feature need to be enabled during the deployment process, or can it be enabled post-deployment?