Account and Product Access

Export

Atlas uses your Opsive account to verify which products it can assist with. Your model-provider login is separate: connecting an Opsive account does not sign you in to Codex or configure an API key.

Connect Unity to your account

  1. Open Atlas from the product you want to use. See Installation for the product menus.
  2. Choose Sign in to Atlas.
  3. Complete the one-time browser connection with the correct Opsive account.
  4. If requested, enter the Unity Asset Store invoice for that product.
  5. Return to Unity. Atlas completes the connection automatically after approval.

Atlas's initial sign-in view before opening the one-time browser connection.

The browser checks direct Opsive purchases and invoices already linked to your account. A newly verified invoice is associated with that account. You do not need to copy an Atlas access token into Unity.

Always start the connection from Unity. A bookmarked connection URL may have expired or belong to an earlier attempt. If approval times out, start a new sign-in attempt.

Work with more than one product

Product access is checked separately. Owning State Designer does not unlock Behavior Designer Pro. A product also needs to be installed and compiled in the current project before you can use its Atlas integration.

Changing the active product starts a separate chat. Keep an implementation in the chat for the product it targets, especially when continuing a plan or modifying an earlier result.

Ultimate Character Controller, UFPS, and Third Person Controller use the controller-family integration. A paid add-on still needs to be installed for Atlas to use its add-on-specific catalog context.

Devices and sign-out

Open Settings > Account and devices… to inspect the connection and device controls. Connected devices are also available through your Opsive account. Disconnect a device you no longer use; it must reconnect before making further authenticated requests.

Settings > Sign out ends the Atlas connection in Unity. It does not sign out your independent Codex installation or revoke an API key at its provider. See Privacy and project data for the distinction between account access, local chats, and server records.

If purchase verification fails

Check the signed-in Opsive account and the selected product first. Use the invoice for that product, not a different asset or add-on. If verification still fails, contact Opsive support with the product and verification error. Do not post invoice details, one-time connection links, or credentials in a public forum.