----- Forwarded by Dan Chamberlain/IT/VANCPOWER on 04/07/2005 08:09 AM
-----
Dan Chamberlain
To: "david natas" <natasdavid at hotmail.com>
04/07/2005 08:01 cc:
AM Subject: Re: [Sigia-l] Designing a site with restricted content(Document link:
Dan Chamberlain)
We hide any restricted data/content until login is complete. This prevents
user frustration and clearly addresses all legal/regulatory concerns.
Dan Chamberlain
Sr. Systems Architect
Dominion Resources
www.dom.com
"david natas"
<natasdavid at hotma To: sigia-l at asis.org
il.com> cc:
Sent by: Subject: [Sigia-l] Designing a site with restricted content
sigia-l-bounces at a
sis.org
04/07/2005 07:48
AM
Does anyone have any thoughts about the best design strategy for a content
managed website where much of the content is restricted depending on the
type of login a particular user has?
Should all restricted content be hidden until an appropriate login is used?
Or should all items be visible to all users, but with a login page between
selecting the link and viewing the actual content?
any thoughts or links to relevant information/research/case studies would
be
greatly appreciated.
------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l