ContributionsMost RecentMost LikesSolutionsRe: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webinar ID Reinstalling Chrome fixes problem. Sohttps://global.gotowebinar.com/join/XXX-XXX-XXX does function as it always has. May it continue! Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webinar ID Actually I think I've got browser problems. On other computer appended links work just like they always have, and after Firefox reinstall firefox is fine. Will try Chrome when I can afford to close windows! I hope this functinalty does not go away! We send registrations to a landing page with a generic join link. Great for those registering last minute. They can get in with their email address. I'll let you know what I find. Re: "HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webinar ID Thanks AshC for trying it out. So when you use the webnar ID athttps://www.gotomeeting.com/webinar/join-webinardo get a reg page using an already registered email? Or do you get a "Come Back later, webinar has not started message" And it used to be possible to join viahttps://global.gotowebinar.com/join/+ ID. Try it! It comes up with a "To join a webinar, enter the webinar ID and your email address" page but the already registered get an error. This is new. "HTTP Status 400 – Bad Request" when someone who has registered tries to join early via webinar ID I've tested this and confirmed when a registrant tries to join early (before webnar has started) using the webinar ID athttps://global.gotowebinar.com/joinor a link with ID appended iehttps://global.gotowebinar.com/join/000-000-000 if they have already registered they get an"HTTP Status 400 – Bad Request" not the page that says "webinar is scheduled to begin this date and time, come back etc" If non-registered email is used they get the (expected) reg page. I've tested 3 webinars, same result. SolvedRe: Panelists MUST be able to see attendee questions I've been asking for a level between organizer and panelist for years to do exactly what you specify. I think the "Sub-organizer" moniker already in use would be a good title since there is curretly very little difference between an orgnaizer and a sub-organizer. It is nice to have a level like "Panelist" that does not see all the questions and comments though. Keep asking!