Comment 2 for bug 690608

This causes some confusion for users after being granted access to a private PPA, it's not obvious from this page that they need to also opt-in to the grant before gaining access to the password.

In particular, if instead of clicking on 'View' for the private ppa tokens, they click on the Team that owns the private PPA and then from the team page go to the PPA's page, they will see under Technical Details an apt line for the private PPA which does not show the credentialed URL link, nor gives any indication that they need to confirm access. They then copy that apt line into their apt sources but then get an error

  "Failed to fetch ... 401 Unauthorized"

The following proposed UI design would address this problem, by adding 'Confirm' links in place of some of the 'View' links:

    https://help.launchpad.net/Packaging/InstallingFromAPrivatePPA

Further, to address the secondary issue of the missing credentials on the PPA page, it would be helpful if instead of displaying the Technical Details dropdown link, to instead display a link to the credentials confirmation page.

With those two changes I think the UX problem would be sorted.