SOLUTIONBRIEF
Powerful, easy-to-configure, reliable license choice for your system integrations with Arena.
KEY BENEFITS |
WHAT ARENA MACHINE USER LICENSE DOES |
|
 |
Easy to manage | Machine users are licensed separately from employee users and used one per integration. License name is tied to function, not person. |
|
Easy to configure | Each machine user includes one events engine. An events engine is an outbound-event integration with a queue to capture Arena activity. It is no-code and includes advanced filtering and other trigger capabilities. |
|
No password expiration | Machine users are exempt from password expiration. |
|
Granular access control | Machine users use access policies for granular access/permission control. |
|
Visibility | An employee user can receive notifications on behalf of machine users. |
|
Handles long-running integration sessions | Machine user sessions can be configured to handle long-running integration session conflicts. For example, a machine user session can prevent unintentional termination or interference of long-running integration sessions. |
|
Supports corporate password policies | Account administrators can configure authentication via a secure web token or a username and password, even for Cloud SSO users. The Arena administrator can change the machine user password. |
If you need an outbound or bidirectional integration, a machine user is the perfect fit. A machine user can easily and quickly be provisioned and configured to simplify your integration development process.
The account administrator can configure the events engine integration in minutes using advanced filtering and triggers. Filtering can easily be updated over time to suit changing business needs.
Configure the events engine to capture and queue Arena activity based on advanced filtering and triggers. Configure the machine user using access policies to access only the data required for the integration.
Track how your system consumes API calls daily. Since account administrators can review API activity by user and session duration, they can easily differentiate between machine and employee user activity. This helps the account administrator understand where the API call loads originate to better understand the API needs of their organization and users.
If you need an outbound or bidirectional integration, a machine user is the perfect fit. A machine user can easily and quickly be provisioned and configured to simplify your integration development process.
