Use field level security in a calculated field
Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2015, Dynamics CRM Online, Dynamics CRM 2016
To create a calculated field you must have the Write privilege on the Field Security Profile entity. If the calculated field uses secured fields in a calculation, you should consider securing the calculated field to prevent users from attempting to access data they don’t have permissions for. If you create a calculated field that uses secured fields in a calculation, the calculated field editor gives you a warning and suggests that you secure the field. More information:
Important
This feature was introduced in CRM Online 2015 Update and CRM 2015 (on-premises).
Interested in getting this feature? Find your Dynamics 365 administrator or support person.