This guide provides insights on what to expect when CME MP and RC operate side by side
in the same org independently, without interoperating. It covers design-time configuration,
including setup, metadata, and data model, and run time behavior, including user flows,
automation, and UI.
Required Editions
| Available in: Classic and Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer
Edition |
There are two types of operating models that can be in use. Both of them have different
implications.
Separate users setup: Assign Distinct CME MP only and RC only users on the app (CME MP or RC)
via profile or permission set. How the boundary is enforced: Permissions enforce the boundary
so that a user only reaches their app (CME MP or RC) surfaces. Strongest isolation.
Common or Shared user setup: One identity carries both apps (CME MP and RC). How the boundary
is enforced: Permissions can’t enforce the boundary as it relies on app (CME MP or RC) such as
scoped surfaces, the record differentiator, and validation rules. The differentiator does the
heavy lifting.
