Agree, I miss this feature after moving from keepass
1 Like
I agree this basic feature is much necessary. When will it be delivered ?
Bitwarden is good to store any kind of secrets, not only passwords.
This may include ssh private keys, ssl certificates, secret tokens for azure, aws, gitlab, etc.
All those kind of secrets may expire.
To help us manage our secrets, could you add a new field of type date ?
Could you add an alert mechanism too ? Or, we would need to implement an external logic that fetches data from Bitwarden API.
2 Likes
Feature Request: Password Expiration Date Field
We request the addition of an âExpiry Dateâ field for vault entries, allowing users to mark when a password will expire or has expired. This feature is widely used in password managers like KeePass to track and manage password rotation.
Key Benefits
- Enhances security compliance for users needing periodic password changes (e.g., every 30/60/90 days).
- Provides clear visual indicators (e.g., red âXâ overlay or strike-through text) for expired passwords.
- Allows reminders and notifications before expiration to prompt password updates.
- Supports enterprise needs, where accounts must be flagged as expired when employees leave.
- Extends to other vault items, such as credit cards or sensitive documents, ensuring proactive management.
Suggested Implementation
- New Field: âExpiry Dateâ field for each vault entry.
- Visual Indicators: Expired entries show a red overlay icon or strike-through text.
- Reminders & Notifications: Users can enable alerts for approaching expiration dates.
- Bulk Management: Option to mark multiple entries as expired for streamlined enterprise use.
Community Demand
- This feature request has been actively discussed since 2018 with consistent engagement.
- Numerous users cite it as a critical need for security hygiene, enterprise compliance, and workflow automation.
- Reference: GitHub Issue #163 and Bitwarden Community Forums.
We appreciate the continuous improvements to Bitwarden and hope this feature can be prioritized in an upcoming development cycle.
4 Likes
@Alicia_Meiers Welcome to the forum, and thank you for contributing your well-reasoned argument in favor of this Feature Request. If you spend a little more time on the forum (.e.g, reading posts and comments), your forum membership level will be promoted from ânew userâ to âbasic userâ, which will give you the ability to vote for feature requests, as well.
When this new feature will be delivered ?
It is quite annoying not being able to set a password expiration date.
2 Likes
It would be great to have an update on this. Please note that some services, such as email providers may have inactivity policy and so it is handy to add this information to the specific affected logins so that users can log on to their services before their accounts are shut down.
3 Likes
I eagerly expect the arrival of this feature as the only option so far is manual calendar checking and/or put date in notes of passwords.
1 Like
@go12
Sorry for tagging you like that, I saw that you were active on this matter (Expiration date for passwords) in the past on this thread.
This feature is really important for almost all companies that are using a password manager, and from the marketing perspective, this is a big deal when they are choosing between different products.
Is there any news on when (if at all) this will be part of your product suite? Having, in my opinion,n one of the best products on the market without a feature password/secret expiration notification is really strange.
Also, KUDOS to you, Alicia, for a nice post and for giving the Bitwarden DEV team all that they need! 
I just started using Bitwarden which I think is fantastic but Iâm missing this functionality of Item Expiration badly.
Iâve been a user of SafeInCloud Password Manager for years and I do like how they have implemented it, itâs very simple and flexible.
SafeInCloud Password Manager features that could be copied âŚ
Quick filters
There is a quick filter on the left panel similar to Bitwarden (Favourites, Bin, âŚ) but is called Special and is expandable/collapsable and contains (Expired, Expiring, Archived, Templates and Recycle Bin).
Each entry also displays the number of entries inside so you can quickly glance it without clicking.
As you can guess when clicking Expired it shows all the entries that have expired. And Expiring will show all the entries that are going to expire soon, which is configurable in the Settings by picking a value from Warn cards expiring within dropdown, for example 30 days, 60 days, âŚ, never.
Default item types and custom Expiry field
There are default items like a Credit card or ID/Passport that already have expiry fields and if populated and expired or about to expire will show in the filter above.
You can also create custom fields and there is a special field type called Expiry which lets you choose/type a date and then it will work the same way as for credit cards and ID/Passports and will display under Expired/Expiring section following the same logic.
Itâs very flexible because itâs up
to you to decide what the name of the field is and you can have more than one if you want to (for example Review date, Expiry date, Follow up date, Free trial deadline, âŚ)
Also entries that have expired show a little hourglass icon in red so you can quickly see that they contain and expired date.
Itâd be great if something like this could be added.
1 Like
Surprised to see this not implimented, and even more since the original request in 2018!
since i dont seem to be able to place a vote, adding a +1 via a comment to this.
it might be worth extending this to more than just Passwords though - There are services out there that have an expiry against a config file, so i use the Secure Note option to store the config.
1 Like
Many developers and IT administrators store API tokens, SSH keys, and other credentials in Bitwarden.
These secrets often have limited lifetimes (30 days, 90 days, 1 year, etc.), but Bitwarden currently does not support tracking or reminding about their expiration.
A built-in âExpiration dateâ field with optional reminders would greatly improve security hygiene and reduce service outages caused by expired tokens.
P.S If this topic has already been discussed somewhere, please let me know. I searched for keywords, but couldnât find anything specific to this, and the feature as a whole would be relevant today.
3 Likes
@Ivan_Shilov Welcome to the forum!
You had posted in the forum section for the Bitwarden Password Manager, so I merged your post into an existing password manager feature request on the same topic.
If you actually intended to propose this feature for the Bitwarden Secrets Manager product, please clarify, so that I can move your post into the corresponding forum section.
1 Like
Note: I slightly adjusted the title of this feature request from Password (vault item) expiration date to Expiration dates for all Vault item types (including automatic reminders).
This is to reflect that not only âpasswordsâ / login items are targeted for expiration dates.
1 Like
This would be essential for Enterprise users who have shared passwords in collections. Ideally, we would also be able to do reminders to rotate the passwords when someone leaves a collection/group, so that they donât take the password with them and use it to log in after being terminated.
And that, as any other change, should (optionally) reset the expiration timer.
Furthermore we should be able to add rules for password changes like:
- At least 4 characters have to be changed
- canât be one of the last 3
I see where youâre getting with this â but both things shouldnât be a problem when the password generator is used for creating new passwords.
Hi,
It would be great feature to have reminder dates in any kind of stored items.
For example if I store to bitwarden m365 application secret and itâs 24 month secret.
It would be great to set a reminder inside bitwarden that I need to change it before it expires.
Notifications could be through mobile app push notification or browser extension.
I started using Bitwarden recently, by importing about 500 vault items from Firefoxâs password manager. I suspect many if not most Bitwarden users start this way.
The name field of most items in my vault is the full website name, which is sorted in strict alphabetical order.
This means that entries for account.foo.com and foo.com and support.foo.com and www.foo.com are not grouped together; rather they are scattered throughout the vault. This makes it difficult to find and delete duplicate entries. I have a whole lot of duplicate entries.
Can you make it so that the vault is sorted by domain, so that a.foo.com is sorted next to foo.com? It would also be okay if this were an option, enabled by default, that power users could turn off once their vault is de-duplicated and tidy.
Thanks for the feedback @Bjartmarr in the meantime, you can also check out wildcard search in the web app, desktop app, and browser extension.
Depending on your plan, you can also check the Reused Vault Health report.
When searching specific fields, you can apply the asterisk (
*) as a wildcard character for specified search values, for example:
>organizationid:*will search for all vault items that belong to an organization.>-organizationid:*will search for all vault items that do not belong to an organization.>login.username:*@gmail.comwill search for any login item username that ends in@gmail.com.>wild*: Will search for all vault items that contain the wordwildand vault items with words that containwild, for examplewildcard.
More tips here: Search your Vault | Bitwarden
Thank you for the suggestions; if I understand correctly this would require me to do a search for each organization in my vault â thatâs 500-ish searches. Which, yeah, I could do that, but itâs a lot to ask of new users. As opposed to a quick scan down the list, which is what Iâd be doing if I could sort the vault by domain.
Searching for re-used passwords will not flag identical domains with different passwords â such as when one entry has the current password and one entry has the old, outdated password that I would like to delete. And it still doesnât put the flagged entries side-by-side, so if foo.com has a re-used password, I have to scan the entire list (or do a search) to find the other entry, which might be at a.foo.com or z.foo.com or anywhere in between.
Iâve since noticed that itâs not just legacy entries; new vault entries are also created with the full hostname in the name field. So this is an ongoing vault maintenance issue, not just a problem for new users.
The root of the problem here isnât that I have duplicate entries; the root of the problem is that the Vault is sorted by hostname, which isnât useful at all; rather than by the domain, which is actually quite useful.