Skip to navigation

About Access Management

Eon allows you to control who can access your account and resources, as well as what they can do once they’re in. You’ll manage this access by assigning roles to your users and API credentials. You can also set up action approvals, allowing you to require approval from others before specific high-impact actions run.

The access management articles cover all the different ways your users and custom code can authenticate in your Eon account and how you can manage their access. The explanation articles explain these concepts:

ArticleWhat’s covered
About Roles and PermissionsDiscusses Eon’s role-based access control model and data access controls. Describes how to manage custom roles.
About UsersDescribes how to manage users with basic login.
About SAML SSOExplains SAML SSO and SAML groups. Describes how to manage users with SAML SSO login.
About API CredentialsDiscusses how to create and manage API credentials, as well as how to use them to authenticate your custom code with the Eon API.
About Action ApprovalsExplains how to require approval before specific actions execute. Describes approval rules, action requests, and how action approvals work with roles and permissions.

While users, SAML SSO, and API credentials are themselves authentication methods, the actual permissions granted to each are managed through roles. It’s important to understand Eon’s role-based access control model to manage your account’s security.

Before getting into the details of each topic, let’s start with an overview of the different ways your account can be accessed.

Overview of authentication methods

Depending on who or what you need to grant access to, you can choose the appropriate authentication method. This table contrasts the different authentication methods available in Eon and when to use each one:

Authentication methodAvailable forDetails
Basic loginUsersAuthentication: Email and password
Managed in: Eon
More information: About users
SAML SSOUsersAuthentication: Third-party identity provider
Managed in: Third-party identity provider
More information: About SAML SSO
API credentialsMachine accessAuthentication: Client ID and client secret
Managed in: Eon
More information: About API credentials

User management: Basic login vs. SAML SSO

If your account doesn’t have SAML SSO enabled, all users must use basic login. When using basic login, each user must be manually invited to the account and assigned a role. If you need to revoke user access, this must also be done manually.

On the other hand, if you’ve added a SAML SSO configuration, you can retain basic login for global admins. To keep your Eon account secure, all users who aren’t global admins should be managed through your identity provider.

Action approvals

Action approvals add an authorization layer on top of permissions. Users still need the underlying permission to submit an action request, and other users must approve pending action requests before those actions run. They don’t replace roles. They add a separate check for actions covered by approval rules. For more instructions and how to work with action approval requests, see About Action Approvals.

Additional information