4 ms·
I will not speak for the parent - But in my case it is because my business uses Google apps for domains and we have accounts shared amongst various people such
by nmcfarl 13y ago
I will not speak for the parent - But in my case it is because my business uses Google apps for domains and we have accounts shared amongst various people such as the customer support. This is an account because Google required accounts (not aliases/lists/groups) to access certain resources – but it is shared because multiple people have the need to perform the function. This however results in Google trying to link that account with every support agent's personal Gmail account which gets annoying…
And this in spite of the fact that we do not have any agents actually login to read mail - we manage all of our support in zendesk.
- mortehu 13y ago> This is an account because Google required accounts (not aliases/lists/groups) to access certain resources What type of resources are these, that can't be controlled with an ACL?
- nmcfarl 13y agoGoogle Checkout is a good example, the founders and the accountant all needed access when we were using it. It's much easier to create one account we all shared - than grant access to all 3 accounts, for all things accounting related. Additionally some services - and I think Google Checkout was one - do not allow you to grant access to others at all, so if you started such an account in the accountants name, everytime a founder wanted to check out the balance, we’d need to get the accountant’s password. (Also you never know when signing up weather this will be the case for a service - thankfully I’ve not seen any new "single account" services launch for a couple of years, but I’m still wary.)
- LamaOfRuin 13y agoGoogle Checkout allows (allowed) granting access to other accounts.
- nmcfarl 13y agoCool - so not checkout, there are still plenty of google services that don't/didn't and sorting them out is not easy.