Security On Standard Forms With Customized Tab

(0) Share

Report

Posted on by Community Member

Hello everyone,

Currently I am working on security roles part. I need some inputs for my current requirement. We have added one customized tab in Parameters form(ProjParameter form). This tab has some parameters which we need to show to only some role. Lets say, data manager. This role also has access on customized master forms.

Issue here is we need to hide other tabs except this customized tab on parameter form. User should not allowed to change other details of project parameter form. (So make it invisible)

As per my current development I can manage only my tab which I can hide/ show based on privilege.

1. Do I need to add privilege to standard tab as well to hide/show based upon role? If yes then will it impact on other roles where system has already assigned this form?

2. Can this requirement be achieved based upon what current situation is? If yes then can anyone guide on approach?

3. Is there any alternate approach for same? One approach is suggested to create duplicate form and set access to that form, is it proper way to go ahead?

Thanks in advance.

Regards,

Smit Patel

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

Like (0)

Report

Hi Smit,

You can set the neededpermission property to Manual for all standard tab pages, but I'm not sure if this would be possible using extension. (Haven't tried yet). Then on privileges you can override form controls to give access where needed.

Another approach is creating a second form with your settings only. You don't have to duplicate it as in my opinion. The access for standard parameters and the new fields are separated. Or did I miss something from your explanation?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Andre,

Thanks for your reply.

On first approach if I make neededpermission property to 'manual' instead of 'none' to standard tabs then it will not affect any other roles. Please correct me if I am wrong. If yes then I will use same.

In second approach you are correct. Both are already separated. So instead of duplicating forms and hiding tabs, I will add only my tab so that no burden of standard tabs.

Regards,

Smit Patel

Was this reply helpful? Yes No
Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report

Can't you simply grant no permissions to read the fields (which will cause them to disappear from forms) instead of manipulating form controls such as tabs? I believe your goal actually is restricting access to field, regardless of where they're displayed.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Martin,

Thanks for your reply.

My goal is to hide standard tabs. If that is not possible at all or taking complex customization then alternate approach is to disable access to standard fields. Only customized fields will be accessible.

I tried to implement the way you are suggesting but I am not getting if I give Read on projparameter datasource then it is not allowing my standard fields with update access. How to override same? If I grant No access on datasource and give Update on custom fields then it is showing but not allowing me to edit.

Regards,

Smit

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

If I give manual access to each tab and set security for my particular role then will it impact all other roles like Project Manager where already permissions are there. i hope I need not to change it for other standard tabs.

Regards,

Smit

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report

Aha, my u8nderstanding of "User should not allowed to change other details of project parameter form", was that you don't want to allow users to change those fields. If you merely hide the tab, users still may be able to change those fields (by using another form, adding the field through personalization, using Excel add-in). It's still suspect that you've chosen a technical solution that doesn't meet the actual business requirement.

Of course, setting removing permissions for whole table is wrong, if your goal is configure permissions for individual fields.

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,020 Super User 2025 Season 2 on at

Like (0)

Report

Setting the neededpermission for the tab controls indeed affects the existing roles and will not restrict access to fields.

So it would be better to use table/fields permissions like Martin mentioned. Or like mentioned earlier: use a second form with only your new fields.

Was this reply helpful? Yes No