Keeping track of customer's credentials, etc.
-
Have you looked at something like BitWarden?
-
I'm a big fan of wikis for this type of thing.
-
I thought about a wiki but that is one I have yet to try.
-
I use lastpass or Bitwarden to hold the credentials. Both have a notes section.
-
I'm all about wikis for this, too.
-
Dokuwiki or Mediawiki? I suppose this would be good on a VPS too.
-
@brandon220 said in Keeping track of customer's credentials, etc.:
Dokuwiki or Mediawiki? I suppose this would be good on a VPS too.
There is a new wiki out there now that looks really nice. https://wiki.js.org/
Haven't used it though. I've used MediaWiki in the past.
-
Things like Lastpass and Keypass work nicely - that being said a nice wiki would be also useful.
We have a good bit of documentation... in Sharepoint. but to export it if needed (if we were to leave o365) will be a small nightmare
-
If you were to use wikis, stick with one that uses a database. Dokuwiki stores your information in a plain-text files.
-
@brandon220 said in Keeping track of customer's credentials, etc.:
sult or have to keep track of info for customers such as logins, IP info, etc... I have tried many different things (spreadsheets, password managers, hand written notes) but none seem to cover all bases except general notes. Trying to get more organized. I don't need a full CRM. What tool have you found useful?
I use 1 Password since I am dealing with credentials I need to keep them encrypted. WHile documentation is on a wiki as others have noted.
-
I have 1Password on my phone and it gets used the most. Of course it is easier to type notes and documentation on a laptop....
-
Rather than place, how about format?
Does anyone have a nice template for keeping track of IP's, Passwords, Network info, etc.
I am using Google Docs right now (thinking about going WIKI) but format is the greatest issue I am having to deal with.
-
Big fans of https://keepass.info/
It improved how our department runs more than anything else we did in 2015.
Keep a master file on your file storage and everyone gets a copy on their desktop (so they can't mess up the master & always have an offline copy). Make a batch script that copies and overwrites it on their desktop and set it to run every Monday morning (or whatever is appropriate) to keep everyone updated.
-
@dbeato said in Keeping track of customer's credentials, etc.:
@brandon220 said in Keeping track of customer's credentials, etc.:
sult or have to keep track of info for customers such as logins, IP info, etc... I have tried many different things (spreadsheets, password managers, hand written notes) but none seem to cover all bases except general notes. Trying to get more organized. I don't need a full CRM. What tool have you found useful?
I use 1 Password since I am dealing with credentials I need to keep them encrypted. WHile documentation is on a wiki as others have noted.
Encryption here is a strawman. You always have access to the unencrypted password. So there is not point to saying it must be encrypted.
There is no reason that a wiki that is secured properly is not valid for something like this.
-
@brandon220 said in Keeping track of customer's credentials, etc.:
I have 1Password on my phone and it gets used the most. Of course it is easier to type notes and documentation on a laptop....
That's what makes LastPass and BitWarden awesome - full access while on a desktop to the same set of sync'ed data
-
@jaredbusch said in Keeping track of customer's credentials, etc.:
@dbeato said in Keeping track of customer's credentials, etc.:
@brandon220 said in Keeping track of customer's credentials, etc.:
sult or have to keep track of info for customers such as logins, IP info, etc... I have tried many different things (spreadsheets, password managers, hand written notes) but none seem to cover all bases except general notes. Trying to get more organized. I don't need a full CRM. What tool have you found useful?
I use 1 Password since I am dealing with credentials I need to keep them encrypted. WHile documentation is on a wiki as others have noted.
Encryption here is a strawman. You always have access to the unencrypted password. So there is not point to saying it must be encrypted.
There is no reason that a wiki that is secured properly is not valid for something like this.
key part!
-
@jaredbusch said in Keeping track of customer's credentials, etc.:
e is no reason that a wiki that is secured properly is not valid for something like this.
How does that look like in a wiki?
-
@dbeato said in Keeping track of customer's credentials, etc.:
@jaredbusch said in Keeping track of customer's credentials, etc.:
e is no reason that a wiki that is secured properly is not valid for something like this.
How does that look like in a wiki?
How does that look in O365? It's just a system that's protected by authentication access.
-
@dbeato said in Keeping track of customer's credentials, etc.:
@jaredbusch said in Keeping track of customer's credentials, etc.:
e is no reason that a wiki that is secured properly is not valid for something like this.
How does that look like in a wiki?
User ACLs and securying the platform.
-
@scottalanmiller said in Keeping track of customer's credentials, etc.:
@dbeato said in Keeping track of customer's credentials, etc.:
@jaredbusch said in Keeping track of customer's credentials, etc.:
e is no reason that a wiki that is secured properly is not valid for something like this.
How does that look like in a wiki?
User ACLs and securying the platform.
That's totally understandable, and I know where we are going on this.
