Learn how optional Elaine capabilities, feature activation, tenant configuration, and instance configuration relate to product usage.
Reference
- Elaine environments are configured for contracted channels, modules, capacity, and project-specific needs.
- Some capabilities require activation, additional setup, a compatible template, or integration work.
- A visible UI control does not by itself guarantee that every dependent service is configured.
- Feature availability can differ between tenants, instances, stages, and Elaine.io releases.
How to use this reference
- Describe the business outcome and affected users.
- Confirm licensing, release compatibility, dependencies, data implications, and capacity.
- Enable and configure the feature in a non-production environment where available.
- Test permissions, failure behavior, reporting, and operational ownership.
- Document the approved configuration before production activation.
Important considerations
- Treat feature flags as configuration, not as a substitute for acceptance testing.
- Revalidate integrations and templates when enabling a capability that changes data or rendering.
- Contact the Elaine service team for the authoritative availability of a specific environment.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.