This section covers everything related to managing users in your social.plus SDK application, from user identity and authentication to safety measures and content moderation.

Core Concepts

How social.plus User Management Works

Decentralized Approach: social.plus SDK does not store or manage personal user data. Instead, users are represented by unique identifiers that you control.

Key Principles

1

Your Data, Your Control

social.plus doesn’t store user profiles, emails, or personal information. You maintain full control over your user data in your own systems.
2

Unique User Identifiers

Every user is represented by a unique userId - typically your database primary key or another immutable identifier.
3

Role-Based Permissions

Assign roles and permissions through your admin panel, giving users different privileges and access levels.
4

Query & Search Capabilities

Use social.plus repositories to query user information and perform searches across your user base.

Implementation Workflow

Your Application Handles:
  • User signup/registration
  • Email verification
  • Profile creation
  • User data storage
social.plus Receives:
  • Unique user ID
  • Display name
  • Optional roles
  • Optional metadata

Benefits of This Architecture

What You’ll Learn

User Identity

How user IDs work and best practices for user identification

User Operations

Querying, searching, and managing user data with repositories

Roles & Permissions

Implementing role-based access control and moderation privileges

Content Moderation

Setting up automated and manual content moderation workflows

Safety Features

Implementing user reporting, blocking, and community safety measures

Best Practices

Proven patterns for scalable user management in social applications

Quick Start

Ready to implement user management? Follow this sequence:
  1. User Identity - Understand how user identification works
  2. User Operations - Learn to query and manage user data
  3. Roles & Permissions - Set up access control
  4. Content Moderation - Implement community safety

Common Use Cases

Typical Setup:
  • Users register in your app
  • User ID = database primary key
  • Roles: admin, moderator, verified, standard
  • Features: posts, comments, likes, follows
User Management:
  • Profile updates in your system
  • Social interactions via social.plus
  • Content moderation for community safety
This architecture gives you the flexibility to build social features while maintaining complete control over your user data and compliance requirements.