Controlling the visibility of the groups on a file/folder

I have a scenario where i have a document named "Today.doc".

There are 2 groups Group A and Group B which are having right access on that document. I want to implement a requirement when Group A members are accessing the document's properties, they should see as Group A only. Is there any way by which Group A members dont see the Group B name in the properties section and vice versa.

This is same as having BCC in the e-mails where the people in the BCC section are able to view that email but other persons cannot see them.

Any kinds of inputs are welcomed. Thanks in advance

Find more posts tagged with

Comments

ukdavo

No - you don't get this feature OOTB.

To be honest when confronted with such an unusual feature request I would tend to ask the business why this feature is required. What do they do about the permissions on their fileshares? Are they concerned that they can see other groups in filesystem ACLs?

I'm sure that you could develop a WDK customisation (e.g. extending the 'permissions' component & scope as necessary) for this but if the requirement is not business critical (e.g. a nice-to-have) then I'd probably suggest that the requirement be dropped from scope. You'll be doing them a favour by limiting the number of customisations, simplifying support and upgrades and reducing development cost.

matt-medicis

I have worked on a similar requirement in the past. Steering clear of customization is wise, but not always possible. We persuaded the business to have encoded group names so that even if Group A looks at the permissions, it would not be obvious that Group B had permissions.

We did this by having the groups named supplier_01234 rather than Apple, Dell or Pizza Hut (for late nights)

Then I believe we put the "true" name of the supplier in the Description of the group. With this, then you can have a report (Documentum Reporting Services) that would give a list of groups and descriptions so that priveledged users (employees) would be able to decipher supplier_01234.

Just a suggestion.

DCTM_Guru

If you have Taskspace, this configuration is supported out of the box. You basically build two different UIs for two different roles.

sivarry

Hi,

We had a similar requirement in past and created a new role to have Group A and Group B and assigned it to the document

-Siva