PDA

View Full Version : Use dotProject with clients, internals and externals


toast
04-04-07, 06:30 PM
We want to run a system which allows us to manage our clients, our freelancer's and our work. Of course everybody should be allowed to see only what we want him/her to see (e.g. one client isn't allowed to see our other clients or the freelancers)

I wanted to solve this by using roles "Intern" (we), "Extern" (freelancers) and "Client". I tried a lot the past four days and read a lot of the posts (including pedroa's "hacks" in the sourcecode), but neither something fitted 100% (about 50%-70%), nor I learned enough to solve the problem on my own. I hate it to let others do my work, so I'll be happy for some suggestions or pushes into the right direction (eastern is the time of hope ;) isn't it?).

ADMIN
the only one who can make changes in user- and system-management, can do everything of course

INTERN
can see companies, project, tasks, calendar, files, forum, ticketsystem

EXTERN
can see the projects and tasks he is assigned to, can make changes in "his" tasks (like changing the status), can upload and download files (download only "his" files), not allowed to see contacts or companies he isn't working with, no forums, no ticketsystem

CLIENT
allowed to see his/her project and tasks, no contacts, not the other clients (this role is working right now nearly perfectly, but sometimes there is a dropdownmenu which contains all users -- I commented it out in the php-source), can see only the interns, not the freelancers.

Does anyone have a suggestion for my role-management. Does anyone run dotProject with a configuration like this? Is some of this absolutly impossible? Thanks for everything.

MacOfTheEast
04-04-07, 09:10 PM
I will just give you a hint which might help you to achieve what you are trying to do. The permission system is based on a users' access to COMPANIES. It all starts there. i.e., give intern access to ALL companies, external access to only their company. Rebuild your role structure based on this information. It is true that some pulldowns "break" the basic permissions structure and will need a bit of tweaking however usually, even though something appears in a dropdown list, the user will be prevented from accessing the option if he doesn't have the proper rights.

MOTE