Comment 1 for bug 232454

Matsubara, This isn't quite the same scenario as reported but it's related to the same problem.

The way I reproduced it is to:
1. Log in as an admin
2. Set the registrant to any non-admin
3. Go to http://launchpad.dev/ubuntu/+edit and make sure "uses blueprints" is checked.
4. Log in as the non-admin user from step 2.
5. Go to http://launchpad.dev/ubuntu/+edit
 -> You'll be redirected to the login page.

Hence the original description of total inaccessibility is correct, rather than just not being able to edit :-)