Why are profiles created by customers to be used for non-Veeva related objects being touched during a Veeva patch or upgrade? Setup Audit Trail shows vadmin user stamped entries during the date and time of a Veeva CRM upgrade. The upgrade affects Veeva related objects on profiles which are:
- not used for Veeva related activity
- did not have any permissions setup for any Veeva objects.
The entries are stating that access was changed from Read and Write to No Access. Does this mean that at one point the Veeva upgrade gave those profiles Read and Write access to the objects?
The Veeva CRM upgrade process does not track whether a profile is not used for any Veeva related objects. It also does not track when there are entries in the Setup Audit Trail during an upgrade stamped with the vadmin user that state access was changed from Read and Write to No Access. It does not mean that access was assigned. When new fields are created by the Veeva upgrade process, the procedure is to set those fields to No Access for profiles which do not have access to the objects where the fields exist. This is why a user would see the access is changed from Read and Write to No Access.
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.