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; } } }

How to hide or make read only "Configuration" of each branch

ravisankar

HI All,

I am using teamsite 7.2.1, where in each branch i am having configuration,staging,editions,workareas in parallel. But in old version there is no option of configuration. so now i need to hide(or make it readonly) the "Configuration" according to client requirement. Please help me how to do that?

Thanks in advance.

Find more posts tagged with

Comments

Adam Stoller

HI All,

I am using teamsite 7.2.1, where in each branch i am having configuration,staging,editions,workareas in parallel. But in old version there is no option of configuration. so now i need to hide(or make it readonly) the "Configuration" according to client requirement. Please help me how to do that?

Thanks in advance.

I do not believe that you have the option to hide the 'configuration' piece - that's part of the product.
Also - and I haven't checked this myself - does that show up for all users or only for Master and/or Administrator users? It should only be of concern if it is the former - and then you could try taking it up with Support (but I wouldn't hold my breath expecting a solution right away)

Migrateduser

I do not believe that you have the option to hide the 'configuration' piece - that's part of the product.
Also - and I haven't checked this myself - does that show up for all users or only for Master and/or Administrator users? It should only be of concern if it is the former - and then you could try taking it up with Support (but I wouldn't hold my breath expecting a solution right away)

It shows regardless of role.

Adam Stoller

It shows regardless of role.

Hmm, yes apparently it is there regardless of role, but if you are not someone with the ability to make changes, the contents are read-only - so it's considered informational.

You need to check with Support to see if there is any supported way to hide this node within the CCPro UI - otherwise it becomes a training issue for the users to learn about what it is, and the fact that they (most of them) can / should ignore it.

ravisankar

Thanks Gothi, Taalgaard for your time.