GO 2.07 - Adressbook - permissions not longer for contacts

[Guest]

Hi,

why have you done this in 2.07?

"-!!!WARNING!!! Removed permissions for contacts. Only permissions for the
addressbooks can be set. Contact permissions will be REMOVED with this upgrade. "

This was a great feature and at least for me it was very important.....now you have just removed this great feature without any announcement before.....hmm...for me this is hard to understand. Now i have much to reorganise to use new version 2.07.....but i am thinking about what will happen next time...which feature(s) will disabled....i do really not understand what is behind....will this feature next time available as new product which can users buy?

Regards Angelo

[Intermesh]

No all of my customers who use Group-Office had troubles with setting up permissions in the addressbook. Having multiple addressbooks with tons of contacts is not managable with permissions per contact.
I just got too many complaints about this and this was the best solution. Simplicity is the most important.
Why don't you just create a few addressbooks with different permissions?

[Guest]

Hi,

first thankx for fast answer!

Remember, we have discussed (dis)advantages of permissions for each contact early with versions 1.9x of group office.

Now it happens again that i have to create a contact in different adressbooks with all the related problems.

Because it happens often that a contact should be just visible for my department A but not for department B, but both contacts are just customers from the same company so they should be both in one adressbook...now i have to create the contact company in two adressbooks and have to insert the correspondend contact responsible in the correct adressbook.

This is just one example....there are more cases which describes how important is that feature.

And what ist the problem for your current customers which are want that this feature will not longer exist? They can create many adressbooks already if this is better for their work and must not configure permissions for each contact, because the default permissions should be the same as for the adressbook....so anyone should be happy.

A good extra feature would be just a button with action "set all permissions for all contacts in this adressbook equal to the adressbook permission".

Is there a chance that you change it back or is there no return?

Regards Angelo

[Intermesh]

Just got another complaint from a customer that was having trouble with the per contact sharing so we have definitely decided to leave that out. I'm sorry but with such a wide audiance it's difficult to keep everybody happy. I hope you'll find a workaround and keep enjoying Group-Office.

By the way, leaving this feature out also enhances speed. Especially with large addressbooks.

[djk]

What if the new version of GO just ignored permissions, rather than removing that information from the database when you upgrade from a previous version?

I currently have a problem where I upgraded a site from GO 2.05 to 2.07.
The upgrade had a problem (cant view emails - it gives an SQL duplicate error
about trying to add to the addressbook when it displays the From: of a
specific message) so I've gone back to using the 2.05 directory.

Now the problem is, users cant see the contacts in their addressbooks.
Presumably because they were deleted from the mysql database by install.php
in the 2.05->2.07 upgrade, but permissions would be required by GO 2.05
(which is what we are running until we can sort out the problem with 2.07).

[Intermesh]

Check if the columns acl_read and acl_write were removed from the table ab_contacts. That's probably the problem.

[mtech]

any way to get the permissions again in 3 version

[Intermesh]

No, we are not bringing those back. It complicates things for most users and will generate a huge acl table that is used everywhere.