Integrating IdP (Identity Provider) / SSO (Single Sign On)
VisualVault supports Single Sign-On (SSO) for ERM v2.1, via SAML 2.0. This allows users to authenticate using their existing organizational credentials. Both Azure Active Directory (Microsoft Entra ID) and Okta are supported as identity providers. SSO is optional and is not required for all deployments.
Before You Begin
Obtain the following values from the customer’s IdP administrator before beginning configuration. These values are generated by the identity provider and cannot be determined from within VisualVault.
Field | Required | Description |
|---|---|---|
Identity Provider Name | Yes | A display name for the identity provider (e.g., Entra ID, Okta). |
Identity Provider Entity Id | Yes | The unique identifier for the identity provider. Obtained from the IdP administrator. |
Identity Provider Metadata URL | No | The federation metadata URL published by the IdP. Obtained from the IdP administrator. Used to auto-populate other fields via the Download button. |
Identity Provider Certificates | Yes | The signing certificate used to validate SAML assertions. Upload using the Certificates button. Obtained from the IdP administrator. |
Identity Provider Login URL | Yes | The SAML SSO endpoint URL where VisualVault sends authentication requests. Obtained from the IdP administrator. |
NameId Format | Yes | The SAML NameID format. Standard value: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress |
Navigating to Single Sign On Properties
Log in to VisualVault with your credentials.
Navigate to Control Panel > Enterprise Tools > Single Sign On.
Configuring Single Sign On Properties
Under Identity Provider, complete the required fields using the values obtained from the IdP administrator.
Under User Provisioning, confirm that Auto Create VisualVault Account if SAML User Does Not Have One is checked.
Under Group Security, confirm that Automatically Add Users to Groups is checked and that Group Claim Name is set to groups.
Click Save.
Integrating EDI Processing
ERM v2.1 supports Electronic Data Interchange (EDI) via sFTP (Secure File Transfer Protocol) as a data integration method. It acts as a secure bridge to move, exchange, and automate the transfer of files between different systems, applications, or organizations. When configured, changes to employee records in the customer organization can automatically trigger document import and metadata updates in the VisualVault Document Library and ERM v2.1 application.
Before You Begin
Obtain the following values from the customer before beginning configuration. These values are generated by the customer and cannot be determined from within VisualVault.
Field | Required | Description |
|---|---|---|
SFTP Host | Yes | The address of the remote server you’re connecting to, e.g.: sftp.example.com |
SFTP Port | Yes | The network port number used to establish the connection. Default is 22. |
SFTP Username | Yes | The login name used to access the SFTP server. |
SFTP Password | Yes | The credential associated with the username which authenticates and grants access to the server. |
Inbound Path | Yes | Directory where 835 files are received |
Archive Path | Yes | Directory where processed files are moved |
Navigating to Customer record (EDI Processing tab)
In the left navigation panel, click Customers.
On the Customers list screen, click the customer record to open it.
Navigate to the EDI Processing tab.
835 Inbound Settings
Configure automatic 835-remittance processing for this customer:
Enable inbound 835 processing for this customer.
Enable Live Processing — automatically process 835 files when received.
Set Poll Interval (Minutes) for how often to check for new 835 files (1-1440 minutes).
sFTP Configuration
Under SFTP Configuration, complete the required fields using the values obtained from the customer.
Click Save.