Make chat sign-in a single, clear step through the forge #2

New issue

Open

opened 2026-11-04 05:32:08 +00:00 by slyons · 0 comments

slyons commented

2026-11-04 05:32:08 +00:00

Owner

Problem

Joining chat is confusing for new contributors. Two pages get in the way:

Element's sign-in page at https://chat.<domain> offers a username and password form next to a Continue with platform account button. The form exists only for the break-glass @admin account, but nothing says so. "platform account" is the org name, and nothing tells people it means their forge account.
Forgejo's consent page: after the button, the forge asks whether to authorize "Matrix" to access the account. That's a second, unfamiliar decision.

The owner found this confusing on their own first sign-in, so new contributors will too.

Proposal

Signing in to chat should be one page with one option: sign in with your forge account. Nothing else to choose or understand.

Check each direction against the pinned versions (Element v1.12.33, Synapse v1.164.2, Forgejo 15.0.11) before relying on it:

Element: go straight to single sign-on instead of showing the sign-in form. Element's config.json has options for SSO redirects.
Synapse: hide password sign-in from clients, and keep @admin usable for break-glass some other way, for example through the admin API with an access token.
Forgejo: skip the consent page for this first-party client, if the pinned version supports it.
Naming: wherever a choice is still visible, name it after the forge (e.g. "git. account"), not the org.
Element desktop and mobile: check what users see there, too.

Done when: a new contributor who opens chat sees exactly one action. It takes them to the forge sign-in, or straight back if they're already signed in to the forge, and they return signed in to chat.

Design doc

Not needed.

### Problem Joining chat is confusing for new contributors. Two pages get in the way: 1. **Element's sign-in page** at `https://chat.<domain>` offers a username and password form next to a **Continue with platform account** button. The form exists only for the break-glass `@admin` account, but nothing says so. "platform account" is the org name, and nothing tells people it means their forge account. 2. **Forgejo's consent page:** after the button, the forge asks whether to authorize "Matrix" to access the account. That's a second, unfamiliar decision. The owner found this confusing on their own first sign-in, so new contributors will too. ### Proposal Signing in to chat should be **one page with one option**: sign in with your forge account. Nothing else to choose or understand. Check each direction against the pinned versions (Element v1.12.33, Synapse v1.164.2, Forgejo 15.0.11) before relying on it: - **Element:** go straight to single sign-on instead of showing the sign-in form. Element's `config.json` has options for SSO redirects. - **Synapse:** hide password sign-in from clients, and keep `@admin` usable for break-glass some other way, for example through the admin API with an access token. - **Forgejo:** skip the consent page for this first-party client, if the pinned version supports it. - **Naming:** wherever a choice is still visible, name it after the forge (e.g. "git.<domain> account"), not the org. - **Element desktop and mobile:** check what users see there, too. **Done when:** a new contributor who opens chat sees exactly one action. It takes them to the forge sign-in, or straight back if they're already signed in to the forge, and they return signed in to chat. ### Design doc Not needed.

slyons added the

labels

2026-11-04 05:32:08 +00:00