Home › Opt-in and enablement

How Oracle Fusion opt-in and enablement work

A short glossary of Oracle's Action to Enable labels, with live 26D figures as examples. The labels come from Oracle; the counts come from our weekly extract of Oracle's What's New tables.

In short: Each Oracle Fusion Cloud What's New row has an Action to Enable. On by default (Action: None) means users can meet it when the update lands. Opt-in stays off until an admin enables it; Opt-in plus Setup also needs configuration. Some older opt-ins expire and become now standard — a subset switches on for everyone, others need setup if you want them. For 26D, across the modules we cover, Oracle's Feature Summary tables list 173 on by default, 124 on by default with potential setup, 89 opt-in, 361 setup required and 21 needing another action (out of 768 features). Oracle also lists 23 opt-ins that are now standard with 26D (9 automatic, 14 setup).

Action to Enable, in plain English

Oracle label	What it means for you	26D count (modules we cover)
None	On by default when the update lands	173
Potential Setup	On by default; Oracle flags setup you may need	124
Opt In	Stays off until an admin opts in	47
Opt In plus Setup	Opt-in, then configuration	42
Setup Required	Off until set up (no separate opt-in step)	361
Other (e.g. Visual Builder, Service Request Required)	Follow the action named on Oracle's feature page	21

Source: Feature Summary "Action to Enable" column in Oracle's 26D What's New documents. Total rows in our extract: 768.

Former opt-ins that are now standard

Oracle's Current Opt-In Expirations list names features whose opt-in period ends with a given release. From that release they are now standard. For 26D that is 23 features: 9 switch on for everyone (Oracle's "Now enabled" = Yes) and 14 need setup if you want them.

26D former opt-ins now standard → · 26D new opt-in features → · 26D on by default →

How to use this each quarter

Read the release hub for counts by Action to Enable (for 26D: 26D hub).
Shortlist opt-ins your business owners asked for; leave the rest off until you need them.
For features that are now standard, check whether Oracle's "Now enabled" is Yes or whether setup is still required.
Test in the pod that receives the update first, then confirm production matches what you signed off.

Frequently asked questions

What does "on by default" mean?

Oracle's Action to Enable column says None: the feature is delivered ready for users when the update reaches the environment. Some rows are "Potential Setup" — still delivered enabled, but Oracle flags prerequisite or optional configuration.

What does "opt-in" mean?

The feature stays off until an administrator opts in. "Opt In plus Setup" also needs configuration before anyone can use it. Nothing changes for end users if you do nothing.

What does "now standard" mean?

Oracle first shipped the feature as an opt-in. Its Current Opt-In Expirations list names a release where that opt-in step ends, so from that release the feature is part of the standard product. Some switch on for everyone; others still need setup. See 26D former opt-ins now standard.

Where do the 26D counts on this page come from?

From Oracle's 26D What's New Feature Summary tables for Financials, Procurement, SCM, Logistics, Projects and HCM (our extract: 768 rows), plus Oracle's Current Opt-In Expirations list for the 23 that end with 26D. Counts are examples for the current release, not permanent facts.