A way to Lock new users to Level 0?

AI 生成的摘要

The discussion revolves around locking new users to trust level 0 in a Discourse forum using SSO. Becky_Herndon seeks a way to prevent new users from automatically advancing to trust level 1, as they want to manually approve and promote users. Sam suggests making trust level 1 unattainable by setting high thresholds, but codinghorror warns that being locked at TL0 is restrictive and could lead to user frustration. Mittineague lists the limitations of TL0 users and asks which restrictions are problematic. Becky_Herndon explains their use case: a selective community where users must be manually approved, likening it to college applications. Cozdabuch confirms no built-in way to auto-lock new users at TL0. codinghorror reiterates the high threshold approach. supermathie proposes requiring approval for all new accounts as an alternative, while Lhc_fl notes that unapproved users can’t even log in, making it stricter than TL0. supermathie suggests using automation or webhooks to enforce TL0 locking, or modifying SSO payloads to include a trust level lock, concluding it’s a rare requirement. The thread ends by asking Becky_Herndon what solution she implemented.

Is there a setting or programmatic way lock all new users to trust level 0?

Why? We want to manually promote accounts from level 0 to 1.

All new accounts will be created via SSO. This means every user on our platform could make an account, in theory. Our mostly-private forum will be structured like an iceberg… one public announcement category everyone can see, and then all other categories will be visible only to trust levels 1+, a small subset of the platform users.

If we can’t do it programmatically, what settings can I use to keep new level 0’s from progressing to 1? (make them read 65535 minutes of posts?)

Yeah that is how I would do it, just make TL1 unattainable automatically.

Keep in mind TL0 is a very tough spot to be in permanently, your experience is heavily stunted.

Being locked at trust level 0 is quite severe. It is called a new user sandbox for a reason. I do not think this is a good solution, we will get blamed for a broken site.

Especially if they Search for info about Trust Levels and don’t think that the defaults have been upped.

@Becky_Herndon

I’m curious, which of these if removed as a limitation do you see would be a problem for you?

Users at trust level 0 cannot…

Send private messages to other users
Reply as new topic in the right gutter (UI removed)
Flag posts
Post any images
Post any attachments
Post more than 2 hyperlinks in a post
Have actual links in the 'about me' field of their profile (will be silently and temporarily converted to plain text)
Mention more than 2 users in a post

I need to edit that slightly, TL0 users can post 1 image now.

Thanks Sam I will try that.

@codinghorror , I don’t want people to blame the site, and I don’t think that will happen with our group. I can’t think of a better analogy than college applications at the moment.

submit college application > get accepted and access higher learning

Our TL0 users are applicants for a hand-picked community. We don’t want them doing anything at all on the forum until they are picked for promotion. We’ll have a post in a category they can see explaining how to apply for advancement. We will also explain things in the About section and maybe FAQ. Once accepted, we’ll promote users to TL1.

still no way to autolock all new users at TL0 is there?

Just set the trust level thresholds to reach TL1, 2 and 3 very high.

Your users will have a very bad time permanently locked in the TL0 sandbox though, it’s quite strict.

Roger that.
We just want to (with daily moderation) go through our own manual 2nd step verification process and leaving them for a few hours before one of the dozen admins (worldwide) sees them and completes the additional internal step, it is the easiest way, but if they escape TL0 within the short time before we get to them, it’s a PITA for us

Thx

似乎今天更好的做法是要求批准所有新账户?

也许我会认为它并非真正可替代。TL0 用户至少可以发言,但未获批准的用户甚至无法登录。

你说得对,这并不完全等同,但 OP 的需求相当严格:

所以今天有几种方法可以实现这一点:

  • 强制批准新用户
  • 使用 discourse-automation 将新用户锁定在 TL0(如果可能的话)
  • 使用“新用户”Webhook 触发外部事件,该事件会回调并将信任用户锁定在 TL0

以及一些需要代码更改的方法:

这似乎是一个罕见的需求。

@Becky_Herndon 你最终实现了什么?