Security constraints prevent access to requested page: why is it so even if I am elevated admin?

[chsai]

I just want to update choices for "alert_sensor" field.

 If I see the backend name of field; I could find that it is out of the box field.

But I could see that it's a text field when I check in the security incident form. But when I try to configure dictionary I could see that it's a reference field to "Security Incident Alert Sensor" table.

Also I am unable to open the same table to add choices to "Alert Sensor" field. Why is it so even if I am an admin and I have elevated rights too?

The error I got when I tried to open the table is:

"Security constraints prevent access to requested page".

Thanks in Advance,

Sai.

[SanjivMeher]

Can you check the ACL for that field? THat should give you some idea.

I tried searching that field, but couldn't find it in my instance. I am on madrid.

[Chris McDevitt]

Sai,

It look like that table/field do not have any ACL's setup. You will probably need to add a Table and then a field-level ACL to gain access to that field.

Go ahead and smash that helpful or Correct button!

[chsai]

Thanks for the update,

I tried all the ways but didn't found any solution.

It is not visible in Demo instance too. Could you please check by trying to open the same table in Demo?

Regards,

Sai

[Chris McDevitt · Accepted solution]

It looks like this table is used for Threat Intelligence Integrations. Unless you are developing a TI integration it is best to leave that table alone. 

With that said....

As noted above, once I add a Table and Field ACL to read/write I was granted access. Elevate your role to Security Admin, go to Tables and search for 'sn_si_alert_sensor' under Name. Scroll down to the Access Control Related list. Click on New and create your ACLs for that table.

Again, unless you're developing a new TI integration I would leave that table alone.