userId, then the SDK uses that ID for login, profile reads, profile updates, search, permissions, and moderation actions.
social.plus does not replace your account system. Keep private identity data in your backend, and send only the stable user ID plus social profile fields your product needs.
Section Map
User Identity
Choose stable user IDs and understand which social profile fields the SDK stores.
User Operations
Create users, retrieve profiles, search users, update profiles, flag users, and manage token workflows.
Roles & Permissions
Check whether the current user can perform actions in global, channel, or community scopes.
Flag and Unflag Users
Add user reporting flows for moderator review.
Implementation Flow
1
Choose a stable user ID
Use an immutable ID from your own system, such as a database primary key or UUID.
2
Log in or create the user
Call the SDK
login method. If the userId does not exist yet, the SDK creates the user.3
Read or update social profile fields
Use user repository APIs for profile reads, search, query, and current-user profile updates.
4
Apply safety and permission checks
Use permission checks for protected actions and flagging APIs for reporting workflows.
Quick Start
- User Identity - Decide what
userIdyour app will send to social.plus. - Create User - Log in or create the user through the SDK.
- Get User Information - Retrieve profiles for known users or user lists.
- Search and Query Users - Build user pickers, directories, or moderation lists.
- Roles & Permissions - Gate protected actions by user capability.