Login management primarily focuses on selecting user IDs and identifying game client code paths to perform client-side login and authorization. The typical solution for signing in to the Vivox network is to associate your user's in-game account or character ID with a separately generated unique user ID or to use the account ID directly for identification.

Your game implementation must approve users who sign in to the Vivox network in advance. After a sign-in is approved, the game assigns a user ID to the client and instructs it to sign in with a provided access token. The client then signs in, is associated with the user ID that is provided, and can then perform voice operations within the Vivox network.

Several Vivox features rely upon the re-use of a player’s Vivox username or account ID. It’s important to remember to not send Vivox actual account names, or any identifiable information, such as a Vivox username or account ID. There must be a 1:1 relationship between your created ID for each session a player is logged in.

Because user IDs are selected on an ad-hoc basis and aren't preserved across sessions, it's important to select a unique ID that either persists with your game's user data or is newly generated during each successive sign-in.

For example, Player1 is hashed to 1a2b3c4d5e6f7g the first time they access Vivox through your game. The next time they access Vivox services through your game they will again be assigned 1a2b3c4d5e6f7g.

Special cases exist in which you can create permanent, persisted, password-authenticated users for your game server or for administrative purposes. You can create these accounts by using the Admin API. For more information, see the API Reference documentation.