This is inferred from the current visible business mix and can be overridden later.
Settings now have a grouped owner page with industry-aware context.
The owner can now see how language, framing, and priorities should bend to the business rather than staying generic.
Live DB truth: outbound registry exists but no ready inboxes are currently available.
The schema is now real, but no prospects, outbound inventory, or action ledger rows exist yet, so Ignite is truthfully in empty bootstrap mode.
Settings stay tied to what the business needs next.
Which owner language profiles are locked at launch
These options keep Ignite from talking like generic software.
Changing industry should change language, proof, priorities, and data framing.
Changing industry should change language, proof, priorities, and data framing.
Changing industry should change language, proof, priorities, and data framing.
Changing industry should change language, proof, priorities, and data framing.
Changing industry should change language, proof, priorities, and data framing.
Changing industry should change language, proof, priorities, and data framing.
What changing industry should actually affect
Settings are not cosmetic; they change how Ignite presents the business.
Industry affects language, priorities, proof framing, and data presentation.
Industry affects language, priorities, proof framing, and data presentation.
Industry affects language, priorities, proof framing, and data presentation.
Advanced inspection stays attached to the page context.
This panel does not replace the owner view. It gives a deeper truth path for the current grouped page without forcing a detached admin detour.