Hi! I would like the user’s subscription data to be stored in my database. A user has an active subscription if the subscription expiration time stored in the database is later than the current time. Unfortunately, the user can change the time on his computer and continue to use the subscription. How do I make it so that the time from the server is used, not the user’s computer?
Hi there, @SzymonPL… if you are that worried about a user changing the time on their computer so they can keep using their subscription, one way you could go is when a user subscribes, schedule a backend workflow to set a user’s subscription to inactive (maybe using a yes/no field) on the expiration date. True, you would then need to “manage” the scheduled workflow (i.e., cancel it and schedule a new one) if/when the user updates their subscription, but that would pretty easy to do, and it would probably be worth it to alleviate your date-related concern.
Anyway, just food for thought there, and I hope it helps.
Best…
Mike
1 Like
Thank you for your reply. Indeed, it seems that the key will be to use backend workflows.
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.