Timeline for Restrict access to specific fields when using Salesforce Integration User Licence on Standard objects (like Contacts)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2023 at 3:41 | vote | accept | Nathan McQueen | ||
| Sep 5, 2023 at 7:36 | answer | added | Nathan McQueen | timeline score: 1 | |
| Aug 9, 2023 at 8:14 | comment | added | RubenDG | You cannot edit Object-Level permission, but you can change Field-Level ones. Moreover you could clone the profile. Anyway, as cropedy said, you cannot remove read/edit permission from required fields. | |
| Aug 9, 2023 at 3:46 | comment | added | cropredy | On standard objects, required fields are always visible (like Contact.LastName, Contact.Name) but I presume you are fetching more fields than those | |
| Aug 9, 2023 at 1:29 | comment | added | Nathan McQueen | @cropredy : using REST API (A query executed via Salesforce's Postman API set returns every field on the object) | |
| Aug 9, 2023 at 1:19 | comment | added | cropredy |
integration user has read access to ALL the fields on the object. - access via the REST API or via some Apex program that the integration user invokes?
|
|
| S Aug 9, 2023 at 1:09 | review | First questions | |||
| Aug 9, 2023 at 4:16 | |||||
| S Aug 9, 2023 at 1:09 | history | asked | Nathan McQueen | CC BY-SA 4.0 |
