--- schema_version: "1" id: 94417b6b0453b2c13769dc24693e137544d90cb53a0a8349dc156b1e30bd98de title: Insufficient Access Event Type collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_eventlogfile_insufficientaccess.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_insufficientaccess.htm source_site: developer.salesforce.com content_type: documentation content_hash: f28e1fc9b7d74dc6c91ed1a2aa0a03ae95682667a7725448ea9449ebec33ff92 description: Insufficient Access events contain details about errors relating to insufficient account, case, contact, and opportunity record access, so that you can troubleshoot and resolve access issues for your users. --- # Insufficient Access Event Type Insufficient Access events contain details about errors relating to insufficient account, case, contact, and opportunity record access, so that you can troubleshoot and resolve access issues for your users. ![Note](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png) #### Note The Insufficient Access event type is disabled by default. You can enable this event type for a period of 24 hours by contacting Salesforce Customer Support. These insufficient access error scenarios are logged: - The user can’t share a case, contact, or opportunity because the user doesn’t have permission to share the parent account or the recipient of the share doesn’t currently have read access to the parent account. - The user can’t change ownership of a case, contact, or opportunity because the user doesn’t have permission to share the parent account or the new owner doesn’t currently have read access to the parent account. - The user can’t change the parent account of a case, contact, or opportunity because the user doesn’t have permission to share the new parent account or the owner of the case, contact, or opportunity doesn’t have read access to the new parent account. Insufficient access errors resulting from bulk operations involving two or more records aren’t logged. For details about event monitoring, see the [Trailhead Event Monitoring module](https://trailhead.salesforce.com/en/modules/event_monitoring/units/event_monitoring_intro "HTML (New Window)") or [REST API Developer’s Guide](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_rest.meta/api_rest/using_resources_event_log_files.htm "HTML (New Window)"). For more information on interpreting Insufficient Access events, see this [knowledge article](https://help.salesforce.com/s/articleView?id=000396437&type=1&language=en_US "HTML (New Window)"). ## Fields | Field | Details | | --- | --- | | ACCESS\_ERROR | Type String Description The type of insufficient access error that the user received. Valid values are: - DATA\_NOT\_AVAILABLE—The record is no longer accessible. For example, a record was deleted and moved to the Recycle Bin. - INVALID\_TYPE—The record type doesn’t exist. - NO\_ACCESS—The user doesn’t have the required access level to complete the attempted action on the record. Example NO\_ACCESS | | ACTUAL\_LOGGED\_IN\_USER\_ID | Type Id Description The 15-character ID of the user who initiated the action that caused the insufficient access error. For example, a user attempts to transfer ownership of a record to a teammate, but the operation fails because the teammate doesn’t have the required access. In this scenario, the ACTUAL\_LOGGED\_IN\_USER\_ID is the user who attempted to transfer access, and the USER\_ID is their teammate. Example 005XXXXXXXXXXXX | | ENTITY\_TYPE | Type String Description The object for which the user received the insufficient access error. Access errors for the account, case, contact, and opportunity objects are supported. Example Account | | ERROR\_DESCRIPTION | Type String Description Description of the insufficient access error that the user received. Example User 005XXXXXXXXXXXX doesn't have full access for the record 001XXXXXXXXXXXX. | | ERROR\_TIMESTAMP | Type String Description The time in GMT that the insufficient access error occurred. Example 20130715233322.670 | | EVENT\_TYPE | Type String Description The type of event. The value is always InsufficientAccess. | | ORGANIZATION\_ID | Type Id Description The 15-character ID of the organization. Example 00DXXXXXXXXXXXX | | RECORD\_ID | Type String Description The ID of the record that the user doesn’t have access to. Example 001XXXXXXXXXXXX | | REQUEST\_ID | Type String Description The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST\_ID. Example 3nWgxWbDKWWDIk0FKfF5DV | | REQUESTED\_ACCESS\_LEVEL | Type String Description The access level required by the user’s attempted action on the record. Valid values are: - DELETE - FULL - READ - TRANSFER - WRITE Example FULL | | TIMESTAMP | Type String Description The access time of Salesforce services in GMT. Example 20130715233322.670 | | TIMESTAMP\_DERIVED | Type DateTime Description The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). Example 2015-07-27T11:32:59.555Z | | USER\_ID | Type Id Description The 15-character ID of the user for whom the insufficient access error occurred, either when the user couldn’t access a record, the user couldn’t complete an operation, or the user was the intended recipient of a record transfer that failed because the user didn’t have the required access. Example 005XXXXXXXXXXXX | | USER\_ID\_DERIVED | Type Id Description The 18-character case-insensitive ID of the user for whom the insufficient access error occurred, either when the user couldn’t access a record or the user was the intended recipient of a record transfer that wasn’t completed. Example 005XXXXXXXXXXXXIA0 | #### See Also - [EventLogFile Supported Event Types](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_supportedeventtypes.htm "The EventType field in the EventLogFile object supports these events. Some common fields, such as CPU_TIME and RUN_TIME, can have null or zero values depending on how the events are generated for a given feature. Sometimes, three quotation marks appear around event data containing special characters in the CSV file. The third quotation mark is necessary for tools and applications to parse the field data at the correct field value boundary.") - [EventLogFile](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile.htm "Represents event log files generated by Event Monitoring. Use event log file data to analyze usage trends and user behavior in your Salesforce org. This object is available in API version 32.0 and later. The Interval and Sequence fields are available only in API version 37.0 and later.") - [_Knowledge Article_: Interpret Insufficient Access Event Logs](https://help.salesforce.com/s/articleView?id=000396437&type=1&language=en_US "Knowledge Article: Interpret Insufficient Access Event Logs - HTML (New Window)")