_Part of Epic #12_ # Summary Organizers should have the option to enable a personal room when planning a meeting and give it a name that serves as an alias for the Meeting ID. This name changes a meeting link into a fixed address. Instead of a new ID for every occasion, a room can stand for a person or a topic - a one-on-one with a colleague, a weekly team sync, a project room. Everyone involved learns where the meeting happens and returns to the same place every time, without looking up a new invitation. And because the room is reusable, the same link works for every occurrence: ready to bookmark, pin to a chat channel, or add to an email signature. It should be possible, that the feature can be toggled on or off at any time. Switched on, the room is primarily available under the personal room name. Switched off, the room is available under its Meeting ID. # Requirement * The Organizer should be able to optionally add a Personal Room name (e.g. `awesome-room`) for a given meeting * The Personal Room name serves as an Alias for the Meeting ID * The Organizer can switch on/off the Personal Room Name Function for the Meeting. When the Personal Room is switched off, the Room remains available under the Meeting ID * When the Organizer changes the Personal Room seetings after the Meeting creation (like switching on/off or changing the personal room name) OT should send an new email to all invited participants containing the updated complete access details * The Admin should be able to set Config Options (Organizers should **not** be able to change these settings for their Meetings): 1. A Config Option to enable/disable the Personal Meeting Rooms Feature 2. A Config Option to enable/disable adding a secure code to Personal Room Urls: * If the Config Option is `ON`, the Personal Room Url is: `https://.../room/awesome-room_xhseu7gh8f4f84f8`. Use `_` as delimiter. * If the Config Option is `OFF`, the Personal Room Url is: `https://.../room/awesome-room` * Admin DB job: When the secure code config option is changed from `OFF` to `ON` we need to offer an Admin DB job for migrating the Personal Room aliases of existing Personal Rooms * Personal Room name rules: 3–40 characters, allowed characters `a-z`, `0-9`, `.`, `-` * Personal Room names must be unique # **UX / UI** * Initially the Personal Room name is auto-suggested from the Meeting Title (GitLab-style slug): lowercase, spaces → hyphens, umlauts transliterated (`ä→ae`, `ö→oe`, `ü→ue`, `ß→ss`), special characters stripped, updates live while the Organizer types the Title * As soon as the Organizer edits the name field manually, it detaches from the Title permanently (no further auto-sync, no reset option) * Field shows a live character counter (`x/40`) * Field shows inline validation feedback: "checking…" while pending, show "Available" / "Verfügbar" directly under the input field * No automatic alternative suggestion on name collision. A clear error message only, Organizer picks a different name themselves: * EN: _"This room name is already taken. Please choose a different one."_ * DE: _"Dieser Raumname ist bereits vergeben. Bitte einen anderen wählen."_ * Save with an invalid name is not possible, the input field is marked and there is a tooltip similar to a missing title with the error message from above. * After saving, the resulting link (with or without secure code suffix, depending on Admin config) is shown read-only on the confirmation/access-details screen. No explanation of _why_ a code is or isn't present, since Organizers aren't exposed to the Admin setting Functionality (not UI) see clickdummy: [personal-room-clickdummy.html](/uploads/322e3e2b618dbdcbde252875963c2fe0/personal-room-wireframe.html) Screenshots from clickdummy, page one (use exact word "weekly" for error message): {width="785" height="161"} Page two: {width="779" height="100"} # Recommendations * When the Organizer changes the Personal Room name, the previous alias link becomes invalid immediately; only the current name resolves to the room. The Meeting-ID link is unaffected and continues to work regardless of Personal Room state * Personal Room changes (on/off, name change) hook into the existing "meeting changed → notify participants" mechanism (already used for date/time changes) to trigger the updated-access-details email — no separate notification system needs to be built # Questions * **Live validation feasibility**? Can the personal room name be checked for availability on every keystroke, or is validation on save the only realistic option? Needs input from backend.