Company login settings

Control who can log in to your company, how they log in, and how long their session lasts.

To change your company security features and settings, go to Company > Setup > Configuration > Company > Security tab, then select Edit.

Timeout settings

Set how long users can stay logged in or remain inactive before Sage Intacct automatically logs them out.

Two timeout types are available:

  • Default inactivity duration: On a company-wide level, the admin determines how long all users can remain inactive before they’re automatically logged out. Users receive an alert when one minute remains.
  • Default session duration: On a company-wide level, the admin determines how long all users can be logged in for any session before they’re automatically logged out, regardless of their activity. Users receive an alert when one minute remains.
Users can adjust their own inactivity and session durations beyond the default values. Set a Maximum value for either setting to limit how far users can extend their own timeouts.

To set a timeout:

  1. Set the Default inactivity duration using the hours and minutes dropdowns.
  2. Optionally, set a Maximum inactivity duration to cap how long any user can extend their own inactivity setting.
  3. Set the Default session duration using the hours and minutes dropdowns.
  4. Optionally, set a Maximum session duration to cap how long any user can extend their own session settings.
  5. Save your changes.

Timeout alerts

Users receive an in-app alert one minute before a timeout occurs.

Inactivity timeout alert: Users receive an alert one minute before the inactivity duration is reached. Users can select one of three options:

  • Stay logged in: The session stays open.
  • Log out: The session ends and the login page appears.
  • Do nothing: The session ends when the inactivity duration is reached.

Session timeout alert: Users are prompted to save their work. When the session duration ends, they're logged out automatically.

Desktop notifications

If a user switches to another tab or application, timeout alerts can be hidden. Desktop notifications ensure that users see the alert even when Intacct is not the active window.

To enable desktop notifications from your user preferences page:

  1. Select the User menuUser circle at the top of any Intacct page and select My preferences.
  2. Under Timeout settings, select Enable browser notifications. A browser permission prompt appears.

  3. Grant permission. Intacct replaces the link with text: Desktop notifications will appear whenever your session is about to time out.

Desktop notification permissions can also be managed directly in your browser settings. The steps vary by browser. The following example uses Chrome.

To manage notifications in Chrome:

  1. Select the three vertical dots in the upper right and select Settings.
  2. Select the Privacy and security tab.
  3. Select Site settings.
  4. In the Permissions section, select Notifications.
  5. Scroll to the Customized behaviors section.
  6. In the Allowed to send notifications option, select Add.
  7. In the Site field, enter intacct.com.
  8. Select Add.

Password settings

Customize the password policy for all users in your company. For more information about Intacct password requirements, see Password policy and requirements

Customizable password policy components include:

Password field descriptions
FieldDescription

Reset password

Defines how long a password lasts before you must change it. Your options span from as sparingly as yearly to as often as weekly.
An admin can override this option for specific users in their user information, but it should only be overridden for users with integrations or API applications that rely on an Intacct user ID and password for connectivity.

Minimum password length

Defines how long an accepted password must be. The minimum requirement is eight characters.

Prevent reuse of passwords

Select the number of recent passwords that a user cannot reuse when they reset their password. The minimum requirement is that users cannot reuse the last three passwords.

To set password requirements:

  1. For Reset password, select how frequently users must change their passwords. Options range from weekly to yearly.

    If you have an integration or API application that uses an Intacct user ID and password for connectivity, go to Company > Admin > Users and permissions > Users, open the user associated with the integration, and select Keep my password until I reset it on the User information tab. This prevents a scheduled reset from disrupting the connection.

    See Field descriptions: User information and Password policy and requirements for more information.

  2. For Minimum length, select the minimum number of characters required for a valid password. The minimum allowed is eight characters.

    Password requirements: Each password must:
    • Contain at least eight characters long AND
    • Contain at least one number, one lowercase letter, one uppercase letter, and one special character.

    For instance, 1$g*1LHd is a strong password. See Password policy and requirements for more information.

  3. For Prevent reuse of previous passwords, select the number of recent passwords users cannot reuse. You can require between three and 20 unique passwords before reuse.

  4. Save your changes.

Login and reset attempts

Control how many failed login or password reset attempts are allowed before an account is locked.

To set your login and reset attempt settings:

  1. For Maximum login attempts per day, select the maximum number of failed login attempts allowed in a 24-hour period. A successful login resets the counter. After this limit is reached, only an administrator can unlock the user.
    After Intacct locks out a user, only an administrator can unlock a user.
  2. For Maximum reset attempts per day, select the maximum number of password reset attempts allowed in a 24-hour period. You can set this between 1 and 10.
    When the number of attempts is exceeded for the period, only the administrator can reset the password until the period is over. Then, the user can try again.
  3. For Maximum number of verification attempts for a password reset, select the maximum number of times a user can enter incorrect information during a password reset. When this limit is reached, the account is locked for 24 hours.
  4. Save your changes.

Enforce IP address filters

For extra security, you can enforce IP address filters. Enforcing address filters means only locations with known IP addresses (such as those coming from your corporate office) can be used to log in to your Intacct company. When you enforce IP address filters, any login that does not come from the list of allowed IP addresses is denied, preventing login attempts from unknown locations.

The following enforcement options are available:

OptionDetails
NoneUsers can log in from anywhere.
Enforce at company levelAll users can only log in from specified range of IP addresses for your company.
Enforce at company level and override at user levelUsers can log in from either the company IP range or their individually specified IP addresses.
Enforce at user levelUsers can only log in from any of their individual, specified IP addresses.
If you enable IP filtering but do not create any filters, Intacct has no IP address range to verify against. Login attempts are not restricted. This has the same effect as selecting None.

To add approved IP addresses:

  1. Select the pencil icon in the Enforce IP address filters section.
  2. In the IP Address Filter Information window, select Add.
  3. Enter an IP address or IP address range.

    • To enter a single address, enter the same IP address in both the Start IP address and End IP address fields.

    • For company-level: Only enter the IP address or address range. Leave the Username field empty.

    • For user-level: Select the Username, and enter the IP address or address range.

      You can add multiple records per user, for example, if a user logs in from two locations, add a separate record for each IP address.

  4. Save your changes.
If IP filtering is enabled and a user cannot log in, verify that their IP address is listed in the allowed addresses. Select the pencil icon next to the dropdown and verify the list.

Enable two-step verification

Add an extra layer of security to your account with two-step verification.

You can require users to verify their identity with a code in addition to their username and password. Codes are delivered via an authenticator app, text, or phone call.

Users who regularly log in from a personal device can mark it as a trusted device to skip the verification step in the future. To prevent this, see the Do not allow trusted devices option below. For more information, go to Set up two-step verification.

You can set up both SSO and 2-step verification for your company.

Users who sign in through their SSO identity provider bypass two-step verification. Users who are not configured for SSO and log in directly to Intacct are required to complete two-step verification. This setup provides a fallback layer of protection, for example, if SSO is temporarily unavailable, an admin can still log in using their Intacct credentials and two-step verification.

If your company also has passkey authentication enabled, users who sign in with a passkey are not prompted for a two-step verification code. The passkey satisfies the strong authentication requirement on its own. Users who sign in with their password instead go through two-step verification as usual.

To enable two-step verification:

  1. Select the Enable 2-step verification checkbox.
  2. Select which users must enter a verification code:
    Verification options
    FieldDescription

    Selected users

    Select if you want to require verification for only selected users.

    To enable 2-step verification for selected users, go to Company and select Users. Then, select Edit and enable 2-step verification for each user.

    All users

    Select if all users must enter a verification code.

  3. Optionally, select Do not allow trusted devices to require a verification code on every login, even from previously trusted devices. When this is enabled, users cannot bypass the verification step.
  4. Save your changes. Users receive an email notification when 2-step verification is enabled for their company.

Passkey authentication

Allow users to sign in with a passkey, which is a device-based method that uses a biometric or a PIN instead of a password. Passkeys are phishing-resistant and work alongside your existing login settings without requiring any changes to your password or two-step verification configuration.

Passkey authentication is available to non-SSO users only. Users who sign in through an SSO identity provider are not affected by this setting.

When a user signs in with a passkey, they are not prompted for a two-step verification code, even if two-step verification is enabled for your company. If they sign in with their password instead, two-step verification applies as usual.

To enable passkey authentication:

  1. Select the Enable passkey authentication checkbox.

  2. Save your changes.

Once enabled, users can register their devices and sign in with a passkey from My preferences > Security > Passkey Authentication. For more information, see Passkey authentication.

To disable passkey authentication for your company, clear the checkbox and save. Users with registered passkeys will not be able to use them while this setting is off.

Field descriptions

Timeout field descriptions
FieldDescription

Default inactivity duration

The first 2 pick lists set the standard hours and minutes a user session can remain inactive before Intacct automatically logs out the user. Because this setting can be adjusted in the user configuration, the third column limits the maximum number of hours a user can set for their session time-out. Users receive an alert when one minute of the inactivity duration remains.

Default session duration

Unlike inactivity duration, which affects an inactive session, login timeout is a fixed limit regardless of the users' activity. The first 2 pick lists set the standard hours and minutes a user can remain logged in before Intacct automatically logs out the user. Because this setting can be adjusted in the user configuration, the third column limits the maximum number of hours a user can set for their timeout. Users receive an alert to save their work one minute before the session duration ends.

Password field descriptions
FieldDescription

Reset password

The time period after which a user must reset their password. You can override this option on the user configuration page for users with integrations, or API applications that rely on an Intacct user ID and password for connectivity.

Minimum password length

Set the minimum password length to be between 8-12 characters. The default is 8 characters.

Prevent reuse of previous passwords

Select between 3-20 for the number of recent passwords that cannot be reused when resetting a password.

Login attempts field descriptions
FieldDescription

Maximum login attempts per day

The number of failed login attempts a user can make in a 24 hour period before Intacct locks them out. Select between 1-20 login attempts before being locked out. The recorded number of attempts resets after a successful login. After Intacct locks out a user, only an administrator can reset user status from Locked out to Active. This setting applies to all users.

Maximum reset attempts per day

The number of attempts that can be tried by a user in a 24-hour period. You can set the number of reset attempts to between 1-10 attempts.

Maximum number of verification attempts for a password reset

This is the maximum number of times the incorrect information can be entered in a password reset attempt. When the limit is reached, Intacct locks the account for 24 hours.

Enforce IP address filters field descriptions
FieldDescription

Enforce IP address filters

When you enforce IP address filters, any login that does not come from the list of allowed IP addresses is denied. Denying these logins adds an extra level of security by preventing login attempts from unknown locations. You can specify ranges of known IP addresses for your company, allowed IP addresses for each user, or a combination of both.

You can enforce IP address access in these ways:

  • None: Users can log in from anywhere.
  • Enforce at company level: All users in the company are restricted to logging in from the range or ranges of IP addresses that you specify.
  • Enforce at company level and override at user level: Users can log in either from the company range of IP addresses or from one or more IP addresses specified in their IP address filters. For example, you can specify that everyone log in from the office. You can then allow your CFO be able to log in either from the office or from home. In this case, the CFO needs 2 filters: 1 for the office and 1 for home.
  • Enforce at user level: Each user must have an IP address filter with a specific address. Users who do not have an explicit IP address filter cannot log in. Individual IP filters are required for login, even within the office range.
When Enforce IP address filters is enabled, and a user cannot log in, verify that their IP address is listed in the allowed addresses. Select the pencil icon next to the dropdown menu and verify their IP address.
Enable two-step verification field descriptions
FieldDescription

Enable verification at login

Add a layer of security to your account. When a user logs in, they need enter a verification code they receive via an authenticator app, text, or phone call. This code is entered in addition to the user ID and password. If a user routinely logs in from a computer only they use, they can identify it as a trusted device and skip this extra step.

For more information, see Setup 2-step verification.

You can set up both SSO and 2-step verification for your company.

Users who sign in through their SSO identity provider bypass two-step verification. Users who are not configured for SSO and log in directly to Intacct are required to complete two-step verification. This setup provides a fallback layer of protection, for example, if SSO is temporarily unavailable, an admin can still log in using their Intacct credentials and two-step verification.

If your company also has passkey authentication enabled, users who sign in with a passkey are not prompted for a two-step verification code. The passkey satisfies the strong authentication requirement on its own. Users who sign in with their password instead go through two-step verification as usual.

Selected users

Select individual users who must enter a verification code at login. To enable selected users, go to Company > Admin > Users. Then select Edit, and enable 2-step verification for each user.

All users

Select to require all users enter a verification code at login.

Do not allow trusted devices

After selecting Enable 2-step verification, you can select Do not allow trusted devices for higher security. Every time a user logs in, they'll need to enter a verification code they receive via an authenticator app. This code is entered in addition to the user ID and password.

Passkeys
FieldDescription

Enable passkey authentication

Select to enable passkey authentication for your company.

Allows non-SSO users to register devices and sign in using a passkey instead of a password. When enabled, users who sign in with a passkey are not prompted for a two-step verification code. Disabling this setting prevents passkey sign-in but does not delete registered passkeys.

Passkeys are optional for users who do not use single sign-on (SSO). Existing password and multi-factor authentication (MFA) methods remain available as a backup.

See Enable passkey authentication for more information.