| Key: |
CHD-1002
|
| Type: |
New Feature
|
| Status: |
Open
|
| Assignee: |
Unassigned
|
| Reporter: |
Daniel Barr
|
| Votes: |
1
|
| Watchers: |
2
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
| Value: |
2 - Significant Value
|
In reference to this thread http://forum.cerb4.com/showthread.php?t=1591
The ability to allow a worker permissions to only certain buckets within a group (or even create subgroups for a group, and then buckets in that sub group...either would be fine) would be a nice addition.
Dan mentioned at the end of the thread that "but our philosophy has always been more one of trusting the Workers rather than not, so I can't say whether it would ever get implemented or not."
I'd just like to point out that I thought of this more as an increased ability to assign 'jobs' to my workers rather than not trusting them.
For a helpdesk that includes multiple websites, it would be more streamlined to have a 'Support' group, and then have sub-groups for each website in that group (with the ability to add default reply to emails, signatures, etc).
In my personal situation, I have (currently) 8 websites to provide support to. It would make it a bit more streamlined if I could just go to the support group, and then the website....rather than looking through a list of 8 (actually 32 since there is billing, sales, and contact too) groups for the one I want.
|
|
I do agree that sub-groups would streamline things if you want to group by role (Support/Sales) and then sub-group products, opposed to grouping by product with sub-groups as roles. Allowing groups to have a parent group, which is really just an organizational tip, should be fairly easy.
We'll have to experiment with it to make sure it "feels" right, but I'll add this to the roadmap.
|
|
Sub-Group (or bucket) worker permissions