Currently, Managing Red Hat subscriptions (Managing content guide) requires the user to jump to the Subscription Central docs in the prerequisites of procedures. This is not a good user experience. The introduction does not explain the Subscription tooling or the features mentioned in the KCS, Subscription Management Admin guide for RHEL:

• Tracks selected Red Hat product usage and capacity at the fleet or account level in a unified inventory and provides a daily snapshot of that data in a digestible, filterable dashboard at console.redhat.com.
• Tracks data over time for self-governance and analytics that can inform purchasing and renewal decisions, ongoing capacity planning, and mitigation for high-risk scenarios.
• Helps procurement officers make data-driven choices with portfolio-centered reporting dashboards that show both inventory-occupying subscriptions and current subscription limits across the entire organization.
• With its robust reporting capabilities, enables the transition to simple content access tooling that features broader, organizational-level subscription enforcement instead of system-level quantity enforcement.

Simple Content Access is also not mentioned except in a note in section 2.1. The KCS article needs to be incorporated into the existing Managing RH subscriptions section.

Task scope:

• Create clear description of use cases including benefits, drawbacks of connected vs disconnected. For the sake of completeness, add a brief description of non-Satellite use cases, aka "Deployment Types" in KCS (connected - RHEL tools; disconnected - 3rd party tools).
• Expand concept module to include SCA description.
• Add features list, especially the list of use cases mentioned in the KCS (tracking data for purchasing and renewal, planning, risk mitigation, portfolio management).
• Replace links to Subscription Central docs with procedure modules for creating and exporting manifests. We should be maintaining our own documentation. (The SC docs look dated. Notes refer to SCA availability in 6.5 and SCA setting for organization in 6.13.)
  Add procedure for configuring subscription services (connected - foreman_rh_cloud plugin; disconnected - export by using foreman_rh_cloud plugin or reports)
• Check existing procedures against the console for accuracy if this has not been done recently.

NOTE: We might want to consider creating a new guide and retiring the SC guides if SCA/subscription management turns out to be too long for the Managing content guide.