FAQ-001274 - OEM Embedded Org Security / Platform Features and Capabilities

Additional features or components can be added to OEM embedded orgs beyond the original managed package, provided they align with the contractual and technical restrictions of the licenses. For example, custom objects, fields, and metadata components can be included as part of the solution. However, any additions must comply with the limitations and guidelines specified for the OEM application, such as restrictions on CRM functionality for certain license types.

No changes are recommended for this FAQ. The content is accurate and clear as written. The FAQ addresses OEM embedded org capabilities and licensing restrictions, which is a platform configuration and licensing topic rather than a code security implementation topic. After reviewing all available security rules, none directly relate to OEM embedded org feature additions or licensing restrictions. The security rules focus on code-level security issues (Apex security, encryption, CRUD violations, XSS, etc.) and vulnerable JavaScript libraries, while this FAQ discusses platform licensing and feature capabilities. The existing answer appropriately covers the key points about what can be added to OEM embedded orgs while emphasizing the importance of compliance with licensing restrictions.