Login or Register

RSS IconRecent posts in this topic

avatar Pro
kthomas on Jun 14. 2008. 8:53 pm
Just upgraded from 1.1.0 to 1.1.2.

Our tickets now say "private" means "Only members with: Administrators, Clients, Members - HG or Project Managers roles who are involved with BCI-- New Main Site project can see this"

Good grief, I got my degree in physics, not botany !

And Clients?? Clients can now (suddenly) see my private objects-- the whole beeping reason I set objects private is so I can say things I don't want clients to see (necessarily). Clients can now see all these????!!!!!

Clients do no have an option to set see/not see private objects in their attachment to projects, so... someone tell me there is a way to turn this off :)
avatar Pro
kthomas on Jun 14. 2008. 9:00 pm
avatar Pro
kthomas on Jun 14. 2008. 9:01 pm
Fine, but those are set with no perms to see private objects. My tickets say "clients" can see private objects. Which is it??? Inquiring minds want to know...
avatar Staff
Ilija Studen on Jun 14. 2008. 10:08 pm
If you set can_see_private_objects for Client roles than they will be able to see them. This option defaults to No and can be Yes only in these two situations:

1. When upgrading all existing roles get upgraded to have can_see_private_objects.

Note that previously you could set roles ONLY to members of owner company so nothing changed.

New client roles are created for you - you are free to check: Client Company Member and Client Company Manager. Members that don't belong to your company got these roles where can_see_private_objects is set to No. System NEVER creates role named just Clients. If it exists - you created it.

2. One of the administrators set the role permissions to Yes.

That's pretty much it. Upgrade process is designed to keep access permissions same as they were in 1.0.x and makes sure that no information leaks.
activeCollab Team Member

RSS IconRecent posts in this topic