Every time a user registers with an invitation link, I would like that account to only last x months and once the deadline has reached the user must renew their account, is it possible to do so? It is basically a membership with an expiration date and renewal. If this feature does not exist in Discourse, is it possible to program it through a plugin or something similar without touching the core? or is there no support in the API and webhooks for something like this?

You’d add them to a group when they joined. You’d then have a plugin that removed them from the group after the time limit was up. Just how you’d keep up with the month isn’t clear. Probably a user custom field with the end date would be the most simple.

“You’d then have a plugin that removed them from the group after the time limit was up.” which plugin? “Probably a user custom field with the end date would be the most simple.” Do I add that information during signup? Then I should use a webhook at that point, correct?

[imagen] Willy: which plugin? There is no such plugin. Someone would need to write it. [imagen] Willy: Do I add that information during signup? No. The plugin would do that. And it’s likely that there’s a way to discern when they got added via the database and data explorer, though I’m not really sure. If you’re not self hosted, or for other reason don’t want a plugin, It might also be possible to hack something together using the data explorer plugin (to get data on when they were added and hence, should be deleted) and use an automation/api tool (like zapier, though I’ve also used github actions) to remove them from the group when the time comes.

This would be a nice candidate for an automation script! Does not exist yet so you could contribute it or hire someone to do it for you and contribute it, in #marketplace.

I can do that, but with an extra feature: it should allow key-value fields to be added. The idea is that I can associate information with an invitation link with the information I want. The values can be a simple string or a JSON, and each key is a column in the database. Then, when the user finishes registering, an extra key-value pair is added, which is their username. My question is, will it pass your filters and be added to the native Discourse source code? And this leads me to an additional question, are invitation links always unique?

I slipped this topic across to #dev because we are moving out of support territory here. You need to just get going with creating the plugin or automation that does what you want. Let us know how you get on! If the features you add are more widely useful, they may be considered for inclusion eventually in core Discourse. Refer to #developer-guides and #community-wiki:developers for guidance on creating plugins. You can also start more topics in #dev to ask more questions, but I do recommend you have code to share as you do so. It is easier for others to help you if they can see what you’ve done so far. [imagen] Willy: My question is, will it pass your filters and be added to the native Discourse source code? And this leads me to an additional question, are invitation links always unique? Yes, invitation links are always unique. I don’t know what you mean by “pass your filters and be added to the native Discourse source code”. These are the types of questions I think you will be able to find out for yourself as you dig into the code.

did you ever get this idea to work?

I’ve implemented it in a plugin that I wrote to support https://www.refrunner.com/. Something like this: # frozen_string_literal: true module Jobs class RemoveExpiredFreeMonthMembers 0") .where("created_at < ?", 1.month.ago) .delete_all end end end If that’s not enough for you to solve it you can post in #marketplace and/or contact me.

Hi Willy, Yes, this is possible without modifying Discourse core files. You can use Discourse groups to manage membership access and a small custom plugin to handle expiration dates. For example, the expiration date could be stored like this: user.upsert_custom_fields( membership_expires_at: 6.months.from_now.iso8601 ) A scheduled job could then check expired memberships and remove users from the members-only group: Group.find_by(name: "members")&.remove(user) When a user renews, simply update their expiration date and add them back to the group. These are basic code examples, not a complete plugin, but they illustrate the approach. For paid memberships, you can also check the official Discourse Subscriptions plugin. Hope this helps!

[imagen] Adam_Root: A scheduled job could then check expired memberships and remove users from the members-only group: I think the idea of using a custom field and a scheduled job makes sense. Also, workflows could be used for this now. No custom plugin required.

¿Es posible establecer una fecha de caducidad para las cuentas de usuario?

Desarrollador

mcwumbly (Dave McClure) 13 Noviembre, 2026 13:14 11

Creo que la idea de usar un campo personalizado y un trabajo programado tiene sentido.

Además, los workflows podrían usarse para esto ahora.

No se requiere ningún complemento personalizado.

Tema		Respuestas	Vistas
Extending users expiry date Product Support	5	779	9 Agosto 2022
Invite only community and newsletter Product Support invites	13	1310	28 Noviembre 2023
Is there a way to set session expiration after a set length of time? Feature	23	8063	5 Abril 2017
Auto-suspend inactive users Plugin	17	5644	24 Noviembre 2019
Automatic badge expiration Product Support badges	7	1651	16 Septiembre 2023

¿Es posible establecer una fecha de caducidad para las cuentas de usuario?

Temas relacionados