client/user schema
Page: 1
Recent posts in this topic
We just purchased the corporate version of aC and I'm trying to tweak for use internally. We have several departments within the company that I have defined as Clients. What we really need is this:
-Each client as its own admin/mgr that can create projects and (optionally) users for that client
-Client managers can add other client users to their projects
-Clients can't see other client projects unless they've been added to the project
Can somebody who's familiar with the codebase drop me some hints about what I would need to change to do this?
Thanks
-Each client as its own admin/mgr that can create projects and (optionally) users for that client
-Client managers can add other client users to their projects
-Clients can't see other client projects unless they've been added to the project
Can somebody who's familiar with the codebase drop me some hints about what I would need to change to do this?
Thanks
Ilija Studen
on Oct 11. 2007. 11:27 am
Hi Mike,
I don't know the structure of your company, but I would not use client companies to define departments, but roles. You can define a Sales role and give it to people from Sales department. As members of owner company they will be able to create projects, manage people etc based on permissions you give them. They can even have access to administration of you decide that they can benefit from it.
Or you really want them as completely separated units?
I don't know the structure of your company, but I would not use client companies to define departments, but roles. You can define a Sales role and give it to people from Sales department. As members of owner company they will be able to create projects, manage people etc based on permissions you give them. They can even have access to administration of you decide that they can benefit from it.
Or you really want them as completely separated units?
activeCollab team member
Thanks for the quick reply!
Here's a more detail explanation. We're a financial services company. Our main departments are Sales, Marketing, Underwriting, Finance, Operations, and Support. There are more departments, but this will serve to illustrate.
I'd like to designate someone from each dept as an admin/mgr that can create projects for that dept. It would be nice if they could create users also, but for now we can do that at the admin level. It's good if users from different departments can see each other and communicate, but they cannot be allowed to see other departments' projects. For instance, it would create business rule violations if folks from Sales could see projects in Marketing or Underwriting. The exception is if the admin from dept A added a user from dept B to a dept A project, which should be allowed.
How would you suggest we configure aC to achieve this? It's fine if we need to do some code tweaking, as long as we stay upgradeable.
Here's a more detail explanation. We're a financial services company. Our main departments are Sales, Marketing, Underwriting, Finance, Operations, and Support. There are more departments, but this will serve to illustrate.
I'd like to designate someone from each dept as an admin/mgr that can create projects for that dept. It would be nice if they could create users also, but for now we can do that at the admin level. It's good if users from different departments can see each other and communicate, but they cannot be allowed to see other departments' projects. For instance, it would create business rule violations if folks from Sales could see projects in Marketing or Underwriting. The exception is if the admin from dept A added a user from dept B to a dept A project, which should be allowed.
How would you suggest we configure aC to achieve this? It's fine if we need to do some code tweaking, as long as we stay upgradeable.
