I’d like to be able to connect my customer notes stored in Sheets with that customer’s profile data in my CRM. You might want to connect a Google Sheet storing a list of user-requested features to user data from your MySQL database, so you can get more context on the user behavior driving these requests. Personally, I use Google Sheets to track my marketing budget, customer notes, blog topics, partner opportunities, and growth data.īut if you’ve spent as much time in Sheets as I have, you’ve probably also run up against a key limitation: the data in your Sheet is confined to Google Sheets, and it’s hard to connect that with data in your other business systems, like a database or CRM. The flexibility of Sheets means it can do just about anything: act as a basic CRM, track finances, manage projects, analyze business data, and more. It’s an ubiquitous tool used by businesses of all stripes and sizes. If you’re anything like me, you’ve probably got a few Google Sheets tabs open right now. func = "register" ) else for ( h = 0 h < 12 h ++) t = Math. getSheetByName ( " YOUR SHEET/GRID NAME HERE " )
#Google sheets login verification
Login - returns the encrypted password/hash to the app based upon the username, for login verification Getusers - returns a list of usernames back to the app for a verification check, to avoid duplicate usernames
#Google sheets login password
Register - generates the uid, appends this and the user and encrypted password to the sheet, confirms success back to the app ( I couldn't use all the special characters (33), as some, like the comma and semi-colon, failed in the verification. On that subject, apparently, requiring an 8 character password, which must include from A-Z,a-z,0-9, and a bunch of special characters produces 350 billion combinations. I did cheat a bit and use the real password for the secret Key and the text to be encrypted, so that the user only had to enter one password, but I feel the password verification helps to make up for this. SimpleCrypto generates a different hash/encode, for the same parameters, each time you run it.Īnyway, the encryption uses two html files to handle the work, and these are on the app in the assets. The developer/owner of the sheet/script is not involved in any way in this process (unless they write blocks/script to capture the real password in another way.but they could do this with any app based login system - I suppose the next step would be to move the textboxes into an online html, but then there are probably keyloggers.). When the user wants to login, this hash/encode is called into the app from the sheet, and the "real" password is supplied in order to decode it. This then provides for a method to encrypt the password to a one time hash/encode which can be stored on the google sheet without undue concern.
I decided therefore to use encryption, provided by the javascript SimpleCrypto, which is based upon crypto.js. There is no real "back-end" server side area easily accessible within google apps script (that is no available to either the user or the developer, like you get in Firebase), apart from userProperties, but then the user needs to be connected to the web app with their google account, which starts to make things complicated ( GD Connector).
HMACSha256 would not be of any use, because the developer/owner of the script/sheet could use this to compare, without the need of the actual password. I looked at the various options available for password security, and decided that a straightforward hash - e.g. Protecting the user from the developer, and protecting the developer from themselves!
0 kommentar(er)
