Access to records is not same when impersonated.

Chindam Priyank
Tera Contributor

when one user (X) can see records in a table, but when another user (Y) impersonates X, the records are not visible and a security constraint error occurs, suggests that there may be specific access or permissions set for user X that are not being properly applied during the impersonation.

The table is not global but Security Incident Response application.

5 REPLIES 5

Ankur Bawiskar
Tera Patron
Tera Patron

@Chindam Priyank 

the access should be same even if someone impersonates or that user actually logs in.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hello ankur,

 

Thank for your response.

But in our case the user is able to view only few records let say 500 number of records when impersonated but the actual user is able to view all records i.e 1000 records.

Here is screenshot this is how user is able to view

ChindamPriyank_0-1705905596695.png

But when the same user is impersonated by other user this error we are getting.

ChindamPriyank_1-1705905703707.png

Kindly suggest

Siddhesh Gawade
Mega Sage
Mega Sage

Hello @Chindam Priyank ,

 

Even if we impersonate someone, the access should be the same. So please check existing ACLs on table, and check which ACLs are not allowing the access. You can use SNOW's Debug security option to find the ACLs.

 

Also check the if there any conditions are being checked using script in your ACLs. That may be the issue.

 

Kindly mark the answer ✔️Correct or Helpful ✔️If it addresses your concern.


Regards,

Siddhesh