Profile and notifications

Short notification previews and direct originals

Recent material changes and historical mentions

1. Profile details and photo

1. Open the profile icon → View profile → Edit my profile.
2. Enter your name, email, phone, website and biography. Prefer an https:// website address.
3. Upload a JPG, PNG or WebP under Profile photo on the same screen. Maximum size is 1.5 MB and 16 megapixels; the saved copy is resized to 512px and location metadata is removed. No photo URL is needed.
4. Save, then check both profile and navigation images. To remove the photo, select Remove current photo and save.
5. New usernames must begin with an ASCII letter and contain only letters and digits. They are stored in lowercase; sign-in is case-insensitive. Existing usernames and URLs remain valid.

2. Optional Notion user UUID

1. Expand External account information. GitHub username and Notion user UUID optionally attribute source authorship to your research activity. They are not authentication tokens.
2. Leave the UUID blank if unknown and ask the connection administrator. Do not substitute a page ID from a page URL.
3. An administrator with permission to read user information can use the official Users API (https://developers.notion.com/reference/get-users) Find your type=person entry in results and copy only its id. Follow next_cursor when has_more is true.
4. Do not enter a bot or another person’s ID. Never paste tokens or the entire user directory into conversations or public documents.

3. Choose notification delivery

1. Profile → Notification preferences. Platform categories default to all selected. Choose chat mentions, replies, messages, mentions in materials/events, researcher assignments and participating scope updates separately. Administrator-disabled categories cannot be received.
2. Enter followed tags and press comma or Enter. Enable the followed-tag category too. New or updated readable material with these tags triggers an alert; tags never grant access.
3. Enable email and choose email categories → Save. The administrator must connect a Gmail sender. Delivery uses your profile email and includes currently readable author/title/body (up to 12,000 characters) plus direct links. Use an email account you control; open LUNA for longer content.
4. Enable browser notifications → Allow in the browser prompt. Successful device registration changes the button to Allowed and disables it. Enable PC/mobile push → Save. If permission is already allowed but Connect device push remains available, press it to complete registration.
5. Ask another participant to enter @yourusername followed by a space and a message in your channel. Check the bell and selected delivery methods. Explicit self-mentions can also test alerts; ordinary messages to yourself are not notified. Check both personal categories and administrator policy.
6. On Windows: Settings → System → Notifications → enable your browser; check Do not disturb/Focus settings. Allow lunalab-ai.com notifications in Chrome/Edge site settings. Alerts can arrive while using other tabs or programs. Delivery after completely quitting the browser depends on its background settings and OS policy.
7. Android: open the site in a supported browser such as Chrome and allow notifications. iPhone/iPad (16.4+): Safari → Share → Add to Home Screen → open the LUNA icon → sign in → Notification preferences → Allow. Ordinary Safari tabs may not offer push registration.
8. No paid SMS service or app purchase is needed. Network, power saving, focus mode and expired login can limit delivery. The platform bell retains notification history. Connect each browser/device separately; after switching accounts on a device, reconnect device push.

4. Administrator: connect a Gmail sender

1. Open Profile → Lab management → Notification policy and Gmail sender. Only platform administrators can access it.
2. Enable 2-Step Verification for the sending Google account. Create an app password for LUNA Lab at https://myaccount.google.com/apppasswords . Institutional policies or Advanced Protection may prevent this. Official guide: https://support.google.com/accounts/answer/185833
3. Enter the sender address and 16-character app password only in this settings form; enable Gmail sending. Do not use the ordinary Google password.
4. Choose Save and send a verification email to the sender, then check that Gmail inbox. For failure, check the app password, 2-Step Verification and account policies.
5. Select allowed notification categories and save. Users must separately opt in to email. Automated sending is limited to 100 attempts per day overall and 20 per recipient. Old notifications are not sent in bulk; failed or uncertain attempts are not automatically retried.
6. Changing your Google password may revoke app passwords; save a new one if needed. To disconnect, disable Gmail sending and revoke its app password in Google. No paid mail or SMS subscription is installed.

5. Choose chat notification events

1. Open Profile → Notification preferences.
2. Select new channels, new messages, mentions, replies, changes and AI response completion separately in the In-platform column. All are initially enabled.
3. For email, enable Receive email notifications, choose categories in the Email column and Save. You can keep all in-platform events but email only mentions and replies.
4. Each message uses one category, in priority order: mention, reply, general message. Disabling that category suppresses it. Ordinary messages you send do not notify you, but explicit self-mentions do. Creating a channel notifies current participants.
5. Open a bell notification to reach the message or conversation. Email includes currently authorized notification content and a direct link. Sending requires the configured sender and is subject to daily limits. Old notifications are not sent retroactively.
6. Losing channel access stops new notifications. Only the owner receives private AI response notifications.

6. Clear your inbox

1. Open Notifications, select the checkboxes beside items and choose Delete selected. Select this page selects the currently displayed items, up to 20.
2. Clear all notifications removes existing notifications across all pages after confirmation. Notifications arriving after you opened this screen are preserved.
3. Cleared notifications disappear from your inbox, bell count and direct links; pending email deliveries are cancelled. Mail already sending or sent cannot be recalled. Linked messages, materials and other recipients’ notifications remain intact. Server processing history is retained to prevent duplicate delivery.
4. While the site is open, the unread bell count refreshes normally every 30 seconds while the page is active, and after sending a conversation message.

7. When a Windows banner is missing

1. In Notification preferences, enable PC/mobile push and desired categories → Save.
2. Press Connect / check device push and confirm Connected. This confirms device/provider registration, not that you have seen an OS banner.
3. Press Test notification. It requests a banner on this device and sends no message or email to anyone else.
4. If invisible: Windows Settings → System → Notifications → Google Chrome or Microsoft Edge → enable notification banners and notification center. Turn off Do not disturb and Focus, and allow notifications for lunalab-ai.com in browser site settings.
5. Verify with a new mention. An open LUNA page also shows a bottom-right notification card and checks periodically while active. Errors or rate limits increase the retry interval, so immediate display is not guaranteed. Provider acceptance does not prove Windows displayed a banner. LUNA cannot override OS focus or power-saving restrictions.

8. Connection state after testing

15. Read notifications without leaving your page

Notification language and free translation

Preventing repeated external-material alerts

Enable device notifications for conversations

1. An automatic guidance card appears on signed-in pages when device notification permission is missing. Click Enable notifications, then Allow in Chrome. If Chrome uses a quiet prompt, check the notification icon in the address bar.
2. After permission is granted, the app connects this device and enables your device notification preference. Existing category opt-outs and digest choices remain unchanged. For immediate conversations, enable Platform and clear Digest in Chat and comments, then save.
3. If already blocked, the site cannot force another permission prompt. Open site information to the left of the Chrome address bar → Site settings → Notifications and allow them, then return. Use Connect device push in notification preferences if needed.
4. Later dismisses the card for the current tab session. Notification preferences always offers the relevant guidance. On unsupported iPhone/iPad browsers, add the site to your Home Screen with Safari and allow notifications in the web app.
5. Permission alone does not guarantee an OS banner. Use the device test button and check OS notification banners, Do not disturb and conversation notification settings.

8. Separate digests from immediate alerts

1. Choose delivery channels per category in Notification preferences. Expand a group, change the needed categories and save.
2. Select a digest interval of 15 minutes, one, three or twelve hours, or daily. Immediate delivery does not wait for a digest.
3. Select categories to batch, such as source changes. Leave time-sensitive chat categories unselected so they remain immediate.
4. Configure GitHub deadline lead times and Seoul reference time separately. These use collected due dates for unfinished work assigned to you.
5. Expand administrator-restricted categories and device/Windows guidance only when needed. The count refers to categories. Required in-app support alerts are exempt, and administrators can follow the policy link to adjust restrictions. Test and device-permission/connection controls remain separately available.

9. Choose social, Timebank and approval alerts

1. Enable researcher-follow alerts for new followers and magazine-selection alerts when you are featured.
2. Enable discussion likes and comment/thread follow categories to receive reactions to your discussions.
3. Timebank covers credits to your account, administrator credit requests and changes to other researchers' accounts. Follow the Timebank chapter for transactions.
4. Join and metadata approval requests reach currently authorized reviewers. New support inquiries alert administrators and resolution alerts the author immediately in-platform; email/push still follow channel consent.
5. If nothing arrives, check overall channel switches, digest selection, administrator policy and current access. Enabling a category does not replay every historical event.

10. Select, mark read and inspect details

1. Select several notifications or select the current page.
2. Use Mark selected read or Delete selected. Source documents, comments and tasks are not deleted.
3. Expand details only for the item you need and use its source links. Device banners omit long details.
4. Email may include readable details and navigation links. Actual new-window behavior depends on the mail client and browser.

Compact deadline reminder selection

1. In notification preferences, open GitHub deadline reminders and click the reminder-time box. It normally shows only your selected times.
2. Check or clear multiple times. The summary updates immediately. Click again or press Escape to close it.
3. Save at the bottom of the page.

Test device push

1. Open notification settings on the PC or mobile device you will use and connect device push. On iPhone/iPad, open the Home Screen web app added through Safari.
2. Send a test notification. The server targets this device only and waits about 15 seconds for receipt and an OS display request. This does not prove a banner was visible.
3. If receipt succeeds without a banner, expand device help. Check Chrome banners and notification center in Windows Settings, including automatic Do not disturb rules. On Android, check browser/site notifications. On iPhone/iPad, check web-app notifications and Focus.
4. Test local display only bypasses the server. If the subscription expired, test again to reconnect. Wait 20 seconds between tests.
5. For immediate chat alerts, enable device push and chat categories, clear their Digest boxes and save.

Delayed collection and source-change digests

1. First collection time is different from the source's actual creation/modification time. External material older than the previous digest is excluded from new-source digests.
2. Sources without dates retain observation-based behavior and may include older material. Missing dates do not prove freshness.
3. No empty digest is sent when no new items qualify. Existing notification history remains.
4. Inspect accessible items in Notifications independently of push/browser status. Polling backs off after temporary errors, so updates may be delayed.