Show Posts
1
Feng Office 1 / Error with permissions
« on: November 16, 2008, 08:46:26 pm »
I think this is a bug.
I have 2 projects, say, "Common" and "Internal"
In "Internal" I have created some contacts, ok, then I go to "Common" and strange thing - any user from "Common" can see all contacts from "Internal".
But I didn't want them to be able to see contacts from another project!
If I downgrade permissions for user from "Common" to not be able to manage contacts, then he can't even create a contact himself, he needs to ask administrator to do that, which is not right, imho.
Thus, instead of having different, independable projects we have some projects whose content is transparent thru all tree of projects...
Another issue is that when I create a project, I need to create new user(s) who would work with it.
When I create them, every user for some unclear for me logic gets his own sub-project, like this:
user: demo, I get a new sub-project demo_personal!...
But why should a new user have his_own_subproject on default, without asking him if he needs it?
I don't have an idea...
What if I want 5-10 users to work on THIS project, and IF any of these users would ever have a need for his own project - he would then create it himself!
Sincerely, Alexandr
I have 2 projects, say, "Common" and "Internal"
In "Internal" I have created some contacts, ok, then I go to "Common" and strange thing - any user from "Common" can see all contacts from "Internal".
But I didn't want them to be able to see contacts from another project!
If I downgrade permissions for user from "Common" to not be able to manage contacts, then he can't even create a contact himself, he needs to ask administrator to do that, which is not right, imho.
Thus, instead of having different, independable projects we have some projects whose content is transparent thru all tree of projects...
Another issue is that when I create a project, I need to create new user(s) who would work with it.
When I create them, every user for some unclear for me logic gets his own sub-project, like this:
user: demo, I get a new sub-project demo_personal!...
But why should a new user have his_own_subproject on default, without asking him if he needs it?
I don't have an idea...
What if I want 5-10 users to work on THIS project, and IF any of these users would ever have a need for his own project - he would then create it himself!
Sincerely, Alexandr
...