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 a feature in GUI denies to run the CLT.

System

If we disable any feature to any particular user in the GUI, Then reasonably he is not able to run that corresponding CLT. For example :

If we disable an unlock feature to an author in GUI then he is not able to run the CLT command iwunlock.

Is there any possible workaround for this author to run the CLT command but still he should not have access in GUI.

Any ideas on this ?

UD....

Find more posts tagged with

Comments

Adam Stoller

If we disable any feature to any particular user in the GUI, Then reasonably he is not able to run that corresponding CLT. For example :

If we disable an unlock feature to an author in GUI then he is not able to run the CLT command iwunlock.

Is there any possible workaround for this author to run the CLT command but still he should not have access in GUI.

Any ideas on this ?

UD....

What do you mean by "disable ... feature [for] ... user in the GUI"?
If you mean you customize the GUI as per the UICG - it has no effect on CLTs and thus you should not have any problem.

However, certain CLTs require certain OS or TS role privileges to be able to run and/or to perform activities within TeamSite depending on what is being acted on.

Migrateduser

Actually I was talking about the disable in the administrator tab.It disables the feature from GUI but simultaneously it disables the CLT operation as well.

Adam Stoller

Actually I was talking about the disable in the administrator tab.It disables the feature from GUI but simultaneously it disables the CLT operation as well.

What version of TS?
What OS?

Migrateduser

TS 6.7.1 , OS - windows 2003 sp1

Adam Stoller

TS 6.7.1 , OS - windows 2003 sp1

I'm not aware of any such functionality in TS that prevents CLT usage based on options selected within the GUI. Perhaps this is something new in 6.7.1? (I currently do not have access to a server to look at it).

You might try contacting support if nobody else here can provide insight.

nipper

I'm not aware of any such functionality in TS that prevents CLT usage based on options selected within the GUI. Perhaps this is something new in 6.7.1?

While I do not have any more detail than Adam, I would not be surprised to see functionality like this get implemented. IWOV has already done similar with the OpenDeploy, requiring commandline users to have OD defined permissions.

GriffTheDog

Why?

Could you not make a special role just for this user. So the rest of the authors can't run the cmd, but this user(s) can.

Migrateduser

No we Wanted Authors to run this