관리자가 초대 대상이 보는 내용을 제어할 수 있도록 멤버가 초대를 설정하는 방법은?

I’d also like to see it where the admin can set what group and what post all invites made by members see, no matter who creates that invite. We have a standard topic and group that all members come into first - however because members can’t set those and there is no way for us to standardize this to what we want the admin have to create very single invite. This means members get no credit for invitees. And it’s a lot of work on the admins.

1개의 좋아요

I pulled this out into its own support topic so we can focus on it. This feels a little complicated. Maybe we can try to address your problem by breaking down what it is you are trying to achieve.

If I understand correctly, you have an invite only community and would like to allow your members to invite more people to join and get credit for inviting people, but you want to be able to control what groups invited members are added to and what topic they land on first. Is that about right?

1개의 좋아요

Yes, that is correct.

1개의 좋아요

I think only admins and moderators are able to create invites that specify groups that invitees are added to and the topic that invitees see when they first log in. Invites by regular members don’t add groups and don’t take the invitee to a specific topic.

Can you tell us some more about what you are trying to do?

  • what additional groups do all new members need to be added to, and why?
  • what is the nature of the topic you want to send new members to upon first log in? Is it not enough to pin a topic globally to make sure everyone sees it?

It would be interesting to have a setting to specify what new members see when they first log in. Right now they are just taken to “TOP”, the list of most popular topics.

We add almost all new members to a group called “Newbie Peppers”. They stay in this group for at least two weeks as they learn their way around the community. Some categories are not open to this group to see. Once they have been in the community two weeks, they can then request entrance to the second group “Seasoned Peppers”, by answering the questions and requesting to join. This is the group that sees almost everything (except a few things reserved for Admins, Mods & Level 4’s).

The topic we want all new members to see first is one we have called “Some information for Newbies”. This details the things they should do first when joining our community and provides direct links to specific other posts we want them to read, including rules, tips & tricks for navigating our platform, etc, etc. etc. It is not enough to pin the topic globally, as 1. we have found they do not find it and 2. Once they are familiar with the community they no longer need the info in that post and pinning doesn’t seem to work well for us. Discourse is very new to most of them, they feel lost and we try to ease the frustration of learning a new platform (and the same time that they are very possibly brand new to our topic too) by providing some guidance step by step so they don’t feel so overwhelmed. [Sometimes that works, other times it doesn’t - lol - but we try].

New members jumping into the list of popular topics doesn’t provide the step by step things to do and they then miss those steps.

Additionally, due to the complex nature of our topic, sometimes they will sign up, do a couple things, and then come back later to do more, completing the steps from that post over time rather than right away.

I hope this helps explain why we need the ability to control the first post and the specific group for new members. Let me know if I can explain anything more :grinning_face: .

2개의 좋아요

Nice! I love the community-specific group names. They are so cute!

Some other members here may have more ideas, but these come to mind:

You may be able to get part of the way towards what you want with Discourse Automation. For instance, you can send a PM automatically to all new members as they sign up with the step by step instructions.

You can also use automation to add people to groups, e.g. when they get a badge or complete a custom user field.

Thank you. We had thought about the PM to all new members; however we find that they don’t even find the greetings message from the bot, so we suspect they aren’t going to find the DM either. In fact that first post we want them to see explains to them about taking the Discobot training, providing them a link to directions we created on how to find the greetings message as one of the things we tell them in that first post they see.

This, by the way, is what our bot looks like, although we only use the top half since otherwise he’d be hard to see in his little circle. Gonna get around to changing his name too - just haven’t gotten there yet.

image

3개의 좋아요

해결하셨나요? #support에서 #community-building으로 이 주제를 옮기려고 합니다. 새로운 멤버들을 온보딩하는 방법에 대해 흥미로운 질문을 하고 계시기 때문이죠. 또한, 위 이 게시물에서 설명하신 접근 방식에 대해 다른 멤버들도 배워보고 싶거나 도움을 줄 수 있을 것 같습니다.

새로운 멤버들이 특정 주제를 반드시 보도록 하려는 우려를 해결하기 위해 해당 주제를 배너로 설정하는 방법도 있습니다. 배너로 설정된 주제는 모든 사용자에게 표시되며, 사용자가 더 이상 보고 싶지 않을 때 수동으로 닫을 수 있습니다.

신뢰도(trust level) 시스템과 배지를 활용하여 "Newbie peppers"와 “Seasoned peppers” 그룹을 통해 사람들을 자동으로 이동시키는 방법이 여러 가지 있을 것입니다. 또는 기존 신뢰도 레벨의 이름을 변경하고 해당 레벨의 요구 사항을 조정하는 것도 방법입니다. 다른 멤버들께서도 좋은 제안을 해 주실 수 있을 것입니다!

1개의 좋아요

No, I have not found a decent solution yet. The only work around is for me to create every single invite. Time consuming and totally wasteful. I’m still not sure why there can’t be an option to require every invite to have a specific post as the first post a person joining the community sees and a specific group for every invite created. In other words, no invites to topics or anything else except what admin chooses. I’m also unsure why members are not provided the same option as admins to adjust invites - then we could provide specific levels with instruction on creating invites and where people go for their entrance post and what group they go into. Our community has specific areas that new members are not to access until they have been in for a specific period of time and have requested to join those areas. Leaving things open by not being able to control what group they are in when they join by invite (we are an invite only community) and what post they see first is problematic for us.

Bannering doesn’t work for this. We’ve tried. 1. The banners are ignored, especially by those on mobile. 2. The first post is long and very specific as to what they should be reading and doing first in our community (with links included so they can just work through each step in the post). Much too long for a banner. With Discourse being totally new to these people, they don’t know what to do or anything, and I have learned in my many years of experience, step by step instructions increases their success. Thus, because we have these “locked” areas for lack of a better term, no one but admin can create invites. After creating almost 9000 invites, I’m a little tired of not being able to allow members to have the invite ability.

We have adjusted requirements for trust levels that advances them through the trust levels, however those are separate from the main groups - which are Newbie and Seasoned.

Perhaps someone will have a work-around, but I suspect not since it seems the ability for regular members to direct invites the way the admin want is not there and there is no ability to decide all invites go to specific places.

:grinning_face:

I will explore automation, but I’ve got so much on my plate and have not yet learned HOW to use the automation to accomplish things.

2개의 좋아요

이 주제를 올려주셔서 감사합니다. 저희 회원들에게도 비슷한 온보딩 관련 고민이 있고, 커뮤니티 구조도 유사하기 때문입니다. 다만 저희 커뮤니티는 초대 전용은 아닙니다. 하지만 디스코스가 "지인을 초대하여 함께 참여"하는 상황을 관리할 수 있기를 바랐습니다. 이 방식이 우리에게 잘 맞을지, 아니면 당신과 같은 문제에 부딪히게 될지 지켜봐야 할 것 같습니다 (문제의 전부를 100% 명확히 파악한 것은 아닙니다).

저희 커뮤니티는 초보자들이 낯설어할 매우 전문적인 주제를 다루고 있으며, 디스코스에 익숙하지 않은 비기술적 대상의 회원들이 많습니다. 또한 회원들이 몇 가지 온보딩 단계를 완료하기 전까지 커뮤니티의 일부는 접근이 차단되어 있습니다.

현재 커뮤니티는 페이스북에서 운영되고 있으며, 온보딩 관리는 각 회원별로 환영 게시글을 작성한 후 코호트(조)별로 “온보딩” 게시글을 수집하는 방식(1주 후, 6주 후, 3개월 후 등)으로 이루어지고 있습니다. 이 부분을 비공개 메시지(PM)로 관리하려고 생각했는데, 신규 회원들이 PM을 잘 찾지 못한다는 말씀이 조금은 우려됩니다!

회원분들도 이메일로 PM을 받아보시나요?

3개의 좋아요

보통 그렇지 않습니다. 이메일을 통한 답변도 허용하지 않으며, 시스템이 보내는 이메일 수를 관리해야 합니다. 회원 수가 9,000명에 육박하다 보니 이메일 서버에 과부하가 걸려 문제가 발생할 수 있습니다. 또한, 디스코urs를 처음 사용하는 사람들에게는 모바일 친화성이 높지 않습니다. 우리는 회원들에게 먼저 컴퓨터를 사용해 ‘시스템을 익히도록’ 장려합니다. 이렇게 하면 커뮤니티가 어떻게 구성되어 있는지 파악할 수 있어, 나중에 모바일로 전환하는 것이 훨씬 쉬워지기 때문입니다. 우리는 다양한 카테고리 및 하위 카테고리와 함께 분류된 방대한 자원 라이브러리를 갖추고 있습니다. 시스템 구조에 익숙해지면, 각 요소가 어디에 있는지 대략적인 개념을 알기 때문에 모바일 전환이 훨씬 수월해집니다. 하지만 불행히도 많은 사람들이 모바일만 사용하므로 어려움을 겪고 있습니다. 그러나 이는 초대 문제와는 별개의 문제입니다.

관리자가 모든 초대 링크에 대해, 관리자가 생성한 것이든 일반 멤버가 생성한 것이든 상관없이 표준화된 특정 토픽과 그룹을 요구할 수 있도록 하는 기능이 많은 커뮤니티, 특히 초대 전용 커뮤니티에서 매우 유용할 것이라 생각합니다.

저도 바로 그 말을 하려 했네요. 회원 기반의 상당 부분이 모바일 전용입니다.

어떤 테마를 사용 중이신가요? 이는 인터페이스의 "접근성"에 차이를 만들 수 있습니다.

1개의 좋아요

회원들이 탐색하고 선택할 수 있는 테마가 많이 있습니다. 기본적으로 적용되는 테마는 ‘기본’ 또는 '클래식’인 것 같습니다. 하지만 회원들이 자신에게 가장 적합한 테마를 선택할 수 있도록 다양한 테마가 설치되어 있습니다.