Easy way to hide top tabs in Content Explorer

We would find it useful to be able to hide the top tabs in content explorer according to role. Does anyone else?

E.g. sub editors would be able to see the publishing tab, but not workflow

This already happens - members of the Admin role can see the top tabs but not any other roles unless they are configured as such, so I cannot see the point in this poll/request.

Our Percussion consultant tells us that in some future release the Content Explorer will be used only for content, while Publishing and Workflow would be part of Workbench or Server Administrator or something like that. Yes, it would be good if sub-editors could handle publishing for their own sites but not anybody else’s, while not having access to the Workflow tab. Right now, if you get access to Publishing you also get Workflow.

That’s partly the idea, but also over-simplified.

The idea is for the Content Explorer to be main tool for “Admins” (and possibly also “Power Users”) who do “day to day” tasks that are the most complex, such as:

clone a site
change site navigation
mass move/approve items
purge items
manage/trigger publishing activities, check logs, figure out whether/if a site is “ok” or not based on it, etc.
edit/create new categories, segments, etc.

and then possibly also…
manage/change workflow settings - because this is often a “day to day” type action when the change is small enough.

The Workbench is there for “implementation” stuff that needs to go through a more formal and discrete development and testing process before being moved into production. This includes:

  • templates and content types, etc. (as in 6.x)
    and will evolve to include
  • publishing “implementation” tasks, such as defining and designing sites, edition and contentlists (run-time publishing, pub log reading, would fall into the “day to day admin” category and stay in Content Explorer)
  • possibly workflow definition (but again, there is some debate on whether Workflow is “day to day admin” or “build-test-deploy” type implementation work.)

In terms of priority, we’re much more focused on separating out “Business Users” from “Admins” and making the life of the Business User much easier. Separating Power Users from Admins, or Admins from Implementers would come later. With the direction we’re going with the Business User UI, we at least get the heaviest users who may also be the least knowledgeable out of the Content Explorer.

That is, instead of “hiding the tabs” the Business Users live in a UI where there are/were no tabs to begin with.

I realize I’m referencing things that we’ve not posted here yet, but bear with me, there will be more on this to come.

We have a similar need to hide the top level tabs. But we want to keep the users in the admin role however we do not want to give them access to any of the tabs other than content. Is there any way we can hide these tabs?