Hi, is it a way to block console (F12) from editing by simple user, because have some "clever" users, who make changes in console, and changed some values in plumsail form, then make a screen and showed to overs users, with different data.
So would like to block this settings, from simple users.
Dear @ixxxl,
The issue here is that forms are not the security tool, they're built for user convenience and to reduce any input errors. You could try to limit console changes, but it would require tons of code and is not guaranteed to get the results.
Technically, tech-savvy users can use console or send HTTP requests directly to SharePoint servers avoiding the forms, and as long as they have appropriate permissions to input data, they could modify it in whatever way they see fit.
1 Like
Not sure if this will help or not. On our forms we block users from viewing source, inspecting elements, etc. by adding the following code:
// CONTROL SOURCE VIEWING
document.onkeydown = (event) => {
if (event.keyCode == 123) {
return false;
}
if (event.ctrlKey && event.shiftKey && event.key == 'I') {
return false;
}
if (event.ctrlKey && event.shiftKey && event.key == 'C') {
return false;
}
if (event.ctrlKey && event.shiftKey && event.key == 'J') {
return false;
}
if (event.ctrlKey && event.key == 'U') {
return false;
}
};
1 Like
Hello @vhancock ,
smart 
Then how do you access developer tools when you are "admin". Or do you have separate site where you develop the app and then export JSON from Plumsail?
Just curious.
Thanks
Stepan
We have multiple sites. One for development, one for unit testing (forms) , one for end-to-end testing (processes where data will be used by many forms/lists/Workflows) and then our master template that we use to create new sites from. We progress code through this sequence to QA and release. We use PowerShell to promote and deploy code. When code is finally in the master template we inject in the above referenced code into all forms.