Integrations

Another new field has become available on the Person form. It is the Employee ID field. This field can be found in the ‘Financial Details’ section of the Person form. When the [...]

To provide an alternative to using the Primary email field values to uniquely identify people who need to be granted access to 4me after an organization’s identity provider has sent a SAML [...]

Most organizations now use an identity provider like Microsoft Azure Active Directory, Okta, OneLogin or Google Cloud Identity. These services have started to allow their users to upload an image [...]

Since the introduction of the Account Designer role, there is no longer a practical reason to limit the access rights that the Account Administrator role provides. This role is now able to create [...]

A whole new set of operators have become available that makes it possible to create Automation Rules that manipulate strings of characters. The new operators are: size, length — returns the [...]

Developers who are most comfortable with C# or Visual Basic will be excited to hear that a 4me software development kit (SDK) has become available for the Microsoft .Net Framework. Like the SDK [...]

Another standard 4me integration has become available. It is the 4me SCCM Connector. This connector makes it possible for organizations to integrate their Microsoft System Center Configuration [...]

It is now possible to move a person record from a support domain account to its directory account. When a new person record is registered in a directory account, 4me checks all the support [...]

To protect organizations against malicious use of the Mail API, the maximum number of email messages that gets processed for any person over a 4-hour period is limited. The limit depends on the [...]

A minor feature has been added to the REST API for changes. This API now allows the manager of the change to be set when a new change is created. In the past, the API user would always become the [...]