This article compares the available methods for importing and synchronizing users and groups in SMARTFENSE. It helps you choose the right one based on the identity tools your organization already uses.
The configuration is available under Users and Groups > Import and Synchronization.
Comparison Table of Methods
| Method | Source | Periodic Synchronization | Recommended For |
|---|---|---|---|
| Manually from CSV file | CSV file (UTF-8) | No | One-time uploads or manual adjustments controlled by the administrator. |
| From CSV file on remote FTP | CSV file (UTF-8) on FTP server | Yes (1:00 AM local time) | Automating reading a file generated by other systems. |
| From Microsoft Entra ID | Microsoft Entra ID directory | Yes (1:00 AM local time) | Organizations using Microsoft Entra ID as the central identity source. |
| From Google | Google Workspace | Yes (1:00 AM local time) | Organizations whose primary directory is Google Workspace. |
| From LDAP directory | Corporate LDAP directory | Yes (1:00 AM local time) | On-premise LDAP directories other than Active Directory. |
| From API | External API | Yes (1:00 AM local time) | Custom integrations with internal systems of the client or partner. |
| From Powershell script | Microsoft Active Directory (AD) on-premise | No | Synchronization with on-premise AD via a script run on a machine with directory access. |
Details of Each Method
Manually from CSV file
Imports users and groups from a CSV file (UTF-8). Suitable for one-time uploads or manual adjustments controlled by the administrator.
From CSV file on remote FTP
Imports users and groups from a CSV file (UTF-8) accessible via FTP. Allows automating the reading of a file generated by other systems within the organization or partner.
From Microsoft Entra ID
Imports users and groups from a Microsoft Entra ID directory. This is the recommended option when the organization uses this directory as the central identity source.
From Google
Imports users and groups from Google Workspace. Allows aligning the instance with the users defined in the organization’s Google domain.
From LDAP directory
Allows importing and synchronizing users and groups directly from a corporate LDAP directory, keeping information automatically up to date.
From API
Imports users and groups via an API, enabling custom integrations with internal systems of the organization or partner. Ideal when a high level of automation and control from external applications is required.
From Powershell script
Allows importing users from Microsoft Active Directory (AD) on-premise into the SMARTFENSE platform. Through this action, it is possible to create new users and edit existing users, keeping the instance aligned with the local directory. The minimum PowerShell version required to run the process is version 7.
Periodic Synchronization
When a method supports periodic synchronization and the option is enabled, the import runs automatically every day at 1:00 AM (local time of your instance).
If your organization uses more than one directory (for example, Microsoft Entra ID and Google), define a single source to avoid conflicts.
💡 Best Practices
- Define a single import source (Microsoft Entra ID, Google, FTP, API, LDAP, or on-premise AD) to minimize conflicts in user management between systems.
- Test first with manual uploads from CSV files before enabling periodic synchronization, to validate the format and the correct creation or updating of users and groups.
- Regularly review import and synchronization logs to detect data errors (e.g., incomplete required fields or invalid formats) and correct them in the source system.
- If you are a partner managing multiple organizations, document which import method each instance uses and who the responsible administrator is in the source system.