set a expiry alert - how is this supposed to work?

Thanks for flagging this to us! I'm seeing the same behavior on my end here too. Setting the purchase date to today, and then selecting any alert schedule option other than "On date..." sets the expiry window to a past date, not a future date like it should.



Will definitely be filing an issue with our development team to get this corrected. For now, you can use the custom date option to pick a future date that works for you! 😅

I find this unintuitive too. I don't even want to put in a date other than the notification. If I have to have two dates, it'd be nice to be have date I obtained card, membership etc, second date for notification about expiration date. I cannot do that with existing logic.

I don't know what the team was thinking with the current date logic. Why force us to have two dates when one can do?

It'd be great to have an object just for expiration date which triggers a notification day of (be nice to have optional time too); and a generic date object that we can title whatever and is just informational.

I done a quick search on the site to see if anyone else had complained about the strange ‘expiry alert’ feature and this is the first post that popped up, so forgive me if this has been discussed at length and answered in another post.

I’m here to agree that this is a completely unintuitive feature. I wish to use it solely for software licences / subscriptions which expire in X amount of time from my purchase date - which the labelling seems to indicate is the intended function.

Why can I only mark items with a past date and not a future date - it makes zero sense to set an expiry date prior to the ‘purchase date’ and immediately flag my new 6 months access licence as ‘expired’.

I want to set a date in the future when the my current licence expires but I can’t even do than manually as future dates are greyed out in the calendar and manually typing a future date into the field also does not work as I am unable to ‘enter’ the typed date.

Images below are for a Software Licence under the ‘Order’ section...

Yes, there are workarounds for this...renaming the ‘purchase date’ field to ‘renewal date’, for example. But the original post is 1 year old now and this unfortunate naming / behaviour still remains. Will 1password ever make this work correctly, and if it already works as expected, will the team ever correct the poor naming conventions used to make more sense and indicate their intention?

I can accept that I may be a complete moron and not understand how this feature is supposed to work as-is, and if that’s the case, could someone please explain? But as this point in time, this function in the capacity I understand it & wish to use it, just seems completely broken.

Hi all, thanks for the feedback here!

I can definitely understand how this feature is confusing and unintuitive in its current state. I’ve filed your feedback with the team for future consideration.