Integrations

The payload of a 4me webhook now contains an extra bit of data to help developers build more efficient integrations. This extra piece of information is the ID of the note that was created during [...]

The REST API for person records now offers an additional predefined filter. The following predefined filters were already available: /people/disabled — List all disabled people [...]

The System for Cross-domain Identity Management (SCIM) is a standard for automating the exchange of user identity information between identity domains, or IT systems. The specification for this [...]

The capabilities of the Automation Rules functionality have been extended again. This time the ability to use regular expressions has been added. In combination with the recent enhancement that [...]

A small adjustment has been made to the Import functionality for person records. This adjustment perfects the way 4me ensures that a new record does not get generated during an import for a [...]

All organizations that have an SPF record defined for support.itrp.com in the domain name system (DNS) zone for their internet domain should now add an SPF entry for _spf.4me.com. The SPF entry [...]

4me’s single sign-on (SSO) functionality has been extended further to provide even more flexibility. Enterprises could already integrate their 4me directory account with multiple identity [...]

People who work for an organization that has activated single-sign-on (SSO) in their 4me account have always been able to bypass SSO and use 4me’s standard login page instead. That can be useful, [...]

When an external server is down, all webhooks that tried, but failed, to reach this server are now remembered as ‘offending’ webhooks. This allows 4me to include the name and 4me [...]

Demo instances can now also be integrated with identity providers like Microsoft Azure Active Directory, Okta, OneLogin or Google Cloud Identity for automated provisioning. After accessing a 4me [...]