User overview

End users need a valid Nexconn token before the client can connect and exchange messages. Your app server obtains that token for the current App Key and returns it to the client.

Register users

Your app server exchanges a business userId for a Nexconn token. See the Register user API for HTTP details.

Clients obtain tokens from your server during login, then call NCEngine.connect (see Quickstart). Manage keys in the Nexconn Console.

Environment quotas and seat counts follow your console contract; this page does not list numeric caps.

Delete users

In development, users with the required console permissions can usually delete test users from the Nexconn Console to control account sprawl. Confirm the current console entry point and environment before deleting users.

Production deletion policies depend on your console contract and compliance requirements. Do not assume that development deletion behavior is available in production.

Deactivate users

For compliance-driven account closure, use the server-side user lifecycle APIs. Data retention after deactivation follows your backend and platform policy.

User profiles

Nexconn does not host nicknames, avatars, or group names for your product. ChatUI reads display data from ServiceHooks implementations (see Hooks).

Friend relationships

Friend graphs live entirely in your services; Nexconn Chat does not store or sync social graphs for you.