I run a small private forum for architects, but would like to add an area accessible to the public, that the architect users can monitor, where laypeople can ask questions or contribute their own perspectives to discussions that are made open to the public. The idea is that members of the public see only public discussions, while architect users see both private and public discussions. Members of the public should preferably have a different sign up experience, as there are a lot of custom fields for architect member sign ups that would not be relevant, and should have fewer options from their control panel settings (for example I don’t want to offer the public the same mail-list functionality available to architect members), and public users should not ever be be able to elevate their trust settings in such a way that private area content becomes exposed to them. I don’t want to create two completely separate forums, as this would presumably trigger the need for two domains, double costs, and add the difficulty of keeping architect user memberships synchronised between forums as they come and go. How best can I accomplish this?

Hello :wave: I think the most of these available with: groups, categories permission, custom user fields and automation. To separate users on signup use Discourse Authentication Validations chaining user fields function. So you can show separate user fields depends on what they choose on the first option ( architect or laypeople. ) After this, with Discourse Automation you can automatically add these users to the expected group. For example: User Field Option Group architect → architect laypeople → laypeople Finally set up the categories permissions for these groups. architect group can see architect and laypeople categories laypeople group can see laypeople categories Something like this maybe can help and add some idea. :slight_smile:

Thanks @Don - some great things to investigate!

Looking at the Discourse Automation plugin, for some reason there seems to be nowhere to actually nominate which group affected new users are assigned to. [The image shows a screenshot of a webpage with a title, "Automation", and several fields for inputting information, likely for creating a new automation rule on a forum. (Captioned by AI)]

You should be able to achieve what you want with the Custom Wizard Plugin 🧙 on the free tier. And your community will almost certainly qualify for the free community subscription if you do in fact need more advanced functionality. I’d approach this by: Limiting the exposed UCFs to what you want to collect from casual members Use one question to identify those who should be full architect members This UCF can then gate a joining Wizard, which can be used to put them in a specified group and ask all of the other UCFs / data that you need.

Thanks @nathank ! I will take another look. A trick in my case is there are something like 15 qualifying user characteristics (currently identified via multi-select custom user field) for access to the private forum area. For better or worse, my first thought, for simplicity, was to try and control access levels via this one multi-select field somehow. Sadly the Discourse Automation plugin at least does not seem to distinguish anything beyond a simple populated vs unpopulated state for the field in custom user fields (essentially a tick box) - I presume the same may apply for the Custom Wizard plugin? ** EDIT ** for some reason I can’t even seem to install this particular plugin Discourse Custom Wizard Plugin install failed - Support - Pavilion - will report back here once resolved ** EDIT ** now installed (a wrong path used in nano)

Here is the document how to set up: Add users to groups through custom field automation

Maybe this works for your sign up process: Discourse Authentication Validations

Thanks @Don. Do other groups (like ‘Public’ in screenshot below) behave like the predefined trust_level groups, and if so, is there a way to prevent automatic progression to increased trust levels/permissions for users based on usage? Or is it only explicitly trust level groups that behave this way? [The image depicts a screenshot of a forum page, featuring a text-based interface with a header and a table displaying various groups, with the "Leave" button prominently marked as active for the "Architects in house discussion" group. (Captioned by AI)]

You can set the Public group auto trust level. /g/group_name/manage/membership If you set it to e.g. 1, then the users in this group will be locked on Trust Level 1. It is useful if you add people automatically to this group when they signed up and they will automatically grant the TL1 (locked). Or if user already registered but under TL1 then they will also reach TL1 (locked) after add them to the group. So they cannot reach higher TLs. But this process won’t work reverse so if you add a TL1 or higher user to the group they won’t be locked on TL1. I don’t know about your site category structure but probably you can play with that too… Change trust level permissions to these added groups to ignore TL accessibilities.

Vías alternativas para inscribirse

Soporte del producto

Don 23 Octubre, 2024 05:03 9

Aquí está el documento sobre cómo configurar: Adding users to groups through custom field automation

Tema		Respuestas	Vistas
Extend Existing Controller? Development	29	2419	30 Mayo 2023
Choose groups and watched categories on signup Product Support	15	1788	5 Julio 2025
Manage group membership in Discourse with WP Discourse SSO Administrators groups , wordpress , payments , how-to	77	19103	7 Mayo 2023
Community approval of users Feature	34	3649	25 Mayo 2020
Automate sending Discourse invite emails with Zapier Integrations how-to , tasks , zapier	37	14451	3 Mayo 2024

Vías alternativas para inscribirse

Temas relacionados