Skip to content

Settings reference

Console → Settings holds every circle setting members experience. Two more cards sit at the top: bot connection and danger zone.

Section Fields
Profile & language Circle language (the language of pages and bot notifications)
Appearance Layout (see Choosing your layout); shareable post cards; post tags (up to 20); trading entry and types (Trading Hub)
Entry & pricing Who can join; fee currency; entry price; billing period; membership lengths; renewal discount (0–99%); inviter bonus; pricing mode; trial days (0–365)
Visibility Circle visibility; browse mode (preview requires a paid circle); post and article visibility
Welcome & onboarding Welcome message; introduction card; welcome card buttons (up to 3); auto-enroll on first message; skip contact greeting; community guidelines (Chinese and English)
Announcements & support Notice bar and notice text (up to 200 characters); support contact
Group chat rules Message cooldown (seconds); link / image / voice / card filtering; Spark toggle (Spark messages)
Spam protection Spam protection toggle; strictness; link policy; new-member message threshold; opt out of cross-circle scanning
Member policy Inactivity warnings (7–365 days, 0 to disable); anonymous mode; admins can see real identities; hide member count
Content & posting Who can post; whether questions are allowed

There is also a bot profile card: the bot’s display name on Mixin (up to 36 characters), description (up to 512 characters), and avatar (up to 512 KB). Red-packet risk controls, invite promotion, campaign permissions and the like live on their own dedicated pages, not in this table.

  • Changes are staged first: the page shows a count of staged (unsaved) items, and clicking Review changes walks you through the impact field by field (a price change, for example, cites the last 7 days of renewal data) before anything is published.
  • When admins change settings involving fees or permissions they must provide a reason — the reason is recorded and sent to the circle owner (owners themselves are exempt).
  • Every change is written to the History: settings-publish operations support one-click undo (if the field was edited again afterwards, the undo warns you that it has drifted).