# Grant Custom Badge Upon Reading ToS **URL:** https://meta.discourse.org/t/grant-custom-badge-upon-reading-tos/368259 **Category:** Data & reporting **Tags:** sql-triggered-badge **Created:** [May 30, 2025, 3:10pm UTC](https://meta.discourse.org/t/grant-custom-badge-upon-reading-tos/368259 "2025-05-30T15:10:18Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger) #### Post date: [May 30, 2025, 7:37pm UTC](https://meta.discourse.org/t/grant-custom-badge-upon-reading-tos/368259/7 "2025-05-30T19:37:49Z")
> [@TempAccount](#): > > When does the “update daily” trigger run? You can speed this bit up by manually triggering `jobs::BadgeGrant` from your `/sidekiq/scheduler` page (for those with access). Mine ran 3 hours ago, but it will differ from site to site. If you didn’t mind just having them in a regular old topic you could create a new one and add the link to it to your `tos url` admin setting so it shows up in the tabs still. You could then grant a badge quite easily based on people viewing that topic (though your experiments with published pages may also bear fruit as well 🤞) I think to do it the same as the Read Guidelines one you’d need to create a plugin to replicate the behaviour for the ToS (not my forte though, so take that with a pinch of salt 🙂) > [@Heliosurge](#): > > Do you know off hand what the team did when they updated the ToS where we had to confirm we reviewed it? While not a badge was this maybe the Policy plugin? This is a [required custom field](https://meta.discourse.org/t/creating-and-configuring-custom-user-fields/113192), which I think works out quite nicely for that. Though you only say you’ve read them rather than actually reading them, so it may depend on what the main thrust of granting the badge is for. --- _[View the full topic](https://meta.discourse.org/t/grant-custom-badge-upon-reading-tos/368259)._