Document URL:
https://docs.theforeman.org/nightly/Managing_Content/index-satellite.html#Managing_Red_Hat_Subscriptions_content-management

Section Number and Name:
3. Managing Red Hat Subscriptions

Describe the issue:
Much of this section is obsolete for anyone using SCA (Simple Content Access.)

Suggestions for improvement:
In SCA mode, things are easier:

• For future-dated subscriptions, you still must add them to your manifest (subscription allocation), but you don't need to attach them to content hosts.

• The entire section 3.6. Attaching Red Hat Subscriptions to Content Hosts, is neither required nor possible in SCA mode.

• Same for 3.7. Updating Red Hat Subscriptions on Multiple Hosts

Section 9. Managing Activation Keys also needs an update.
9.1. Creating an Activation Key - The entire blurb here (everything before "Custom Products") only applies to organizations not in SCA mode. In SCA mode, it is neither required nor possible to attach a subscription to an activation key, and auto-attach isn't a thing.

9.2. Updating Subscriptions Associated with an Activation Key - This entire section only applies to organizations not using SCA.

9.4. Enabling Auto-Attach - This entire section only applies to organizations not using SCA.

9.6. Enabling and Disabling Repositories on Hosts - This applies to both SCA and non-SCA orgs. It may be good to note here that in SCA mode, a lack of an attached subscription will not prevent a content host from having access to custom products, because custom products are always enabled by default. So in SCA mode, you'll need to use other strategies for restricting access to content, including disabling repositories and using content views/LCEs.

Side note about 9.6. Enabling and Disabling Repositories on Hosts - These instructions apply to hosts, not activation keys. So maybe this section is in the wrong place. However, activation keys also have a Repository Sets tab and the procedure is pretty much the same, so we should add a section here for that.

The Content Management guide also needs instructions for how to enable or disable SCA for an org. (it's a checkbox on the organization's Edit page.) It should also mention that SCA defaults to on for newly created organizations.

Additional information: