Hey, sorry for the delay on this, the acquisition has reorganized our backlog a bit, but we're interested in taking on this challenge. Hope to have some more updates soon!
Hi Dave—this is something we're really interested in, I should have some updates to share here in the next few weeks :).
Currently planning mobile apps!
Heya, we took a bit of time recently to focus on getting Google Sign-In out the door. We're going to regroup to plan out the next few weeks and Mobile is going to be a big priority.
As a quick update we have a pre-alpha build that we're able to use internally to navigate around our logins. Nothing beautiful (yet), but we have a lot of the infrastructural and backend work completed to make an app that will be useful to everyone.
I expect in the near future we'll have a much better update, and hopefully will be ready for some customer beta users shortly there after :).
Hi Valerie, no release date... yet! But we'll be looking for beta testers as we get a bit closer if you're interested in helping out.
Thanks Steven, we've noticed the same thing since when you save the login and you're not in the group that can cause some issues, we have some ideas on how to address both of these issues.
Hey, sorry for the delay—we've been focused our time on the larger, more difficult items and have been ignoring a lot of the smaller, easier changes in the process.
We've been outlining a UI redesign which we're going to get into the backlog one day (tm), in the mean time it's worth the effort to abbreviate, use groups, and front load the title with the important stuff until we get there.
We don't have any established timeline for that update, but, we'll go through and update the status of all of the related suggestions when we're ready to kick that off.
Thanks for the feedback; have definitely heard this one before :).
One thing that might help is using groups per client so you don't need to include the client name in the title, but instead can be more descriptive, especially if you have different shared accounts for staging vs production access. So instead of having a title like:
"Smith and Company Digital Ocean Production"
You might have something as simple as:
"Production Hosting" or "Production Digital Ocean"
And you can filter and search based off of company name / see what group its in.
We also have a feature request for "Tags" in here that you might want to upvote if you think that could help making identifying client accounts easier, getting the name of the client out of the title and into a tag.
This isn't something that could be done without a lot of effort; the extensions are built around having a single user to manage what you have access to and managing encryption. We'd need to build a context switcher (or some way to manage context in the app), which would probably look a lot like singing out and signing back in again.
Have you thought of adding your employer email to your business organization? That way when you log in as your employer's email, you'll also see everything for your business as well, and can do all the filtering and searching that you'd expect.
(TLDR; the product doesn't support 2 users for 1 organization, but we do support 2 (or more) organizations for 1 user.)
Hi Arash, does this export too do the trick for you: app.teampassword.com/dashboard#export_data ?
This would be a little tough since all of our encryption happens client side. If you were using a TeamPassword API, would you be OK with writing client side decryption?
That could be pretty complicated, and definitely more work than I'd expect to have to do consuming someones API, but I might be lazy! Let me know if something like that could work, or, if we could provide some value in doing a Zapier integration to hook into any non username and password scenarios (ie, login added, person added, etc.)
10-4, makes sense to me. The one area we think this could be really helpful is in doing password resets, you reset the password, update it in TeamPassword, and then hit submit, but then the site you're on gives you a validation error.
Is it just the most recent version you'd want to see, or would you want 'versions'? It seems like an anti-pattern to keep too much old information on file, but I can't think of a real reason for us not to do that (other than being confusing.)
Definitely see value here; does an Admin get to approve accounts to be deleted permanently? Where would you want to have the proverbial trash can?
Is your recommendation a duplicate of this one? https://teampassword.uservoice.com/forums/194897-general/suggestions/6989095-allow-an-admin-to-turn-on-dual-factor-for-all-user
If so I'll add your vote to that one so we fewer requests with larger numbers!
Sorry for the delay! We think tagging could be a great feature, but we want to make sure we can implement the feature in such a way that tags don't become the wild west.
We believe groups are a great way to group passwords for both authorization and organization, but we do understand that they can be too restrictive in some cases.
It'd be helpful to hear what tags you'd want to create!
When a user can't log in we need to completely remove that user's account so you can re-invite them as if they're a new user, allowing them to create a new password. You can reach out to support with the person's email to make that request.
We're working on some features now which will help alleviate this issue, but in the mean time support can help!
Hey—when you share something on TeamPassword, you encrypt the account for each team member who should have access using their public key. If you have 50 employees and you share an account with everyone, 51 encrypted entries are created (1 for everyone else, 1 for you.)
When they go to decrypt that info, they use their password to decrypt their private key, then get their copy of that encrypted info. This all happens client-side, so our servers don't have any access to the private info being shared.
In the case where a user forgets their password, and therefore can't decrypt their private key, they cant access those encrypted entries, and we can't re-create them in order to facilitate a password reset.
Hope that helps clear things up!
(Edit: this is traditional private key encryption, which you can learn more about here: https://en.wikipedia.org/wiki/Public-key_cryptography. Really cool concept if you're interested in achieving asymmetrical encryption.)
Just a quick note here on why we don't have this yet—our servers have no knowledge on the usernames and passwords you have stored in TeamPassword, so we can't take an automated approach to resetting forgotten passwords. A user's master password is their key to decrypting passwords, so we can't swap that out without re-encrypting data for them.
You can read a bit more on the topic here:
Hey Dmitry, for things like CRM accounts and Skype we'd recommend using the 'private' accounts, which aren't shared with anyone else in your company. Does that not work for you in this case?
I dropped this in the backlog—we'll test it out in staging to see if it introduces an adverse effects, otherwise I'll let you know when we launch it!
Thanks for the recommendation!
Yes—please contact support and we'll get you sorted.AdminBrian Sierakowski (Founder, TeamPassword) shared this idea ·
16 votesAdminBrian Sierakowski (Founder, TeamPassword) supported this idea ·
Do they have the same username and password?
We can currently manage this through our accounting system—reach out to let us know which email you'd like to receive your monthly receipt.
Will keep this in mind as we improve reporting to make this configurable from your settings page.
Thanks for the update Jana; we're still looking at this.
Sorry if this comes off as a silly question, but why don't you just close out of the window or use the chrome extension?
Does this happen when a user leaves the window open? The decryption happens client side, so there's no communication to the server to see if the session is active on copy. Could be!