zai-org / zai-org/feedback

[Feature Request] Promo account sharing - Share quota with friends via referral link

Open
#238 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Feature: Promo Account Sharing

Allow users to generate sharing links so friends can use Z.ai products (GLM, chat.z.ai) charged against the original user quota.

Concept:

User A generates link -> Friend B clicks -> Friend uses product -> Charged to User A quota

"Your friend wants to try GLM out, you give him a link and as he is using the product - your quota gets drained." — DCCCXIX

Link Types:
  • Quota-limited ($5/$10/$20)
  • Time-limited (24h/7d/30d)
  • One-time or unlimited (revocable)
Business Value:
  • Viral growth, zero acquisition cost
  • Product-led growth, no friction
  • High trust via friend recommendations
  • Trial users likely convert to paid
Security Limits:
  • Free: 1 link, $10/month, 5 recipients
  • Paid: 5 links, $50/month, 25 recipients
  • Pro: Unlimited + revenue share
Phases:
  1. MVP: Basic share links + dashboard
  2. Analytics + time-limited links
  3. Revenue share + API access

Reporter: DCCCXIX (Discord)
Thread: https://discord.com/channels/1346756824233148527/1536668456022442105

Priority: High (viral growth, low cost)


Submitted by: Regards, Roman (Discord: bignavi_x) - Z.ai Volunteer Ambassador - https://t.me/VibeCodePrompterSystem - http://claw.rommark.dev/blog

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or implementation entry points. Start by turning the proposed link types, quota limits, recipient limits, revocation, dashboard, and phased analytics into agreed requirements, then identify the account, quota, and product-access components they affect. Done requires a maintainer-approved scope and acceptance criteria before implementation begins.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.