On 9/15/2015 10:14 AM, Rick Larson wrote:
Thanks for your help.
Just for a little more clarification.
By "push access" I mean that 150+ users will add the details of one account to
their iPhones, Android or Windows phones, to which one address book will be pushed. No
one except one Admin will have write access. When he/she changes an address this will be
pushed immediately to all of the devices and the same changes will be reflected on their
devices.
Below you write about everyone with read access only accessing a URL to the
address book and reading it there. We were not interested in this so much but
interested in setting up an extra account in our mobile phones which will be an
additional address book to our own personal one in the phone.
Thanks again
On Sep 14, 2015, at 9:25 PM, Christian Mack <[email protected]>
wrote:
Hello
Am 14.09.2015 um 16:14 schrieb Kcir:
New here, so be patient with me if I am in the wrong place.
I have 150 people with whom I would like to share one address book, on their
mobile phones. We set up a gmail account, but with gmail's security settings
when someone logs into an account on their mobile phone in Canada, US,
Germany, South Africa, India, Australia, etc, all on the same day it locks the
system out. It believes the account has been hacked. We need to keep changing
the password all the time to make this work for a little while.
If we were to use SOGo would we be free of this problem? Would it allow us to
sign up 150+ people from 35+ counties around the globe and all freely use the
push contacts without locking us out?
By "push access" do you mean write privileges for all of your users?
If yes, they all need an account at your SOGo server.
Then you can share your address book with them and give them write access.
If no, then you can give public read only access.
This means everyone who knows the URL to the address book can access and
read it.
Access to one account is not limited in itself.
You can access it from all countries, with multiple client systems and
different clients at the same time.
Why would you give 150+ users the one login/password?
Why wouldn't you just personally administer the "shared" address book,
on a separate sogo account, and "share" it out to the 150+ people?
This way you could control for example, when one person leaves your
organization, you can suspend their account only, and not disrupt the
other 149 people!
With one shared account, you would have to reissue that one account's
password, and force 149 people change their password in their device!!!
--
[email protected]
https://inverse.ca/sogo/lists
