Enify opens and places applications and information on your available screens. Enify does this by saving a link to the information in the selected application. Enify does not save or override any security settings in your applications.
Using an Enify element to open and place an application in a layout on your screen does not in any way influence the applications own security.
This means, when using Enify, you cannot access information from an application if you don't already have access outside Enify. If you utilise Enify to open an application that requires that you sign in, the application will present you with its normal sign in page (unless you are already signed in with Single-Sign-On or a cached credentials).
Here are some examples using Enify to open applications:
User action | Enify response |
Starting an new application on your PC that requires sign-in. (No Single Sign On [SSO] or cached credentials available) | Enify will show the sign-in page for the application |
Starting an new application on your PC that requires sign-in but has cached credentials or using SSO. | Enify will usually show the the application without need to sign in |
Opening an application that is already running on you PC that normally requires sign in | Enify will show the the application without need to sign in |
Sharing an element or Board with another user with an application requiring sign in. They have no Single Sign On [SSO] or cached credentials available. | Enify will show the sign in page for the application - the other user will need to provide their sign in credentials. |
Sharing an element or a Board with information the other user don't have access to in the native application | Enify will show "you don't have access to this information" page and the user need to contact the person who sent the element or Board. |