User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am creating an information architecture map for a site I am working on. 90% of the site is visible to all on the Internet, but the 10% is available for users, based on their role.

My question is whats the best way to represent this? Currently I have all the IA in one map, and have colour coded the pages for "group A", "group B" so on.

Is this a usual way, or is there a better approach?

share|improve this question
I'm glad you found a good answer, but you don't need to accept the first answer you get. If you leave it for 24 hours you'll probably get more answers, possibly even better / more suitable ones. Accepting an anwser so quickly may deter other people answering. – JonW Jun 27 '12 at 16:19
True I suppose. Anything by Jessie James Garret gets my vote for a good answer. :) I've removed the good answer (sorry dhmholley) to see if anyone else answers. But it was good for me. – Bernard Tyers Jun 27 '12 at 17:02
up vote 7 down vote accepted

Jesse James Garrett's Visual Vocabulary for IA has the concept of a "conditional area", represented by a dotted line grouping the elements.

The example he gives is the following:

enter image description here

In your example, you'd have the condition based on their role and throw some sort of error when the user tries to access a page outside of their role.

share|improve this answer
Excellent! Thanks very much for the link. I had sorta used a similar approach (shaded background container), but didn't think about the security error branch.. – Bernard Tyers Jun 27 '12 at 15:52

A simple icon, such as a keyhole lock, that can show the page is locked (and therefore unlockable with the correct key), is a good way of identifying which pages are behind the login or firewall. Using a dotted line pointing away from the lock to an error page/box, along with other lines that connect the page to represent typical navigation, should be make sense.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.