Modifying Smart UI Header to hide Search and Add Favorite based on role

Smart UI gurus.....

Is there a means to hide in the Smart UI header the search and favourites icons based upon user's role/rights. I'm looking to hide the search option as users don't have access to the search templates, therefore the search cannot be executed anyway and I want to "force" navigation to find content. The favorite button, not so fussed. Both these should be based on user's role - i.e. if they belong to a specific group, then hide them. For reference

Additionally, is it at all possible to revoke the "Classic view" option under the user icon at top right - again, based on role or some other logic. Again, I have some users whom we want to "discourage" from reverting to the Classic UI , but others who will work between the two.

These changes need to be consistent throughout the system.

Is this at all possible and any hints on how?

Find more posts tagged with

Comments

GregPetti

I haven't seen any way to configure this with SmartView (yet) though I'm sure someone will chip in if there is a way. It would be great if Perspectives ultimately allowed some additional page control options so that you could make most of those header features conditional based on various logic conditions. It would also be good if SmartView/Perspectives supported some of the menu grooming features in a similar fashion to ActiveView (e.g. TopMenu and FunctionMenu as examples). Just putting it out there!
There are ways to do this on the client dynamically but presumably that is discouraged? What is supported is .css overrides and you could be able to use an override to hide those icons (I've not played with the override feature yet). You presumably don't want to hide the whole menu on the right hand, however, and simply hiding an option would probably require something dynamic.
One thing I could suggest (if you can't get rid of the Classic View option) is you could use ActiveView to create a request override that could be used to redirect back to smartview, or to create an error message, or simply a nice screen that tells them it isn't available.
Greg

Chris Meyer

This might solve your problem:

- Create a CSS file that hides these elements.

- Add the CSS as a document to Content Server.

- Set the document mimetype to `text/css`.

- Restrict permissions on the document to users who should have the CSS applied.

- Set the "Style" setting on the `?func=admin.smartui` page to the fetch URL of the document.

The downside is that admin users will always have access to the file, which means the style will always be applied to them. You might be able to work around this by using a WebReport (if you can get WR to serve up a `text/css` content type) and compose the CSS based on the user.

David Henshaw

Ah Chris....now that has me thinking....there is a admin setting where you can supply the path to a CSS file to use for the Smart UI. I'm already doing that to alter the "banner" and add some branding.

Wouldn't it be nice if instead you could use a WebReport that returns the CSS and implement the logic as to what CSS to use in there!!

Anyone from OT listening?

Greg Griffiths

I've been able to get a WR - using the HTML template to return a block of CSS (enclosed in <STYLE> tags) that is then picked up by the main report, so you should be able to get something similar working.

If you want to just use it as a router you could deploy two CSS files into the Support directory (user.css and admin.css) and then use the WR to write the HTML STYLE tag to point to the correct one depending on the permissions you have, perhaps even add a param so that Admin users can see with the user style on too. see WebReport\html\webreport-destination.html

if you go to ?webreports.managedestinationmediatypes you can add TEXT/CSS as an Export type and then select in the DESTINATION tab of your report.

Brett Sanders

Was anyone successful hiding the menu items via css? I'm curious what path was successful and if any example files could be shared. Thanks.

Reiner Merz

Use the navigation header widget. This can be done directly with requirejs. These are some slides from my base csui training:

Greetings

Reiner