Introduction
This article is designed to help account owners and admins set up fynk quickly and efficiently. It provides all the essential information about account language, security and internal parties to ensure a smooth start.
Default account language
The default account language plays an important role in several areas of fynk. Here’s how it’s used:
It will be the preselected language for all newly created templates and documents.
(For imported documents, the language is detected automatically by AI.)All AI-generated summaries and abstracts, as well as most metadata extractions, will be provided in the account language.
If a document doesn’t have a defined language, the account language will be used as the fallback language for outgoing emails to external users.
Internal parties
In the My Parties section, you should list all internal entities relevant to your organization—such as company locations, legal subsidiaries, or departments. These entries can then:
Be preselected when creating new documents or templates
Be automatically recognized as internal during AI-driven document analysis
Important Note:
External parties—like suppliers, customers, or partners—should not be added here.
They are handled separately: fynk identifies and stores them individually per document, and will suggest them automatically during document creation.
Account Security
fynk offers a wide range of possibilities when it comes to account security. To secure your fynk account, the best way is to use either SSO via SAML2 integration or our native 2FA solution. Additionally, user provisioning via SCIM is available as well.
Single Sign On
Single Sign-On (SSO) using SAML2 allows users to access fynk through their company’s existing identity provider - such as Microsoft Entra ID (Azure AD), Google Workspace, or Okta - without needing to manage separate login credentials.
Benefits of integrating SSO with fynk:
Faster, seamless login experience for users
Stronger security by centralizing authentication and enforcing existing password and 2FA policies
Setting up SSO with your identity provider requires an admin of your IDP (Azure, Google, Okta etc.) as well as a user with admin or owner role in fynk. A dedicated documentation is available here.
SSO is only available with a Pro subscription. You can view your subscription here.
User Provisioning via SCIM
SCIM (System for Cross-domain Identity Management) is a standard protocol that enables automatic user provisioning and deprovisioning between your identity provider (like Azure AD, Okta, or Google Workspace) and fynk.
Benefits of integrating SCIM with fynk:
Automated user management – Users are created, updated, or removed in fynk based on changes in your identity provider
Consistency & accuracy – Ensures user roles and teams stay up-to-date
Security – Immediate deactivation of access when users leave the organization
Setting up SCIM with your identity provider requires an admin of your IDP (Azure, Google, Okta etc.) as well as a user with admin or owner role in fynk. A dedicated documentation is available here.
SSO is only available with a Pro subscription. You can view your subscription here.
Two Factor Authentication
Two-Factor Authentication (2FA) adds an extra layer of security to your fynk account by requiring not just a password, but also a second verification step via a time-based code generated by an authenticator app like Google Authenticator or Microsoft Authenticator.
Benefits of enabling native 2FA in fynk:
Stronger account protection against unauthorized access
No need for external identity providers - 2FA works out of the box in fynk
Simple and user-friendly setup for all users
Meets security best practices and supports internal compliance policies
2FA can be enabled individually by each user in via profile settings as well as account-wide via account settings.
Hint💡: SSO should NOT be used alongside with Two Factor authentication, as this can cause serious side effects potentially leading to inability of logging in.