Technical setup scenarios

This article provides an overview of four typical technical scenarios to create the right setup to suit your organization's requirements.

Data and password encryption:

Data will be encrypted on both the client-side interface and the API. This means that any data sent back to the API will be encrypted before it's transmitted. To make sure only the API can read the data, a private/public key pair will be used for encryption.

This same method will also be applied to handle password values in the configuration. Only the API will be able to decrypt and access the password.

This means that after the password is entered it will not be saved in the PBIX file or other places. Only the new encrypted key is used for extended security.

For the self-hosted API option, customers can use their own private/public key pair for encryption.