Comment 6 for bug 1693560

Well, this may help and be vexing at the same time. The easiest way to trigger this is to be to use an incognito window and start fresh. It seems like "something" is saved in a cookie or local storage that prevents this erroneous permissions failure from popping up, but I just wiped out all stored cookies and local storage for a test machine, logged in with what's basically a Circulator account in the seed data, and this error popped right up. Now to find out why...