Release Channels and Early Access

Use this page to explain how Soracom can publish generally available guidance while protecting pilot-only details, rollout steps, or account-specific instructions.

Release channels

The docs platform can support three common visibility modes:

• Public for content anyone can read.
• Gated for content that stays routable but only renders after sign-in or entitlement checks.
• Hidden rollout content for documentation that should return a not-found response unless the signed-in operator is entitled to the feature.

When to use fragment gating

Fragment gates are useful when most of the article is public but a sentence, callout, pricing note, or configuration block should stay behind authentication.

The recommended default is Loading private content….

Example: operator-only rollout checklist

Recommended authoring pattern

1. Keep the general product explanation public.
2. Gate operator-specific rollout details inline or as a block.
3. Move the whole page to access: gated only when the entire body is rollout-specific.

Related

• Feature Rollout Controls
• Event Handler