Action1

Overview

The Action1 integration connects your Action1 enterprise to Oneleet, syncing your Action1 users and API credentials as user account assets. This lets Oneleet monitor who has access to your Action1 console.

What does Oneleet monitor?

• Action1 users and API credentials (user accounts), including each user’s system role and whether they’re enabled
• Whether each user who signs in with an Action1 password has app-based multi-factor authentication enabled

Oneleet doesn’t check MFA for users who sign in through single sign-on (Entra ID, Google, Duo, or Okta), because your identity provider enforces their MFA. API credentials can’t sign in to the console, so the MFA check doesn’t apply to them.

Action1’s default email-code verification doesn’t count as app-based MFA. To pass the check, each user enables an authenticator app from the MFA entry in their avatar menu in the Action1 console.

Action1 only returns users’ assigned roles to API credentials with the Assign Roles or Manage Roles permission. Oneleet uses a read-only credential, so it shows each user’s system role (User, Admin, or Contributor) instead.

Setup

To set up the Action1 integration, navigate to Integrations > Add integration > Action1.

Oneleet connects with an Action1 API credential that has the read-only Enterprise Viewer role. Sign in to Action1 as an Enterprise Admin to create it.

1. In the Action1 console, under Configuration in the left sidebar, select Users & API Credentials.
2. Click New API Credentials, enter a name, assign the Enterprise Viewer role, and click Proceed.
3. Copy the Client ID and Client Secret. Action1 only shows the secret once.
4. In Oneleet, enter the Client ID and Client Secret.
5. Choose the Region that matches the address of your Action1 console, and click Connect:
   • na for app.action1.com
   • na-2 for app.na-2.action1.com
   • eu for app.eu.action1.com
   • uk for app.uk.action1.com
   • au for app.au.action1.com