Feed

Hi @Emma,

For the licenses, the Salesforce User license is usually the go-to because it unlocks all the MCC needs to function smoothly, like sending emails, syncing data. The Salesforce Integration User license is a bit more limited, so while it might seem tempting, it could end up restricting some of the MCC functionalities you're keen on using.

If you're leaning towards the Integration User license, it's a good idea to have a chat with your Salesforce rep. They can give you the lowdown on whether this license will cover all your bases without leaving you wanting more.

Now, onto the CRM API User's profile. Crafting a custom profile with just the permissions you need is a smart move. It keeps things secure without putting a damper on functionality. Pinpoint the permissions essential for your MCC tasks, set up a profile around them, and yes, implementing a non-expiring password policy with solid security measures is wise. Just remember to run some tests in a sandbox to make sure everything's ticking along nicely before you launch it into production.

This approach keeps your integration tight and secure while ensuring you've got the access you need. Just a heads-up, though: keep an eye on those permissions and be ready to adjust as needed. Salesforce and MCC evolve, and so should your settings.

Hope that helps!

@Kellen Kirby No, you don't need to show the checkbox field in the screen flow. When the user clicks the button for the first time, the flow will run, performing whatever logic is needed. At the same time, you can update the checkbox field on the record to "true." Even if you're doing something like creating a different record, you can still update the original record by querying it with the recordID and making the update. This checkbox can then be used in the flexi page to control whether the button is visible. If the checkbox is "false," the button will show; if it's "true," it will be hidden. This is all handled in the backend, so the user won't see the checkbox field.