This article details the most frequently asked questions from customer IT.
Platform
- Integration of Templafy in MS Office
- Achieved by installing Templafy Desktop or by centrally deploying Web Add-ins.
- 4 - 16 hours depending on internal processes.
- Set up Single Sign-On
- Most commonly used are SAML2 and OpenID Connect.
- 1- 8 hours depending on internal processes.
-
Deployment of MSI / Web Add-in
- Different Add-ins, permissions, templates, etc. can be deployed to specific user groups / regions.
- Single Sign-On
- Templafy supports multiple authentication methods for same tenant. This means users from different Active Directories can sign in using different methods.
- Templafy Web Application - Runs in the cloud and is updated server side. The web application is always running the latest version.
- VSTO Add-ins - Updates are handled by the Templafy Desktop client. There is no need for IT involvement to roll out any updates. Client IT can get access to updates prior to releases to test locally if needed.
- Web Add-ins - Automatically updated server side.
Integrations
Security
NoteTemplafy is a secure multi-tenant Saas solution running in the Microsoft Azure cloud offering various benefits with security and automatic load scaling. |
-
Company data is stored on Microsoft Azure. Templafy is clustered into regions to provide enhanced availability. Customers can select a region for data storage. Once selected the data storage cannot be moved.
-
Templafy leverages sub-processors to support the provision of Templafy services.
- No. Templafy is typically used for standard, generic content such as contract templates and brand-compliant slide decks that users generate and further build on.
- User data: Minimum user data is user email which is used as unique identifier. Typically name, department, contact info, and other relevant elements as configured by customer admins/owners.
- Company info: office addresses, disclaimer texts, logos
-
Digital assets uploaded to Templafy: templates, images, slides
-
System information: IP address and usage behavior as users navigate through the Templafy services.
- Storage:
- Data is stored in SQL Azure.
-
Digital assets are stored in a unique Azure Blob storage for each customer.
-
Both types of storage are considered highly secure and reliable (All data is saved on 3 disks and has geo redundancy to other data center within geographical region).
- Encryption:
-
Templafy supports TLS1.2.
-
Data at rest is encrypted using AES 256-bit encryption is enabled by default throughout all Azure services in use for the Templafy Services.
-
TLS1.2 is used to communicate between all the Azure services in use for the Templafy Services.
-
File and disk level encryption on blob storages.
-
Disk level encryption on SQL database.
-
MD5 is not a FIPS-compliant cryptography algorithm, thus if FIPS-compliance is enforced, MD5 will not generate a checksum for data integrity.
Comments
Article is closed for comments.