Data Security with Shared Assistants
Every request an Assistant makes is on behalf of the logged-in User, so a User sees only the Fields and rows they are allowed to see, and anything outside that appears not to exist. When you share an Assistant with people outside your Informer deployment, you can still keep its attached data secure with Informer's row- and Field-level security.
Domains and User Fields
The most secure way to share an Assistant with data is a Single Sign-On (SSO) Domain. An SSO Domain lets people log in with credentials from another application, creating a User in Informer on first login (like LDAP or Active Directory). Informer maps that User's Fields, so a Dataset Filter based on a User Field works automatically; if the User Field is not set, the Filter returns no results.
This method requires an SSO Domain, User Fields, and Dataset Filters. See:
Generated Token
A less secure option is a generated Token, which gives access to an Assistant without creating a User or logging in. You can restrict a Token by IP address at creation, so outside users can only reach the Assistant from certain networks. All queries using the Token run as the User who created it, so that User's row- and Field-level security applies to any attached Dataset.
Note: This method is not recommended for Assistants with sensitive attached data.