nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

disabling custom menu item | for users.

sivaramiyer

can I disable custom menu items for a set of users? [not for roles]
TS 6.1sp1 /solaris

thanks,
Sivaram./

Find more posts tagged with

Comments

ISCBorisB

can I disable custom menu items for a set of users? [not for roles]
TS 6.1sp1 /solaris

thanks,
Sivaram./

No, not in 6.1 or even 6.5. You can in 6.7.x. Regardless of the version you can of course code custom validation
within the code itself and render back some "You are not authorized to use this Service..." Error page

kaalraa

can I disable custom menu items for a set of users? [not for roles]
TS 6.1sp1 /solaris

thanks,
Sivaram./

The straight answer would be 'No'.

When we were at TS 6.1, we used to check the authencity of the user within our script which executes through user menu item.

HTH

kaalraa

No, not in 6.1 or even 6.5. You can in 6.7.x. Regardless of the version you can of course code custom validation
within the code itself and render back some "You are not authorized to use this Service..." Error page

Boris,

Are you sure that you can disable custom menu items for users (not roles)? What i had seen through admin tab, it works specific to a role.

Please confirm. Thanks.

ISCBorisB

Boris,

Are you sure that you can disable custom menu items for users (not roles)? What i had seen through admin tab, it works specific to a role.

Please confirm. Thanks.

It is done by roles, correct. As you undoubtedly know, starting with 6.7 you can make an arbitrary number of roles per Branch.

Menu access credentials are normally "grouped" (for the lack of better term), you practically never have it really on account per
account basis. So, custom menu access rights become just another factor in the roles creation and roles access right allocation.

kaalraa

It is done by roles, correct. As you undoubtedly know, starting with 6.7 you can make an arbitrary number of roles per Branch.

Menu access credentials are normally "grouped" (for the lack of better term), you practically never have it really on account per
account basis. So, custom menu access rights become just another factor in the roles creation and roles access right allocation.

Yes, thats correct. If you are starting out an application, you [should/must] take the factor in account, however for any running application it is very difficult to attain the requirement.

Thanks Boris for the clarification.