LEP/PrivacyTransitions

Not logged in - Log In / Register

Privacy Transitions

Pages must clearly state if information is private, or will be private. Users must be informed when their actions disclose private information and may choose to cancel the action.

Contact: Curtis
On Launchpad: disclosure + ui

Rationale

This initial user testing of the disclosure UI discovered that few users can identify when pages contain private information nor do they realise when they are disclosing information to other users.

Users do not trust Launchpad or their actions. A user might try to avoid using Launchpad when working with private data, or spend additional time researching the consequences of the action they are about to take.

The existing UI that shows locks and vertical stripes does not convey that the page has private information. The list of subscribers does not clearly convey who the page is disclosed to.

Stakeholders

User stories

$STORY_NAME

As a user
I want know when the data I am submitting will be private
so that I know that I am not disclosing information.

As a project driver
I want unambiguously know that that a page is private
so that I know that I cannot disclose the information.

As a project driver
I want know when I subscribe or assign a user that I am disclosing information
so that I can choose to cancel the action.

Constraints and Requirements

Must

Nice to have

Must not

Out of scope

Subfeatures

None

Success

How will we know when we are done?

How will we measure how well we have done?

Thoughts?

None

LEP/PrivacyTransitions (last edited 2012-04-23 16:31:19 by sinzui)