# Event-page and registration access test card

Use this English card with an authorized test visitor and a logged-out browser. Keep any real password out of the card. The event page, registration form, and ticket types may have separate controls.

| Approved access boundary | Decision / owner |
| --- | --- |
| Should the event appear in provider listings? | |
| May anyone with the direct URL view the page? | |
| Is a password required to view the page? | |
| Is a separate password required to submit registration? | |
| Are ticket-type codes or approval rules configured separately? | |
| What support route stays reachable without page access? | |

| Logged-out visitor test | Expected at this provider | Observed | Issue owner |
| --- | --- | --- | --- |
| Direct URL, no password | | | |
| Direct URL, wrong page password | | | |
| Direct URL, correct page password | | | |
| Registration attempt without required form password | | | |
| Registration attempt with correct form password | | | |
| Support/contact route without access | | | |
| Previously shared link, after any access change | | | |

- [ ] The recorded listing, page-view and registration outcomes match the approved boundaries.
- [ ] Invitations and shared passwords are not described as identity verification.
- [ ] The instructions sent to visitors name the right link and the actual control they will encounter.
- [ ] Ticket issuance and admission are checked in their own workflow.
- [ ] A named owner will repeat these tests when the settings or link changes.

Provider references: [EventCreate website and registration access settings](https://support.eventcreate.com/en/articles/1638080-how-to-make-your-event-website-private-or-password-protected), [Humanitix public/private event visibility](https://help.humanitix.com/en/articles/8950908-what-is-the-difference-between-a-public-and-private-event), and [EventRegist event-page password](https://support.eventregist.com/en/knowledge/password-protected). Follow only the controls your provider offers.