Using SocialMine

This guide is for tenant users (your customers): creating and scheduling posts, using AI, connecting social accounts, and using collaboration and billing features.

Signing in

• Register and log in through the client app (e.g. /register, /login).
• Email verification and password reset flows use the addresses and SMTP settings configured for your deployment.

Protected areas require a valid session; the app uses JWT-based authentication against the API.

Dashboard

After login, the Dashboard summarizes activity and shortcuts into key workflows (posts, accounts, AI, settings).

Social accounts (OAuth)

Before publishing or scheduling to a network, connect the corresponding profile:

1. Open Social Profile in the sidebar and choose a platform (Facebook, Instagram, LinkedIn, X/Twitter, TikTok, Threads, etc.).
2. Use Connect to start OAuth. You will be redirected to the provider and back to the app after approval.
3. Connected accounts appear per platform; you can disconnect or manage them from the same area.

Requirements:

• The platform must be enabled and configured with app credentials in the admin Social Platform settings. Platform operators should follow Social platform configuration to create apps and permissions in each provider’s developer portal.
• Callback URLs in the provider’s developer console must match what SocialMine expects (based on API_PUBLIC_URL).

Instagram typically requires a Facebook/Meta app with the correct permissions and an Instagram Business account linked to a Facebook Page.

Posts and scheduling

Creating a post

Use Manage Post → routes such as Create Post (/posts/create):

• Title and description (body text).
• Link and media (image/video) as supported by your plan and the target platforms.
• Which accounts to target (selected connected profiles).
• When to post:
  • Immediately — the post is published shortly after submission (subject to API success).
  • Specific date/time — stored as scheduled; the server publishes when the time is due.
  • Draft — saved without publishing; you can finish later.

Templates can be applied if you use Post Template (/posts/templates).

Post lists and calendar

How scheduling works (backend)

• Scheduled posts are stored with status SCHEDULED and a scheduledAt time.
• A background job on the server runs every minute, finds due scheduled posts, and attempts to publish them through the Post Publisher (platform APIs).
• On success, status becomes PUBLISHED and sentAt is set. On failure, status may become FAILED (check logs and provider errors).

Operational note: For scheduling to fire, the NestJS process must be running continuously (not only when someone has the browser open).

AI-powered content

AI features are per-tenant (client) and configured under AI Assistant → AI Configure (/ai/configure).

Configuration

• Provider: Disabled, OpenAI, or DeepSeek.
• API keys are stored for your tenant and used server-side when generating content.
• Optional defaults: language, length, tone, and level—used to shape generations where applicable.

Until a provider is enabled and a valid key is saved, generation endpoints will return an error asking you to configure AI.

Where AI appears

1. AI Writer (/ai/writer)
   Enter a use case and primary keyword, optionally variants (1–10). The API generates content suitable for reuse in posts.

2. Create Post — AI assist
   From the create-post flow you can open the AI modal with topic, prompt, and platform context (e.g. Facebook, Instagram, LinkedIn, X). Generated text can be inserted into the post body.

3. AI Templates (/ai/templates)
   Manage reusable templates that align with your AI and posting workflow (as implemented in your build).

Generation calls the server route POST /api/ai/generate (authenticated), which applies your tenant’s AI settings.

Users and roles

• Users (/users) — manage team members for the tenant where your permissions allow.
• Roles (/users/roles) — role definitions and assignments for access control inside the tenant app.

Exact permissions depend on your subscription and how administrators configured the product.

Subscription and billing

• Upgrade plan and Billing under the Subscription menu connect to your deployment’s plans and payment gateways (e.g. Stripe), as configured in the admin area.

Support tickets

Use Support Ticket to open and track tickets (/tickets, create, and detail views). Attachments and departments depend on server configuration.

Settings

• Settings includes business profile, tax/currency, and branding (logos and appearance where enabled).
• Profile and Security cover the logged-in user (password, etc.).
• Developer API (/developer/api) documents how to call the API with your credentials where exposed.

Demo deployments

If the server runs with DEMO_MODE=true, many write operations are blocked at the API. You may be able to browse the UI, but creating posts, connecting accounts, or changing settings might fail until demo mode is turned off—see Setup.