Description of problem:

For a role (or a user who only has this role) that offers only "Promote Changesets in Environment" verb, when logging in and going to the available, default "Content Management" page, a 403 is returned.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a user called 'changesets'
2. Create a role called 'changesets role', containing user you just create and create a role which has ONLY the verb "Promote Changesets in Environment"
3. Login with user changesets.
4. Noting the two top-level tabs available (Dashboard, Content Management), click the "Content Management" tab.
  
Actual results:
User is given a permission denied - which makes sense, because user does not have access to all content management - but it is awkward.

Expected results:
Not exactly sure, some UXD consideration is required. Should user be dropped to first available subtab for which s/he has rights?

Additional info: