"Masking" catalog data in the frontend?

[Former Member]

What would be the best way to enable the following -

Logging into the GUI with a User ID that would display only specific records in the catalog?

If we create "masks", can we associate those to the User IDs? or Roles?

Thanks

Anshuman

[Former Member]

Awesome Tim...Thanks a lot.

That was precisely what I was looking for.

Thanks again.

Anshuman.

[Former Member]

Hey..Thanks for your response.

However, my question was a little different.

See, the Roles can be set to change/modify the "Masks" table itself...but, not to have different Masks assigned to specific Users per their Roles...I hope you are getting me.

And, yeah...I do agree that a Hierarchy is a better way to do it, but if you have a requirement to group a set of Catalog records that don't follow any (hierarchy) then what all options do you have?

Appreciate your efforts.

Anshuman.

[Former Member]

Anshuman,

You should be able to do this by selecting the Constraints and applying specific masks to the option selected for the Role. Please see the excerpt from the Console Reference Guide below. I believe this is what you are looking for. Also, what version are you running? Maybe this is a new feature of a newer release.

<i>Record constraints are selections of masks and/or other lookup table

records that allow you to create virtual subset repositories on a per role

basis. These subsets are dynamic in that they can be based not only on

masks but also on lookup values. Only main table records that fall within

the constrained record set will ever be visible or known to the role.

For the Masks table and for each lookup table that is referenced by at

least one single-valued lookup field and no multi-valued lookup fields,

you can specify constraints by selecting which masks or lookup values –

and therefore which main table records – should be visible and

accessible for the role.

For each table for which you can assign constraints, the value in the

Constraints column is as follows:

• [ALL] – table not constrained

• [n] – table constrained to include ‘n’ selected records</i>

Thanks,

Tim

[Former Member]

Anshuman,

You can set the access in the MDM Console for Roles. Under the Admin section for the Roles there is a tab to set access for Tables and Fields. Here you can set the specfic masks, categories,... that the user has Read/Write access to.

Just a thought, but using masks may not be the best way to set security as they are not dynamically updated. Maybe a better use would be to use Category, or some other hierarchy or lookup, to handle access as this would be more dynamically updated.

Thanks,

Tim