I want to be able to assign users to a category (E.g. Company), and then have another user that is able to view information related to users in just that category, but not others.

For example, I might have these users.

Name | Department
Jane Smith | ABC Widgets
Joe Bloggs | ABC Widgets
Bob Roberts | ABC Widgets
John Doe | Acme Solutions

So I then want to make Bob Roberts somehow able to see a list of users that are in the same company as himself, but not other companies.

Ideally, I'd like to be able to free-tag users with taxonomy terms, and then access those tags within Views to output a list of users with the same term as the currently logged in user. As far as I can see, none of the modules that facilitate user tagging are stable for Drupal 6.

Any suggestions as to the best way of achieving this would be greatly appreciated.

Comments

balserodeluxe’s picture

I have the very same requirement. If I find something, will post it here also...

balserodeluxe’s picture

Evaluating:

User Terms
TACL
TAC
Organic Groups

Organizational Infrastructure looked particularly promising, but when I install it on Drupal 6, one of the "Required" parameters (Entity Type) shows a blank dropdown, so I couldn't even test it!

caschbre’s picture

One option that I've used in the past is to work with the organic groups module. I then created a view that lists all members of a group and added whatever fields I wanted to display. Set the view to only be visible by members of the group.

This might be overkill simply for displaying users by department but groups provides the access control. I also needed additional group functionality so it worked for my use case.

leo pitt’s picture

Thanks, I'll have to check out Organic Groups.

I did read the documentation but to be honest found it a little bit unclear as to how it actually works.

caschbre’s picture

Organic Groups is an access control module. It can be configured that only members of a group can see content posted within that group. It also can list all members of that group.

So in your situation you'd probably create a new content type called "department" and make it act as a group.

ullascs’s picture

@ leopitt :

Thanks for introducing this topic here.

Were you able to get a different solution or went ahead with OG?