会员使用指南 · Member guide

登录 · Sign in

Use your registered email address to request a six-digit code. Codes expire after ten minutes. The resend control shows a cooldown; delivery or rate-limit failures should be retried after the displayed message. Contact the committee if your address is not registered. Never share a login code.

After the migration cutover, sign in once on the new application address. A session from the old origin is not proof that the new origin has been accepted. If the application asks you to sign in again, complete a fresh code login rather than reusing an old tab.

入会 · Join

Open a committee invitation link, enter your details, acknowledge the privacy notice and verify your email. Your application remains pending until the relevant chapter or national administrator approves it. Existing members do not need to register again after migration.

Approval is a review step. Email verification alone does not approve an application. If an application is rejected or no longer pending, ask the reviewing committee for the next step instead of submitting duplicate records.

会员 · Members

Browse the directory, read chapter posts and events, edit your own details and RSVP. Other members' phone numbers and email addresses are restricted. RSVP means you intend to attend; it is not a checked attendance record.

属会与总会 · Administration

Chapter administrators use the partner portal for their chapter. National administrators use the platform portal. Review pending applications, manage records and archive or suspend access through the provided controls. Transfers and permission changes are recorded. A chapter transfer does not automatically grant administrator rights in the new chapter.

Suspending or archiving a linked member revokes that member's active sessions. Reactivation restores the membership status but still requires a fresh login. The last national administrator is protected from demotion or archival so that the association cannot lose its administrative control.

Changing a linked login email is handled from the verified email-change flow. It requires a recent login and a challenge sent to the new address. Editing a member profile does not change the login email.

照片与通知 · Photos and notifications

Photos require authorized access and are served through private application routes. A photo URL must refer to an uploaded application record; arbitrary remote URLs are rejected. Private file migration to the production Blob store still requires cutover verification.

Re-enable notifications on each device after moving to the new domain. A published event queues notification delivery. The delivery states distinguish provider accepted from a person reading the notification; expired device subscriptions are removed and transient failures are retried. Save your work before choosing Refresh when a new application version is available.

活动 · Events and RSVP

Administrators save an event as a draft, then publish it when the details and audience are ready. Published edits create an update notification. Cancelling an event preserves its history and sends a cancellation notification; a published event cannot be deleted. All-day events use Malaysia-midnight start and exclusive end values.

RSVP means “I intend to attend.” It is not a checked attendance record. Event visibility, chapter scope and committee-only rules are checked again when an RSVP or attendee list is requested. Viewers can read permitted events and RSVP lists but cannot RSVP. Users outside the permitted scope cannot read the event or its RSVP list.

Troubleshooting

• No login code: check the address, wait for the displayed resend cooldown, and contact the committee if the address is not registered. Production inbox receipt is still a cutover acceptance check.
• Email change rejected: sign in again so the session is fresh, use a trusted application origin, and enter the six-digit challenge before it expires. A login email already owned by another account cannot be claimed.
• Push notifications stopped: sign in on the new origin and enable push permission again on every device. Provider acceptance is recorded per device; it does not confirm that the notification was read.
• Access disappeared after a transfer or suspension: complete a fresh login after the administrator finishes the change. Chapter transfers can remove chapter-admin rights in the destination until a national administrator grants them.
• Photo unavailable: use the application photo flow and verify that you still have access to the related member or record. Private Blob migration is not yet production-verified.

Operators can find the cutover sequence, rehearsal evidence and implementation status in the repository under docs/migration/CUTOVER.md, docs/migration/REHEARSAL.md and docs/migration/IMPLEMENTATION-STATUS.md.

更新后的地址 · Addresses after migration

Members: https://app.lee-kong-si.cenvora.dev

Chapter administration: https://partner.lee-kong-si.cenvora.dev

National administration: https://platform.lee-kong-si.cenvora.dev

These are the planned cutover addresses. Confirm DNS, certificates and the deployed SHA in the cutover evidence before treating them as live.