About this article
- Templafy Glossary - in context
- Platform layer
- Core layer
- Feature layer
- Integrations layer
- User interface
- Templafy Glossary - alphabetically
- List of acronyms
Templafy Glossary - in context
Below you'll find all Templafy keywords explained in the context they are used in. Further down you'll find the same words in alphabetical order.
Platform Layer
The Admin Center is found at [tenantid].templafy.com/admin. It is only accessible by users with the Admin or SuperAdmin role. The Admin Center is where everything on a Tenant is configured.
Tenant
Templafy is a multi tenant solution. That means that we have many tenants running on the same servers. All customers that use Templafy have a tenant which can be seen as an isolated version of Templafy.
Since many non-tech people are not familiar with the term Tenant we try to avoid using it in the UI. Instead, we use the term Account in some places.
Tenant ID
Each Tenant has a unique Tenant ID which, among other things, is used for their subdomain such as [tenantid].templafy.com.
Account
An Account and a Tenant are basically the same. We have an Account information page, where it's possible to configure the contact information etc. about the Tenant.
If a user has access to multiple tenants he/she will see a Change account menu option in the WebApp.
Single Sign-on (SSO)
SSO is an industry standard that allows a user to log in to Templafy with their Windows Username/Password. In fact, the user will not even have to enter their credentials, it happens automatically. Most customers use SSO to login to Templafy, which also means that Templafy does not store username/password information.
Authentication Method
Templafy supports 4 different SSO protocols. OpenIdConnect (called Microsoft Entra ID in our UI), SAML2 (Ping Federate, OneLogin, OKTA etc.), WS-Federation, and Google Authentication.
Templafy also supports Email/password authentication, which is typically used until SSO is configured.
Active Directory (AD)
In a Windows environment, the Active Directory is a central server that contains a directory with all users, their details and how they are grouped in Active Directory Groups.
Identity Provider (IdP)/Security Token Service (STS)
An Identity Provider (IdP), sometimes called an Identity Service Provider or Identity Assertion Provider, is an online service or website that authenticates users on the Internet by means of security tokens, one of which is SAML2. In the WS-Federation Model, an Identity Provider is a Security Token Service (STS).
When setting up SSO a trust is made between Templafy and the customer's Identity Provider/Security Token Service - typically a Microsoft ADFS Server.
Claims
When a user logs in with SSO, the Identity Provider sends a list of Claims about the user. This is personal information like FirstName, LastName, PhoneNumber, Email etc. as well as a list of Active Directory Groups the user belongs to. Claims are updated every time the user logs in.
Claims Discriminator
Sometimes the same customer (usually an Enterprise) have multiple tenants using the same Identity Provider. The Claims Discriminator is the configuration option that enforces which enterprise user will get access to which tenant, e.g. only users from Spain have access to the Spanish tenant.
In Templafy, claims are used to control which features and assets a user has access to, and to create default values for user profiles.
User
An end-user is a person that has access to one or more tenants.
User group
A user group is a group of users. User groups can be used for all security configuration in Templafy.
User groups can be based on Active Directory claims.
User roles
We currently have 3 roles in Templafy.
User: Normal end user. Does not have access to the admin part.
Admin: Has access to the administration platform and can, for instance, upload templates. Some advanced settings are however not available.
Owner. Have access to everything the Admin has, and can also change user rights, configure SSO and more.
The plan is to introduce more fine grained access rights for admins
Furthermore, we have Partner users who have access to more features like Signup and "Feature toggling" and Templafy users who have access to SysOp.
User profiles
A user can have multiple user profiles. User profiles are used to create documents and email signatures with dynamic data.
In Templafy user profiles can be configured to pull default values from the claims sent from the Identity Provider when the user logs in.
User profile manager
In the user profile manager, it is possible to edit, create and delete user profiles. This is accessible from the "..." menu in Templafy, and from the User Profile Selector on the Create Document Form.
Shared user profile
From the User profile manager it is possible to subscribe to shared user profiles. When a user profile is subscribed to, it is shown with a small link icon.
Resources
(also known as Company Data)
When creating documents and email signatures, there are different kinds of resources:
- Data sources: These are tables with rows and columns that contain all kinds of data used by Templafy. Most tenants have a list of addresses, disclaimers etc.
- External Datasource (when a Data connector is used): These are tables with rows and columns that contain all kinds of data used by Templafy imported by the connector.
Modules
Templafy Modules are groupings of features aimed at solving specific challenges for customers.
Currently, the available modules are:
- Administration (always required, gives the customer access to the Admin Center)
- Library
- Dynamics
- Email Signature Manager
- Font distributor
- Offline
- Validator
- SlideProof
- ProductivityPlus
Currently, Templafy Implementation Partners can activate modules.
Templafy Desktop
Templafy Desktop is a program that is installed on Windows using the Templafy Desktop MSI package. It runs in the background on the users' machines and ensures that a user always has the latest VSTO Add-ins, tools from partners (e.g. Omnidocs). Templafy Desktop can also be used to distribute fonts, and is responsible for Offline synchronizing, to support creating dynamic documents offline, and more.
Templafy Desktop Client
Templafy Desktop is composed of a core software and a client software. When Templafy Desktop is installed, only a small bootstrap software is installed. Every time Templafy Desktop starts, it connects to our server and downloads the newest version of Templafy Desktop Client.
Templafy Desktop Client is the actual software responsible for downloading and installing Templafy Desktop Packages. This means we can add features and fix bugs affecting Templafy Desktop without having to distribute an updated Templafy Desktop MSI package, but by simply updating the Templafy Desktop Client. New versions of Templafy Desktop Client and its packages are configured in the Admin Center.
Templafy Desktop Packages
Templafy Desktop Packages are used to distribute files to users' PCs. A Templafy Desktop Package can contain the following:
- VSTO-Add-ins - (both Templafy's VSTO Add-ins, and add-ins from Partners, or customer's own Add-ins)
- Registry settings - Typically used to register Add-ins
-
Templates - A Templafy Desktop Package can include old-school office Templates (
.dotm,.potm,.xltm) - Fonts - Technically Fonts are also distributed using Templafy Desktop Packages
Offline Synchronization
Templafy Desktop is used to synchronize Templates and Asset libraries to the user's PC. Offline synchronization makes it possible to use Templafy to create documents and insert assets while offline. Tenants' resources like data sources, images and current user profiles are also included when synchronizing offline.
Network throttling
When Templafy Desktop updates Add-ins or runs offline synchronization, it uses network throttling. With this technique, we guarantee that users download their updates in a structured and scheduled way, in order to ensure our customers' network stability. For example, thousands of users connecting in one location are not allowed to all download at the same time and at maximum speed, we only allow a specific number of download slots at a time, at a speed of 10Mbps/sec.
Core Layer
Assets
In Templafy we currently have 9 different asset types. Templates are a special kind of asset.
Libraries
Assets are available through libraries. A library can only contain one type of asset.
Template Libraries
- Documents: A library which contains document templates for word processors. For instance, for Microsoft Word or Apple Pages. In code these are sometimes called WordProcessingDocument.
- Presentations: A library which contains templates for presentation templates. For instance, for Microsoft PowerPoint or Apple Keynote.
- Spreadsheets: Library that contains templates for spreadsheet templates. For instance, for Microsoft Excel or Apple Numbers.
Assets Libraries
- Slides: Library that contains slides. These slides can be inserted into presentations.
- Slide elements: Library that contains slides elements. These can be used to insert shapes, text etc. into a slide in a presentation.
- Text elements: Library that contains text elements. Text elements are pieces of text (which can also contain for instance tables and other rich elements) and can be inserted into both word processing documents and emails. Text Elements can also be used as building blocks in Built Templates.
- Images: Library that contains images and thereby can be inserted into a document or email.
- PDFs: Library that contains PDFs that can be downloaded.
- Links: Library that contains links to other websites.
Folders
Libraries can have Folders (called AssetFolders in code), and folders can have subfolders. User groups and User profiles filters, Offline synchronization are defined at the folder level.
Tags
Assets can be tagged with one or more Tag. This is used when searching for specific assets.
Filters
Folders can have filters. We have 2 kinds of filters:
- AD Filters / User Group filters (previously known as Security Filters) - These are based on User groups based on claims. These filters cannot be circumvented by the user.
- User Profile Filters (previously known as convenience filters) - These filters are based on what the user selects in their User Profiles, therefore they cannot be used to enforce security, but to show and hide relevant assets.
Templates
Templates are a special type of asset (Document, Presentation and Spreadsheet). When using Templafy to create a document, dynamic data can be inserted into the document from e.g. user profiles, data sources and resources (previously known as Company data).
In Microsoft Office a Template has a special file extension like .dotx, .dotm, .potx, .potm but Templates in Templafy are just normal documents such as, .docx, .pptx, .xlsx files. We do, however, support Excel Spreadsheets with macros .xlsm (still not templates .xltm).
Document
A document is created from a Template. This includes Word Documents, PowerPoint Presentations and Excel Spreadsheets.
Content
Content is created from Assets. If you upload content to Templafy, such as an image or a Slide, it becomes an asset. When a document is created or an asset is inserted into a document, it becomes content
When a document is created or an asset is inserted into a document, it becomes content. For example, in DCU the "C" stands for Content. Document Content Update.
Dynamics
Dynamics is a module in Templafy that allows the dynamic creation of documents and content.
Forms are currently used to configure the form presented to the user when creating a document, it connects user choices and user profile data with the dynamic configuration in the template.
Forms Designer will be part of Templafy Designer, but is still in the making.
The functionality to use a base template for multiple templates. The body of each template can be differentiated by specifying which Text Elements should go in the body of the base template.
Base template
Base templates are word processing templates used as the foundation of Built templates. They are not directly available to users. They typically hold a shared structure, layout, headers and footers that can be reused to create multiple built templates.
Document automation
Templafy Dynamics can facilitate what we refer to as Document Automation. It allows an interactive experience by following a workflow when creating, for example, a contract or a proposal. The user is asked questions, and each answer results in a specific text being inserted into the final document. We are currently creating the next version this feature. All the backend is in place but a nice UI in the Templafy Designer is in the making. An integrated part this is Built templates.
Templafy Designer
Templafy Designer (previously know as Template Designer) is the tool we use to create and configure dynamics templates and assets. Templafy Designer is activated from the "..." menu in the Templafy Task Pane inside Word, PowerPoint and Excel.
The Templafy Designer will also be used to configure Built Templates and Builder, and it will be the tool used to upload Templates and Assets to Templafy.
Document Content Updater (DCU)
The ability to update the dynamically inserted parts of a document. For instance, this could update a document based on another user profile, meaning that a different logo and company name would be inserted into the document. DCU is an update triggered by the user.
Validator
Functionality that automatically detects if some elements, dynamically inserted into a document, exist in a newer version of the template used to create the document. Validator is managed by admins and offers the user the possibility to review and apply available updates.
Currently, we only have Validator for PowerPoint Slides, which will detect and prompt the user to update outdated slides.
Templafy can run offline. Offline is a module sold separately and it only works for new Dynamics templates. DCU works when running offline, while Validator does not work (see also Offline Synchronization).
Feature Layer
Email Signature
Functionality to create and manage email signatures in Templafy. In Templafy an email signature has 4 parts:
Top campaign - The top campaign is a signature part that goes above the actual signature.
Body - The main part of the signature, typically contains information from the UserProfile like name, phone, address, website links etc.
Bottom campaign - The bottom campaign is a signature part that goes below the actual signature.
Disclaimer - The disclaimer is a signature part placed at the bottom of the signature.
Each Email signature part can be configured independently. It can target different User Groups and can be active for a specific date interval. For example, it is possible to have a Christmas Bottom campaign valid from December 1st to December 31st, for all users in the Sales Active Directory Group.
Email signature for Outlook
The functionality to insert an email signature managed in Templafy into an email composed in Outlook Desktop for Windows.
Email Signature Server for Office 365 (and Mobile Devices)
The functionality to insert an email signature managed in Templafy into an email sent from a mobile device or from the Office 365 web app. The signature is appended on the server after the email has been sent by the mail client (e.g. iPhone, Office 365). Requires Email Signature Server setup on either Templafy or customer's Azure environment and it's relaying on Kubernetes and Docker containers.
Docker
Docker is not a Templafy technology. it allows to host Email Signature Server for Office 365 to offer a signature for different devices and from a centralized way.
Kubernetes
Kubernetes is not a Templafy technology. it allows to orchestrate and manage the Docker containers for providing a sustainable and a scalable email signature server solution.
Font distributor
It allows for updated fonts to be distributed to end users without involving Administrators. This feature requires Templafy Desktop.
Check & ProductivityPlus
ProductivityPlus is a PowerPoint on-prem Add-in productivity tool. With this it is possible to produce, good looking, complex presentations - quickly!
Check Is an on-prem add-in for PowerPoint that can check presentations for correct use of fonts and colors, spelling, alignment of shapes and much more.
Integration Layer
External Libraries/DAM integrations
DAM (Digital Asset Management) integrations are integrations into external image banks. Their assets are shown in Templafy and can be inserted into documents and emails.
Public API
Templafy has a Public API that customers and partners can use to upload, update, delete and query images. We may eventually add support for handling other kinds of assets, and also to create/delete users etc.
Custom DAM integration
If a customer has a DAM system not supported by Templafy, we can either implement it as a first-DAM system, or the customer (or typically an Implementation Partner) can make the DAM integration without needing to involve Templafy by using the Generic DAM API.
Document Management Systems (DMS)
A DMS system is a system for managing documents, such as documents produced by Templafy. Typically the user starts on a case or client in the DMS system and clicks "Create document", then Word or PowerPoint opens and shows the Create Document form. Typically when the user saves, it's saved directly back to the DMS.
User Interface
VSTO Add-ins
Add-ins for on-premise Office for Windows.
Please note that Add-ins are spelled with a dash. Not "AddIns" or "Addins" but Add-ins.
Web Add-ins
Add-ins for Office 365. This means Add-ins that can be installed in Office Online, Office on-premise for Windows, and Office on-premise for Mac.
WebApp
The user interface found at tenant.templafy.com or from within the Templafy Add-ins.
Asset Explorer
The explorer that is used to navigate through the assets.
The library selector is located above the asset explorer and makes it possible to navigate between the different libraries and external libraries in Templafy.
Templafy's Add-ins are, in most cases, located inside a task pane in Office. This area in Office is referred to as a task pane.
Templafy Glossary - Alphabetical
| .msi Package |
A package that contains files for distribution. Usually the .msi package in our context is the .msi package for the Templafy Host which installs Templafy Desktop. |
| Account |
An Account and a Tenant are basically the same. We have an Account information page, where it's possible to configure the contact information etc. about the Tenant. |
| Active Directory (AD) | A central server that contains a directory with all users, their details and how they are grouped in Active Directory Groups. |
| Active Directory Groups | A group of users in a client's active directory. In Templafy, these groups can be used directly in filters. |
| ADFS Server | Active Directory Federation Services Server. Used by clients to facilitate SSO via SAML2. |
| Admin | A Templafy admin has access to the administration interface and can, for example, upload and organize templates. However, some advanced settings are not available. |
| Admin Center | The admin interface to Templafy. |
| Asset Explorer | The explorer that is used to navigate assets. |
| Assets | In Templafy we currently have 9 different Asset types. Templates are a special kind of Assets. |
| Assets Libraries |
Slides: Library that contains slides. These slides can be inserted into presentations. Images: Library that contains images which can be inserted into a document or email. Links: Library that contains links to other websites. Only available from the web application in a browser. PDFs: Library that contains PDFs that can be downloaded. Only available from the web application in a browser. |
| Authentication Method | Templafy supports 4 different SSO protocols. OpenIdConnect, SAML2 (Ping Federate, OneLogin, OKTA etc.), WS-Federation, and Google Authentication. Templafy also supports Email/password authentication, which is typically used until SSO is configured. |
| Azure Tenant ID | A globally unique identifier(GUID) that is different than your organization name or domain. This will be used for setting up SSO with Microsoft Entra ID. Find it using the following guide: https://docs.microsoft.com/en-us/onedrive/find-your-office-365-tenant-id |
| Base template |
Base templates are used as the foundation of Built templates. They typically hold a shared structure, layout, headers and footers that can be reused to create multiple built templates. Built templates are currently only available for Word. Built templates for PowerPoint are on our roadmap. |
| Blob Storage | A feature in Microsoft Azure that lets developers store unstructured data in Microsoft's cloud platform. Blobs are grouped into "containers" that are tied to user accounts. We use blob storage to store email signatures on the client's servers for example. |
| Built template | The functionality to use a base template for multiple templates. The body of each template can be differentiated by specifying which Text Elements should go in the body of the base template. |
| Citrix VDA | Virtual Desktop Application. A virtual application that is run on a different server environment. Templafy doesn't work here. |
| Citrix VDI | Virtual Desktop Instance. A virtual machine with an image. |
| Claims |
Claims are simply statements (for example, name, identity, group), made about users, that are used primarily for authorizing access to claims-based applications located anywhere on the Internet. Each statement corresponds to a value that is stored in the claim. Claim:Value. Templafy uses claim to determine which users have access to content etc. |
| Claims Discriminator | Sometimes the same customer (usually an enterprise) have multiple tenants using the same Identity Provider. The Claims Discriminator is the configuration option that enforces which enterprise user will get access to which tenant, e.g. only users from Spain have access to the Spanish tenant. |
| Connector |
These are a collection of instructions that customize the way your email flows to and from your Office 365 organization. They can enable mail flow between Office 365 and any email server that you have in an on-premises server. They can apply security restrictions or controls. Most Office 365 organizations don't need connectors for regular mail flow. |
| Content | In Templafy, templates and images uploaded are not considered Content but Assets. In Templafy Content is whatever is in a template or a document. For example, body text, images, disclaimers, contact information etc. Templafy features DCU and Validator can update and validate content. |
| Content Controls | Individual controls that you can add/customize for use in templates, forms and documents. They are placeholders to be inserted with data specified elsewhere. In PowerPoint, we use Shapes to insert relevant data. |
| Cookie | Cookies are used to store data on a client's computer. There are different types including session and persistent cookies. Session cookies are non-persistent and only exist in temporary memory. Persistent cookies expire at a certain date or time. |
| Core Layer | |
| Current User Context | Deployment option for installing the .msi so that only the appropriate user is attributed the Templafy Desktop client |
| Custom DAM integration | If a customer has a DAM system not supported by Templafy, we can either implement it as a first-class DAM system, or the customer (or typically a Partner) can make the DAM integration without involving Templafy. SkabelonDesign have made a few of these. |
| DAM | Digital Asset Management system. Services that stores digital assets such as images, logos, iconography etc. Bynder, BrandWorkz, Frontify are all examples of DAM systems. We integrate DAM systems into Templafy. |
| Delegated Authorization |
Giving authorization to a specific resource of a user. A more fine grained approach than federated authorization. For example giving an app access to a user’s calendar. |
| Docker |
A tool designed to make it easier to create, deploy, and run applications by using containers. Containers allow a developer to package up an application with libraries and other dependencies, and ship it all out as one package. |
| Docker Image |
A file comprised of multiple layers used to execute code in a Docker container. An image is essentially built from the instructions for a complete and executable version of an application, which relies on the host OS kernel. |
| Document | A document is created from a Template. Technically in Templafy this includes Word Documents, PowerPoint Presentations and Excel Spreadsheets. |
| Document Content Updater (DCU) | The ability to update the dynamically inserted parts of a document. For instance, this could update a document based on another user profile, meaning that a different logo and company name would be inserted into the document. DCU is an update triggered by the user. |
| Domain Hint | Primary email domain. This is used in authentication method settings for which domains need to be approved to login. |
| Document Management Systems (DMS) | A DMS system is a system for managing documents, such as documents produced by Templafy. Typically the user starts on a case or client in the DMS system and clicks "Create document", then Word or PowerPoint opens and shows the Create Document form. Typically when the user saves, it's saved directly back to the DMS. |
| Document Properties |
Metadata on a document that can be defined by a user, in addition to default properties. Standard properties: Title, author, subject etc Automatically updated properties: File size, last updated etc. Custom properties:Defined and inserted by the user Document library properties: Associated with documents in a document library on a website or public folder. Document libraries have preset rules on their property values and users are prompted to include those properties on the new document. |
| Dynamics |
Dynamics is a module in Templafy that allows the dynamic creation of documents and content. In the first version we called the functionalities plug-ins, and in the new version we call them dynamics. We first called these new dynamics transformations and transformation steps, but these terms are no longer being used. |
| Email Signature | Functionality to create and manage email signatures in Templafy. In Templafy, an email signature has 4 parts:
Top campaign - Top campaign is a signature part that goes above the actual signature
|
| Email Signature for Outlook |
The functionality to insert an email signature managed in Templafy into an email composed in Outlook Desktop for Windows. |
|
Email Signature Server for Microsoft 365 |
The functionality to insert an email signature managed in Templafy into an email sent from a mobile device or from the Office 365 web app. The signature is appended on the server after the email has been sent by the mail client (e.g. iPhone, Office 365). Requires Email Signature Server installation on Microsoft Azure Kubernetes environment. |
|
entityID |
Azure field that IT needs to fill in as https://app.templafy.com/AuthServices. Also a property in the client metadata that Templafy needs to extract and put into the Authentication method configuration. |
|
Exchange Admin Center |
Microsoft Azure module where IT can edit mail rules, connectors etc. |
| External Libraries/DAM integreations | DAM (Digital Asset Management) integrations are integrations into external Image banks. Their assets are shown in Templafy and can be inserted into documents, presentations and emails. Supported DAM integrations |
| Features Layer | |
| Federated Authentication | Giving access to multiple IT systems using one identity from an identity provider. When we refer to SSO then we're essentially referring to setting up federated authentication of Templafy. |
| Filters | Folders can have filters. We have 2 kinds of filters: User Group Filters (previously known as Security Filters). These are based on User groups based on claims. These filters cannot be circumvented by the user. User Profile Filters (previously known as convenience filters). These filters are based on what the user selects in their User Profiles, therefore they cannot be used to enforce security, but to show and hide relevant assets. |
| Folders | Libraries can have Folders (called AssetFolders in code), and folders can have subfolders. User groups and User profiles filters, Offline synchronization are defined at the folder level. |
| Font Distribution | This module is sold separately. It allows for updated fonts to be distributed to end users without involving Administrators. This feature requires Templafy Desktop. |
| Golden Image | Golden images(golden master, master image) are the base OS configurations from which all virtual machines in a VDI environement are built. These images serve as the foundation for the overall user experience. |
| Group Policy Object (GPO) | Provides centralized management and configuration of operating systems, applications, and users' settings in an Active Directory environment. |
| Identity Provider (IdP) | An Identity Provider (IdP), sometimes called an Identity Service Provider or Identity Assertion Provider, is an online service or website that authenticates users on the Internet by means of security tokens, one of which is SAML2. In the WS-Federation Model an Identity Provider is a Security Token Service (STS). When setting up SSO a trust is made between Templafy and the customer's Identity Provider/Security Token Service - typically a Microsoft ADFS Server. |
| Just-in-time (JIT) Provisioning |
The end user identity is provisioned(created or updated) at the service provider the first time the end user tries to gain access to the service. No prior identity provisioning activity between the identity provider and service provider is necessary. In Templafy's case that means users are created the first time they attempt to access the Templafy platform. The user attributes are passed by the identity provider and the user is created. |
| JSON Web Token (JWT) |
JSON Web Token's are used for authenticating with Templafy. Login credentials are provided to the authentication provider, the authentication returns a signed JWT. The JWT is then used as a means of access to Templafy. There are two JWT used for Templafy. One for Templafy Desktop and one used for Templafy in Office. The signed tokens are valid for 24 hours. The tokens are stored in the registry and the encryption key is stored in Windows Credential Manager. |
| Kubernetes |
An open-source system for automating deployment, scaling, and management of containerized applications. We use Kubernetes for deploying our email signature server. |
| Libraries | Assets are available through libraries. A library can only contain one type of asset. |
| Library Selector | The library selector is located above the asset explorer and makes it possible to navigate between the different libraries and external libraries in Templafy. |
| Local Machine Context | Deployment option for installing the .msi so that every user on a given machine with have the desktop client installed. This is as opposed to Local User Context. |
| Local User Context | Deployment option for installing the .msi so that only a certain user has the desktop client installed. |
| Manifest File | A file containing metadata for a group of accompanying files that are part of a set or coherent unit. Essentially a file that contains data about version number, author etc. Templafy uses this to install web add-ins from the Microsoft store. |
| Modules |
Templafy Modules are groupings of features aimed at solving specific challenges for customers. Currently, the available modules are:
Currently, Templafy Implementation Partners can activate modules. |
| Multi-tenant Solution | A single instance of software and its supporting infrastructure serves multiple customers. Each customer shares the software application also shares a single database. Each tenant's data is isolated and remains invisible to other tenants. |
| Network Throttling | When Templafy Desktop updates Add-ins or runs offline synchronization, it uses network throttling. With this technique we guarantee that users download their updates in a structured and scheduled way in order to ensure our customers' network stability. For example, thousands of users connecting in one location are not allowed to all download at the same time and at maximum speed, we only allow a specific number of download slots at a time, at a speed of 10Mbps/sec. |
| OAuth 2.0 |
OAuth 2.0 is a set of defined process flows for delegated authorization. This means that it’s a set of processes for giving access to certain resources within apps. For example if you want to access to the calendar of a Google user. You can give delegated authorization to that resource. |
| Offline support | Templafy can run offline. Offline is a module sold separately and it only works for new Dynamics templates. DCU works when running offline, while Validator does not work (see also Offline Synchronization). |
| Offline Synchronization | Templafy Desktop is used to synchronize Templates and Asset libraries to the user's PC. This makes it possible to use Templafy to create documents and insert assets while offline. Tenants' resources like data sources, images and current user profiles are also included when synchronizing offline. |
| Okta | An enterprise-grade identity management service, built for the cloud, but compatible with many on-premises applications. Templafy can integrate with Okta as an SSO provider. |
| On-Premises | Software that is installed and run on computers on the premises of the person or organization, i.e. not stored in the cloud. |
| OpenID Connect | OpenID Connect is the few additional steps added over OAuth 2.0 to extend OAuth 2.0 flr federated authentication. The id-token is the added piece in OpenID Connect that allows the OAuth 2.0 flow to be used for federated authentication. The id-token is typically returned in JWT format. |
| Public API | We have an API that customers and partners can use to upload, update, delete and query images. We might eventually add support for handling other kinds of assets, and also to create/delete users etc. |
|
Resources (previously known as Company Data) |
When creating documents and email signatures, there are different kinds of resources:
|
| SAML2 | SAML is another popular federated authentication flow that relies on an exchange of messages for authentication in XML SAML format instead of JWT format. It's the older cousin of OpenID Connect. |
| SCCM | Microsoft System Center Configuration Manager. This is a tool for IT teams to deploy software to machines organization-wide. SCCM is often used to install Templafy Desktop to all machines. |
| SCIM | System for Cross-domain Identity Management is a standard for the exchange of user identity information between identity domains. For example, if a user is deleted in Active Directory then they'll also automatically be deleted in Templafy. |
| Security Token Service (STS) | A service responsible for issuing, validating, renewing and cancelling security tokens. |
| Shared user profile | From the User profile manager it is possible to subscribe to shared user profiles. When a user profile is subscribed to, it is shown with a small link icon. |
| Signing Certificate | Encoded certificate contained within the client metadata that needs to be extracted and inserted into the client's Authentication configuration. |
| SMTP | Simple Mail Transfer Protocol, the accepted internet standard for how emails are sent from one email server to another. SMTP is conceptually similar to HTTP, just for email. |
| Single Sign-on (SSO) | SSO is an industry standard, that allows a user to log in with their Windows Username/Password to Templafy. In fact, the user will not even have to enter their credentials, it happens automatically. Most customers use SSO to login to Templafy, which also means that Templafy does not store username/password information. |
| Slides | |
| SlideProof | It is an on-prem add-in for PowerPoint that can check presentations for correct use of fonts, colors, spelling, alignment of shapes and much more. |
| Slide elements | A slide element is one or more shapes on a slide, that can be inserted from the library onto other slides in the active presentation. |
| SlideProof | SlideProof is a PowerPoint Add-in for productivity. |
| SSL | Secure Socket Layer, the precursor to TLS, cryptographic protocol |
| SuperAdmin | Have access to everything the Admin has, and can also change user rights, configure SSO and more. |
| Tags | Assets can be tagged with one or more Tag. This is used when searching. |
| Task pane | Templafy's Add-ins are, in most cases, located inside a task pane in Office. This area in Office is referred to as a task pane. |
| Templafy Designer | Templafy Designer (previously know as Template Designer) is the tool we use to create and configure dynamics templates and assets. Templafy Designer is accessible for SuperAdmins from the Templafy Task pane inside Word, PowerPoint and Excel. Going forward, the Templafy Designer will also be used to configure Built Templates and Builder, and it will be the tool used to upload Templates and Assets to Templafy. |
| Templafy Desktop |
Templafy Desktop is a program that is installed on Windows using the Templafy Desktop MSI package. It runs in the background on the users' machines and ensures that a user always has the latest VSTO Add-ins, tools from partners (e.g. SkabelonDesign) and "old-school" company templates. Templafy Desktop can also be used to distribute fonts, and is responsible for Offline synchronizing, to support creating dynamic documents offline, and more. |
| Templafy Desktop Client |
Templafy Desktop is composed of a core software and a client software. When Templafy Desktop is installed, only a small bootstrap software is installed. Every time Templafy Desktop starts, it connects to our server and downloads the newest version of Templafy Desktop Client. Templafy Desktop Client is the actual software responsible for downloading and installing Templafy Desktop Packages. This means we can add features and fix bugs affecting Templafy Desktop without having to distribute an updated Templafy Desktop MSI package, but by simply updating the Templafy Desktop Client. New versions of Templafy Desktop Client and its packages are configured in the Admin Center. |
| Templafy Desktop Packages |
Templafy Desktop Packages are used to distribute files to users' PCs. A Templafy Desktop Package can contain the following:
|
| Template Libraries |
Documents: A library which contains document templates for word processors. For instance, for Microsoft Word or Apple Pages. In code these are sometimes called WordProcessingDocument. Presentations: A library which contains templates for presentation templates. For instance, for Microsoft PowerPoint or Apple Keynote. Spreadsheets: Library that contains templates for spreadsheet templates. For instance, for Microsoft Excel or Apple Numbers. |
| Templates |
Templates are a special type of asset (Document, Presentation and Spreadsheet). When using Templafy to create a document, dynamic data can be inserted into the document from e.g. user profiles, data sources and resources (previously known as Company data).
|
| Tenant ID | Each Tenant has a unique Tenant ID which, among other things, are used for their subdomain such as [tenantid].templafy.com. |
| Tenant | Templafy is a multi tenant solution. That means that we have many tenants running on the same servers. All customers that use Templafy have a tenant which can be seen as an isolated version of Templafy. |
| Terraform | Infrastructure-as-code software. Use it to define a data center infrastructure in a very high-level configuration language(HCL). Basically creates infrastructure following a config file. Templafy uses Terraform for configuring the infrastructure for the Kubernetes/Docker setup. |
| TLS | Transport Layer Security. A cryptographic protocol. HTTP+TLS=HTTPS |
| User | An end-user is a person that has access to one or more tenants. A user does not have access to the admin part. |
| User group | A user group is a group of users. User groups can be used to toggle (activate and deactivate) specific features to only some users. Going forward, Templafy user groups will also be used for filtering of templates and assets. User groups can be based on Active Directory claims. |
| User profile manager | In the user profile manager it is possible to edit, create and delete user profiles. This is accessible from the "..." menu in Templafy, and from the User Profile Selector on the Create Document Form. |
| User profiles |
A user can have multiple user profiles. User profiles are used to create documents and email signatures with dynamic data. In Templafy user profiles can be configured to pull default values from the claims sent from the Identity Provider when the user logs in. |
| Validator |
Functionality that automatically detects if some elements, dynamically inserted into a document, exist in a newer version of the template used to create the document. Validator is managed by admins and offers the user the possibility to review and apply the available updates. |
| VSTO Add-ins | Add-ins for on-premise Office for Windows. |
| Web Add-ins | Add-ins for Office 365. This means Add-ins that can be installed in Office Online, Office on-premise for Windows, Office on-premise for Mac and Office on-premise for iPad. |
| WebApp | The user interface found at tenant.templafy.com or from within the Templafy Add-ins. |
| WS-Federation | Ws Federation is one of the identity protocols and is rarely seen at Templafy. The setup with ADFS is easy and that has often been the reason for using it. |
List of acronyms
In Templafy we try to not use too many acronyms.
That said, the list below includes the acronyms we have not been able to avoid. This is a full list of acronyms we use in our business.
Microsoft Entra ID - Microsoft Active Directory
ADFS - Active Directory Federation Services
DAM - Digital Asset Management
DCU - Document Content Updater
DMS - Document Management Systems
EAC - Exchange Admin Center
GPO - Group Policy Object
JIT - Just-in-time provisioning
JWT - JSON Web Token
PHS - Password Hash Synchronization
PII - Personally Identifiable Information
SAML - Security Assertion Markup Language
SCCM - Microsoft System Center Configuration Manager
SCIM - System for Cross-domain Identity Management
SPA - Single Page App
SSL - Secure Sockets Layer
SSO - Single Sign On
TLS - Transport Layer Security
UI - User Interface
UX - User Experience
VDI - Virtual Desktop Instance
VDA - Virtual Desktop Application
Related articles
Comments
Please sign in to leave a comment.