Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

Sage Intacct Sandbox Login Issues: Troubleshooting and Solutions

Sage Intacct sandbox environments help businesses test configurations, practice workflows, and evaluate changes without affecting their live accounting operations. However, users can occasionally encounter Sage Intacct sandbox login issues when entering their credentials, completing two-step verification, opening the sandbox environment, or accessing their accounts after a refresh. These problems can interrupt testing and delay development work, particularly when users can still sign in to their production company.

The cause is not always an incorrect password. Sandbox access can depend on the correct environment, company ID, user account, assigned permissions, authentication method, and the sandbox’s current status. A refreshed sandbox may also differ from the environment a user accessed previously. Browser session problems, expired verification codes, single sign-on requirements, or account lockouts can create similar symptoms, making it important to identify the actual cause before changing account settings.

This guide explains how to fix Sage Intacct sandbox login issues through practical troubleshooting steps. You will learn how to check sandbox availability, reset a password, resolve verification-code problems, review user access, and investigate issues that begin after a sandbox refresh. Start with the simplest checks and progress to administrative changes only when necessary. Menu names and available sandbox-management features can vary by account configuration, permissions, and Sage Intacct environment.

Why Do Sage Intacct Sandbox Login Issues Occur?

Sage Intacct sandbox login problems generally arise when the sign-in details, environment, authentication requirements, or account permissions do not match the current configuration. A user may enter a valid production password but still fail to authenticate in the sandbox, or may successfully sign in but discover that the sandbox is missing from the available options.

Sage Intacct describes a sandbox as a copy of a production environment used for testing, training, and development. However, a sandbox is a separate environment, and its access requirements should be verified independently.

Common causes of sandbox login problems:

Possible causeTypical symptomWhat to check
Incorrect sandbox environmentProduction opens, but the sandbox does notConfirm the sandbox company ID and login route
Invalid or outdated passwordLogin rejects the entered credentialsVerify the username and reset the password if necessary
Verification-code failureThe password is accepted, but authentication does not finishCheck the selected verification method and code validity
Locked accountRepeated login attempts failStop retrying and ask an administrator to check the account
Missing sandbox permissionsThe sandbox option is unavailableReview role or user permissions
User not available in the sandboxOther users can access the environment, but one user cannotCheck the user record and sandbox access configuration
Sandbox refreshLogin behavior changes after the environment is refreshedVerify the refreshed company’s state and user configuration
Single sign-on mismatchDirect password login fails unexpectedlyConfirm whether the user must authenticate through the organization’s identity provider
Browser session issueLogin loops, stale pages, or repeated prompts appearTest a private browser window and clear relevant site data
IP restrictions or security controlsCredentials appear correct, but access is deniedAsk an administrator to review company security settings

These symptoms can overlap. For example, a user who has entered an incorrect verification code repeatedly may become locked out, while a user whose password was reset may be prompted to complete two-step verification again. Sage Intacct documents both behaviors in its sign-in guidance.

How to Fix Sage Intacct Sandbox Login Issues?

Follow the solutions below in order. If several users are affected, check the environment’s status and company-wide authentication settings before asking everyone to reset their passwords. If only one person is affected, focus first on that user’s credentials, verification method, and access permissions.

1. Confirm You Are Opening the Correct Sandbox Environment

One of the easiest mistakes is trying to open the production company or another environment instead of the intended sandbox. This is especially likely when a company has several sandboxes for testing integrations, training employees, or evaluating configuration changes.

How to check the environment:

  1. Open the Sage Intacct sign-in page or your organization’s approved Sage Intacct access route.
  2. Confirm that you are using the intended sandbox login option.
  3. Check the sandbox company ID provided by your administrator.
  4. If your organization uses a sandbox-specific link or console, access the environment through that approved route.
  5. Compare the environment name or company ID displayed after login with the sandbox you intended to open.

Sage Intacct’s sandbox documentation explains that sandbox names can incorporate the production company ID and a user-entered sandbox name. The Sandboxes page also distinguishes between states such as Pending, In progress, Ready, and Failed. A sandbox must be ready before you can log in to it.

If you cannot find the sandbox, ask your administrator to confirm that it exists, has finished provisioning, and is available to your account. Do not assume that a missing sandbox is caused by a password problem.

2. Check Your Sage Intacct Sandbox Login Credentials

If the sandbox opens but rejects your login, check the credentials before changing any security settings. A valid account name does not guarantee that every environment will accept the same password or authentication route.

Use this checklist:

  • Confirm that the username is spelled correctly.
  • Check for accidental spaces before or after the username.
  • Verify that Caps Lock and the keyboard language are correct.
  • Enter the password manually if a password manager may be supplying an outdated value.
  • Make sure you are not using credentials for a different Sage account or a separate Sage Intacct Community account.
  • Confirm whether the account requires single sign-on rather than direct password authentication.

Avoid repeatedly submitting possible passwords. Sage Intacct warns that multiple incorrect verification attempts can result in an account lockout, and its login troubleshooting guidance also describes lockouts caused by repeated failed sign-ins.

If the same credentials work in production but not in the sandbox, do not immediately conclude that the entire account is broken. Confirm the sandbox company ID, the user record available in that environment, and the applicable password and authentication settings.

3. Reset Your Sage Intacct Sandbox Password

A password reset is appropriate when the password is forgotten, rejected despite careful entry, or potentially changed by an administrator. However, the correct reset process depends on how the user account is configured and whether the user can complete the required identity verification.

Sage Intacct’s standard password-reset instructions direct users to select Forgot your password? on the sign-in page. Reset instructions are sent to the account email, and the user may need to answer the security question configured in My preferences. If recovery information has not been set up, the user should contact the designated support user or administrator.

To reset the password:

  1. Open the appropriate Sage Intacct sign-in page.
  2. Select Forgot your password?
  3. Enter the username or account details requested on the reset page.
  4. Check the email address associated with the account.
  5. Follow the official reset instructions and complete any required identity verification.
  6. Create a new password that meets the displayed requirements.
  7. Return to the intended sandbox and test the new credentials.

If the reset email does not arrive, check spam, junk, quarantine, and other filtered folders. Verify that the account email address is correct, and ask your administrator to confirm it if you cannot access the account.

Important: Do not assume that resetting a password for a separate Sage account, Community account, or identity-provider account will reset the Sage Intacct business-user password. Identify which sign-in system the sandbox uses before performing the reset. If the self-service process fails, ask the Sage Intacct administrator to reset the user’s password using the supported administrative workflow. An administrator may be able to assist when the user has forgotten their security-question answer or cannot complete self-service recovery.

4. Resolve Sage Intacct Sandbox Verification-Code Problems

Sometimes the password is accepted, but the user cannot finish signing in because the verification code is missing, invalid, or being sent to an inaccessible device. Sage Intacct supports two-step verification methods that include an authenticator app, text message, or phone call, depending on the account configuration. 

If Sage Intacct sandbox keeps asking for a verification code, determine whether the prompt is expected or whether the configured verification method is no longer usable. Try these steps:

  1. Confirm which verification method is displayed on the sign-in screen.
  2. If using an authenticator app, open the app associated with the configured account and use its current code.
  3. If using text or phone verification, confirm that the registered phone number is still available.
  4. Request a new code through the official sign-in flow if the page offers that option.
  5. Enter the latest code carefully and avoid reusing an older code.
  6. Check that your phone can receive messages or calls and that unknown senders are not being blocked.
  7. If the code still fails, stop repeated attempts and contact the administrator.

Do not share verification codes with colleagues or anyone claiming to provide unofficial support. A legitimate administrator should use the approved account-management process to investigate access. Sage Intacct’s two-step verification guidance explains that incorrect codes count as failed login attempts and that repeated failures can lock a user out. If a user cannot receive a code, an administrator may need to reset the verification method so the user can set it up again.

5. Fix Sage Intacct Sandbox Two-Step Verification Issues

Two-step verification is an additional security requirement beyond the username and password. The user may need to complete an initial setup, use an existing authentication method, or reconfigure verification after losing access to a phone or authenticator app.

Sage Intacct states that two-step verification is enabled by default for production companies and users. The available controls for non-production companies can differ, so sandbox requirements should be checked rather than inferred from production behavior. For users who can still access their preferences:

  1. Sign in through the required authentication route.
  2. Open the user menu and select My preferences.
  3. Review the security and two-step verification options available to your account.
  4. Confirm that the primary verification method is current.
  5. If supported, configure a backup method to reduce the risk of future lockouts.

For users who cannot complete verification:

Ask a Sage Intacct administrator to review the user’s verification settings. Depending on the configuration, the administrator can manage the primary method, backup method, and trusted devices through the user-management area. The official instructions describe the user-preferences workflow and administrative controls for verification.

Do not disable security controls simply to bypass a login issue. If a change is genuinely necessary, an authorized administrator should follow the company’s security policy and Sage Intacct’s documented procedure. Where single sign-on is configured, direct login and two-step verification behavior may differ from the standard password-based flow.

6. Check Whether Single Sign-On Is Required

Some organizations configure Sage Intacct users to authenticate through a corporate identity provider. When single sign-on (SSO) is enabled for a user, direct password login may not be permitted. Entering a familiar password into the standard sign-in page can therefore fail even when the user account remains active.

Sage Intacct documents that users configured for SSO must authenticate through the organization’s SSO identity provider instead of logging in directly with an Intacct password. Its documentation also describes requirements and limitations for SSO access.

How to troubleshoot an SSO-related login failure:

  1. Confirm with your administrator whether the sandbox user is configured for SSO.
  2. Open the organization’s approved SSO portal or sign-in route.
  3. Sign in using the identity-provider account required by your organization.
  4. If the identity provider rejects the login, resolve that issue through the organization’s IT or identity-management team.
  5. If the identity-provider login succeeds but Sage Intacct still denies access, ask the administrator to review the user’s SSO configuration and sandbox access.

Do not change the user’s SSO setting on your own. An administrator should verify the intended authentication policy before switching a user between SSO and direct login.

7. Verify Sandbox User Permissions

A user may be able to log in to Sage Intacct but still be unable to see or open the sandbox. This can occur when the user or assigned role does not have the necessary sandbox permissions.

Sage Intacct’s official instructions state that users must have sandbox permissions assigned to a role or user before the Sandboxes application becomes available. The documented permissions include List, View, Add, Edit, Delete, and Refresh, although the exact permissions required depend on the action the user needs to perform.

For an administrator reviewing role permissions:

  1. Go to Company > Admin > Roles.
  2. Find the role assigned to the user.
  3. Open the role’s Subscriptions or permissions area.
  4. Locate the Company application.
  5. Review the sandbox permissions and assign only those required for the user’s responsibilities.
  6. Save the changes and verify whether the sandbox option becomes available.

To review permissions assigned directly to a user:

  1. Go to Company > Admin > Users.
  2. Find the relevant user.
  3. Open the user’s Subscriptions or permissions area.
  4. Locate the Company application and review the sandbox permissions.
  5. Save authorized changes and ask the user to sign in again.

Menu labels can vary with the interface and account configuration. Follow the permissions documentation available in your Sage Intacct environment if the navigation differs.

Granting every sandbox permission is not necessary for every user. Someone who only needs to enter an existing sandbox may not require permission to create, delete, or refresh one. Use the principle of least privilege and reserve environment-management permissions for authorized administrators.

8. Restore User Access After a Sage Intacct Sandbox Refresh

A sandbox refresh replaces the sandbox’s existing state with an updated copy of production. This helps keep the test environment current, but it can also explain why a user, permission, or authentication setting appears different after the refresh.

Sage Intacct describes refreshing a sandbox as creating an up-to-date copy of the production environment. Refresh operations require the appropriate permissions, and access to self-service sandbox management depends on the company’s eligibility and configuration. If you could log in before the refresh but cannot now, work through the following checks.

  1. Confirm that the refresh finished. Ask the administrator to check the sandbox’s status. If it is still being created or refreshed, wait until it is ready.
  2. Verify the environment. Confirm that you are opening the same sandbox company ID and not a different sandbox or production company.
  3. Review the user record. Ask an administrator to confirm that your user exists in the refreshed environment and has the intended status and access.
  4. Check permissions again. Confirm that the user or assigned role has the required sandbox permissions and access to the relevant applications.
  5. Recheck authentication. Verify whether the current environment requires direct login, SSO, or two-step verification.
  6. Test the sign-in process again. Open a fresh browser session and use the approved sandbox access route.

A refresh should not be treated as proof that a password is wrong. First determine whether the issue affects one user or several. If multiple users lose access immediately after the same refresh, an administrator should investigate the refreshed environment and its configuration before each user resets a password. If the expected user or permissions cannot be restored through normal administration, contact Sage Intacct support or the organization’s designated support user. Provide the refresh date, sandbox name, affected usernames, and exact error message.

9. Add or Restore a Missing Sandbox User

If your user account is missing from the sandbox, an administrator should verify whether the account exists in the current environment and whether the user is correctly configured. The fact that someone has production access does not automatically establish that every sandbox permission or access path is correct.

Sage Intacct’s user-administration documentation explains that adding users requires appropriate administrative privileges. Creating or changing user records should therefore be handled by an authorized administrator. Recommended administrator checks:

  • Search for the user in the sandbox’s user-management area.
  • Confirm that the user is active and associated with the expected account.
  • Review the user’s role, subscriptions, and sandbox permissions.
  • Check whether the organization uses SSO and whether the user’s identity-provider details are configured correctly.
  • Confirm that the user is accessing the correct company environment.
  • If the user record is absent, follow the organization’s approved process for adding or restoring access.

Before creating a new user, check whether an existing record can be corrected. Duplicate accounts can complicate access management, audit trails, and permission assignments. The administrator should also confirm that the organization’s subscription and user limits permit the intended change. If the user appears in the administration area but still cannot access the sandbox, investigate permissions and authentication rather than creating another account.

10. Troubleshoot Browser and Session Problems

Browser problems are worth checking when the sign-in page repeatedly reloads, returns to the login screen, shows an unexpected error, or behaves differently from another browser. Cached pages, stale sessions, and conflicting browser extensions can interfere with a login workflow. Try these steps in order:

  1. Close the Sage Intacct tabs you are no longer using.
  2. Open a new private or incognito window.
  3. Navigate to the organization’s approved Sage Intacct sign-in page.
  4. Enter the correct sandbox credentials and complete the required authentication steps.
  5. If the private window works, clear the relevant site data in your regular browser.
  6. Temporarily disable browser extensions that may interfere with sign-in, subject to your organization’s IT policies.
  7. Restart the browser and test again.

If you use a password manager, verify that it is not filling credentials from another Sage product or a different company environment. You may also need to sign out of an old session before opening the intended sandbox.

Do not clear all browser data as the first step if doing so could disrupt other business applications. Start with a private window to help determine whether the issue is related to the existing browser session. If the same failure occurs across multiple supported browsers and affects other users, ask your administrator to investigate the environment or authentication configuration instead of repeating browser cleanup.

11. Check Account Lockouts and Security Restrictions

Repeated failed sign-ins can lead to an account lockout. Security controls can also reject a login when a user accesses the company from an unfamiliar location or an IP address that is not permitted by company policy.

Sage Intacct’s login troubleshooting guidance explains that administrators can help unlock users after excessive failed attempts. It also recommends checking company IP-address filtering when credentials are known but access is still denied. What to do:

  • Stop trying additional passwords or verification codes.
  • Check your email for an account-lockout or security notification.
  • Contact the Sage Intacct administrator and explain what happened.
  • Ask the administrator to check the user’s status and recent access attempts.
  • If IP filtering is enabled, ask the administrator to confirm whether the current network is permitted.
  • If the account is locked, follow the supported unlock or password-reset process.

If you recently changed networks, started using a VPN, or moved to a different location, mention this to the administrator. These details may help identify whether a security rule is involved. Do not attempt to bypass company security restrictions by using an unapproved network or device. The administrator should confirm that the access is legitimate and make any required changes according to company policy.

12. Determine Whether the Problem Is With the Sandbox or the Whole Service

The scope of the problem can help you choose the next step. If only one user is affected, investigate that user’s account, authentication method, and permissions. If several users cannot enter one sandbox, investigate the sandbox’s status and configuration. If production and multiple sandboxes are all inaccessible, consider a broader authentication or service issue.

Use this quick diagnostic guide:

What you observeRecommended next action
Only one user cannot sign inCheck credentials, account status, verification, SSO, and user permissions
Several users cannot access one sandboxCheck sandbox status, company ID, and environment configuration
Login works, but the sandbox is missingReview sandbox permissions and whether the sandbox is ready
Password works but verification failsCheck the configured verification method or request administrator assistance
Access failed immediately after a refreshReview user access and authentication settings in the refreshed environment
Multiple environments fail for several usersAsk the administrator to investigate broader authentication or service issues

If you suspect a service disruption, consult your organization’s support process and Sage Intacct support resources. Record the time the issue began and whether other users can reproduce it. This information helps distinguish an account-specific problem from a broader one.

13. Contact Sage Intacct Support When the Problem Persists

If the steps above do not resolve the issue, contact your organization’s designated support user, Sage Intacct administrator, or the appropriate Sage support channel. Prepare the following information before submitting a case:

  • The sandbox name and company ID.
  • The date and approximate time of the failed login.
  • Whether production login still works.
  • Whether one user or multiple users are affected.
  • The exact error message, copied without changing its wording.
  • Whether the issue began after a password reset, verification change, or sandbox refresh.
  • The browser and sign-in method being used.
  • The troubleshooting steps already completed.

Include screenshots only when they do not expose passwords, verification codes, confidential financial information, or other sensitive data. Never send a password or one-time verification code in a support request.

Sage Intacct’s support guidance notes that case priority and response expectations depend on business impact, environment, and the applicable service agreement. Identify the affected environment as a sandbox when submitting the case. Providing clear diagnostic details reduces unnecessary back-and-forth and helps support teams determine whether the problem concerns the user account, security settings, sandbox provisioning, or the wider environment.

How to Prevent Sage Intacct Sandbox Login Issues

Preventive account management can reduce repeated sign-in failures and help teams recover more quickly when authentication settings change.

  1. Keep recovery information current: Review your account email address, security question, and available recovery methods while you can still sign in. Sage Intacct’s user-preferences documentation explains that recovery information is used during password recovery and that administrators may need to assist users who have not configured the required information.
  2. Configure a backup verification method: Where supported, maintain a backup method for two-step verification. If your primary phone is lost or unavailable, a configured backup can help you complete authentication without an extended interruption. Store any recovery codes securely and follow your organization’s security policies.
  3. Document the correct sandbox login route: Keep an internal record of the sandbox name, company ID, approved sign-in link, and authentication method. This is particularly useful for organizations with multiple sandboxes or SSO requirements. Avoid relying on old browser bookmarks without confirming that they still point to the intended environment.
  4. Review access before and after refreshes: Before refreshing a sandbox, communicate the planned change to users and document any configuration or access requirements that may need attention afterward. Once the refresh is complete, verify that the environment is ready and that key users can sign in.
  5. Apply permissions according to job responsibilities: Grant only the sandbox permissions each person needs. Users who simply test workflows should not automatically receive permissions to create, delete, or refresh environments. Review role assignments when employees change responsibilities or leave the organization.
  6. Avoid repeated failed login attempts: If a password or verification code fails, verify the details before trying again. Repeated incorrect attempts can cause lockouts, so contact the administrator when the reason for failure is unclear.
  7. Maintain a simple troubleshooting record: Document recurring login issues, their causes, and the verified resolutions. Include the environment, error message, and whether the issue followed a refresh or security change. Avoid storing passwords or verification codes in these records.

Conclusion

Sage Intacct sandbox login issues can result from incorrect credentials, verification-code failures, SSO requirements, missing permissions, account lockouts, browser sessions, or changes following a sandbox refresh. The most effective solution is to identify where the login process fails instead of resetting passwords or changing security settings unnecessarily.

Start by confirming the correct sandbox company ID and checking your credentials. Next, review password recovery, two-step verification, and SSO requirements. If you can sign in but cannot access the sandbox, ask an administrator to review your user record and sandbox permissions. When access problems begin after a refresh, verify that the environment is ready and that the relevant access settings are correct.

If these checks do not resolve the issue, contact your Sage Intacct administrator or support team with the exact error message and details about the affected environment. Following a consistent troubleshooting process helps restore access while protecting the security and integrity of your production and sandbox environments.

FAQs of Sage Intacct Sandbox Login Issues:

Why does my Sage Intacct password not work in the sandbox?

Your password may be incorrect, outdated, or associated with a different account or login method. You might also be opening the wrong sandbox company ID or using direct login when your organization requires SSO. Verify the environment and username first. If the password continues to fail, use the supported password-reset process or ask your administrator to review your account.

How do I reset a Sage Intacct sandbox password?

Open the appropriate Sage Intacct sign-in page and select Forgot your password? Follow the instructions sent to your registered account email and complete any required identity verification. If you cannot access the recovery email or answer the required security question, contact your Sage Intacct administrator or designated support user for assistance.

How do I fix Sage Intacct sandbox two-step verification issues?

Check that you are using the configured authenticator app, phone number, or other supported verification method. Use the current code and avoid repeated incorrect attempts. If your phone is unavailable or codes are not arriving, ask an administrator to review your verification settings and reset the method if necessary. Do not share verification codes with anyone.

Can I use my production password to log in to Sage Intacct sandbox?

Do not assume that a production password will work in every sandbox configuration. Confirm the credentials and authentication requirements for the specific sandbox, especially if a refresh or password change occurred recently. If production login succeeds but sandbox login fails, check the company ID, user record, and authentication settings before resetting credentials.

Why can I log in to Sage Intacct but not the sandbox?

You may lack the required sandbox permissions, be using the wrong environment link, or be trying to access a sandbox that is not yet ready. Ask your administrator to confirm the sandbox’s status and review the permissions assigned to your user or role. If the problem started after a refresh, have the administrator check access in the refreshed environment.

How do I restore user access after a Sage Intacct sandbox refresh?

First, confirm that the refresh has completed and the sandbox is ready. Then ask an administrator to verify the user record, role assignments, sandbox permissions, and authentication requirements. Test the approved login route again. If the account is missing or access remains restricted, follow the organization’s approved user-administration process or contact Sage Intacct support.

How do I resolve Sage Intacct sandbox authentication errors that persist after troubleshooting?

Record the exact error message, sandbox company ID, time of failure, and whether other users can sign in. Tell your administrator whether production access works and whether the problem followed a refresh, password reset, or security change. The administrator can investigate account status, SSO, verification settings, permissions, and IP restrictions before escalating the issue to Sage Intacct support.

Related Articles