Power Platform Community Forum Thread Details

We need to prevent users from being able to update the "Track Email Messages" setting at the user level.

To my understanding, this change takes place in the Org DB settings.

Prior to the new look ( new UI ), I believe the changes were made within the Org DB solution.

Now, it looks like we need to use XRM toolbox, Org Settings tool and set HideEmailAutoTrackOptions to true.

1) Is XRM toolbox the correct place to make the change and does this change need to be manually made in each environment? As stated above, I remember these changes needed to be made in the solution but with it being managed there is no way to import to PRD so I assume this is no longer the way to update?

2) Will admins still have access to update this setting using XRM toolbox User Settings Utility?

3) I dont recall ever having to update the Org DB settings. Is this a risky update and are there any downsides in doing so? There is a warning message in the tool saying ensure you have a back up of the current settings prior to changing them.

4) No other settings will automatically get updated if we change HideEmailAutoTrackOptions?

Thanks you!!

Categories:

Microsoft Dataverse with Power Apps

Hi @nvrhughes,

Firstly, note that I am contributing some research as this has not been responded to yet. Also noting I do not use this tool, so I hope that the content below is of some use to you.

Some trouble shooting

Is XRM Toolbox the correct place to make the change and does this change need to be manually made in each environment?
Yes — XrmToolBox + Org Settings Tool is the right approach for this setting.
- HideEmailAutoTrackOptions is not exposed in the Power Platform Admin Center 0or UI; it’s only available through OrgDBOrgSettings (the Org DB settings).
- These settings are environment-specific, so yes, you’ll need to update them individually in each environment (DEV, TEST, PROD, etc.).
- Previously, you may have been able to tweak these from the "Email tracking" UI, but now with the "new look," OrgDBOrgSettings is the supported way.
  Important: Because it’s an environment-level setting, it cannot be exported via solution and imported into PROD. Manual update is the only way.
Will admins still have access to update this setting using XRM Toolbox User Settings Utility?
- No — not this one.The User Settings Utility in XrmToolBox updates user-level personal options (e.g., default view, default dashboard, email tracking preferences if they are exposed).
- Once you enable HideEmailAutoTrackOptions = true, the option is hidden from the user interface. Even admins won’t see the toggle in users’ personal settings anymore.
- Admins can still override other user settings with the utility, but not this specific one once hidden.
Is updating Org DB settings risky? Downsides?
Generally low risk if you know what setting you are changing.
- OrgDBOrgSettings are Microsoft-documented supported settings. The tool (XrmToolBox Org Settings Editor) simply exposes them in a friendly UI.
- The warning is generic — because you are changing a database-level flag. That’s why it’s always recommended to take note of the current value before changing (so you can roll back).
- No known performance or stability issues with this particular setting.
  
  So: low risk, just follow best practice:
- Backup value before changing.
- Test in sandbox first.
- Apply in PROD after validation.
Will other settings automatically update if we change HideEmailAutoTrackOptions?
No.
- These OrgDBOrgSettings are independent flags. Changing one does not cascade into others.
- The only effect of HideEmailAutoTrackOptions = true is that users will no longer see the "Track email messages" option in their personal settings.
- Existing user selections are preserved, but since they can’t see or change them, it effectively locks the org-level default in place.

Summary / Recommendation

Use XrmToolBox + Org Settings Tool.
Update setting manually in each environment.
Admins won’t be able to override per-user once hidden.
Safe to change; just record the old value.
No impact on other OrgDBOrgSettings.

Steps to update HideEmailAutoTrackOptions

Prep
- Ensure you have XrmToolBox installed and can connect to your Dynamics 365 / Dataverse environment.
- Make sure you have System Administrator security role.
- (Optional but recommended) Take a screenshot/export of current OrgDBOrgSettings so you can roll back if needed.
Connect to your environment
- Open XrmToolBox.
- Go to Connections → Add new connection.
- Select Microsoft Dataverse connection.
- Authenticate with your admin credentials.
Open Org Settings Tool
- In the XrmToolBox home screen, search for “Org Settings” or “OrgDBOrgSettings Editor”.
- Launch the plugin.
- Once it loads, it will display all available OrgDBOrgSettings and their current values.
Change HideEmailAutoTrackOptions
- In the search bar, type HideEmailAutoTrackOptions.
- Select it - Default value is usually false.
- Change the value to true.
- Click Update (or Save depending on plugin version).
Validate
- Log into Dynamics as a normal user.
- Go to Personal Settings → Email tab.
- Confirm the “Track email messages” option is no longer visible.
- Emails will now follow the organization-level default setting without user override.
Repeat in other environments
- This must be done per environment (DEV, TEST, PROD).
- Always validate in sandbox before PROD.

Notes / Best Practice

Record the original value (false) before changing — in case you need to revert.
This change does not affect other OrgDBOrgSettings
This setting only hides the user option; it doesn’t change the org’s actual default for email tracking. If needed, verify the default at the org level (System Settings → Email).

After this, users will no longer be able to change the “Track Email Messages” preference — it will be locked to whatever your org’s global setting is.

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like♥.
Visit my blog Practical Power Apps LinkedIn