Why: after #2072, answering an approval from the dashboard needs the signed-in account linked to a separate "person" record that holds authority, is the default owner or sits on the escalation path. That is a second identity model beside accounts and memberships, edited on its own page, and a fresh install can't approve anything from the dashboard until someone finds it. Who may approve is already decided by role: the shipped org policies (modules/governance/roles.go) permit approve to admin and owner. Approvers are accounts, and a channel identity (a Telegram user, say) is just another credential of an account, linked during setup.
Today: governance.people and governance.person_identities (00026) map channel identities such as telegram:1001 to people with an authority flag. approvals.verify resolves an answer through People.Verify. The dashboard path (#2072) maps the session to account:<identity id> and needs that string linked to a person on /org/people. Default owner and escalation steps name person ids. judgement/facts.go resolves an owner identity through PersonID. Accounts live in governance.identities with memberships (role per org), and governance.identity_subjects already binds an (issuer, subject) credential to an account for OIDC.
Plan
A channel identity is a credential of an account. Channel identities move into identity_subjects (issuer = the channel connector, subject = the channel's user id), the table OIDC subjects already use. One lookup resolves any answer, from the dashboard or a channel, to an account.
Role alone gates approving. The approvals module checks the account's principal against the access policies for approve on the request, exactly as every other permission is checked. Admins and owners can approve. Raising ceilings and policy, which authority gated, becomes the policy-management permission. No four-eyes rule. An org that wants a narrower set of approvers writes an access policy.
Setup path: link your channels.
First-run setup gains a step after the admin account: for each installed channel connector that can link, show "Link your Telegram" as a deep link and QR code (t.me/<bot>?start=<one-time code>).
Tapping Start sends the code to the bot. The connector emits an account.link event (like approval.answer) with the channel user id and code, and core binds that credential to the account that issued the code. The step shows "Linked as @name" live.
Codes are single-use, short-lived and bound to the issuing account.
The same step appears after a channel connector is installed later, and as "Linked accounts" on the account page.
Unlinked answers say how to fix it. A tap from an unlinked channel identity is refused as today, and the bot replies with the link to the dashboard's linking step, instead of failing silently.
Connector contract. A channel connector declares that it can link and returns the link URL for a code (Telegram knows its bot username from getMe). archipelago's Telegram connector implements it.
Default owner and escalation name accounts. They pick members, and #2094 becomes that picker.
Delete the people model.
governance.people, person_identities, /api/people, the /org/people page and org_people capability, governance.Verified, the People interfaces in approvals and judgement, AccountIdentity and the authority flag all go.
Migration: a person's channel identities are rebound to the account the person maps to unambiguously (the org's sole owner on a single-owner install). Anything ambiguous is dropped and relinked through the setup step. Default owner and escalation steps map the same way or are cleared.
The approve checks stay security-seam tests.
What stays: the fresh passkey assertion for approving an irreversible action from the dashboard (#2072), and the #2093 question for channels.
Done when: on a fresh install, the admin who finishes setup can approve from the dashboard with no further configuration. Linking Telegram in setup lets the same admin approve by tap. A member without approve is refused on both paths. Nothing in the product or API mentions people records or account: identities. Manual check: run first-run setup on an empty database, install the Telegram connector, link from the setup step, trigger a held action, approve once by tap and once from the dashboard.
**Why**: after #2072, answering an approval from the dashboard needs the signed-in account linked to a separate "person" record that holds authority, is the default owner or sits on the escalation path. That is a second identity model beside accounts and memberships, edited on its own page, and a fresh install can't approve anything from the dashboard until someone finds it. Who may approve is already decided by role: the shipped org policies (`modules/governance/roles.go`) permit `approve` to admin and owner. Approvers are accounts, and a channel identity (a Telegram user, say) is just another credential of an account, linked during setup.
**Today**: `governance.people` and `governance.person_identities` (00026) map channel identities such as `telegram:1001` to people with an `authority` flag. `approvals.verify` resolves an answer through `People.Verify`. The dashboard path (#2072) maps the session to `account:<identity id>` and needs that string linked to a person on `/org/people`. Default owner and escalation steps name person ids. `judgement/facts.go` resolves an owner identity through `PersonID`. Accounts live in `governance.identities` with `memberships` (role per org), and `governance.identity_subjects` already binds an (issuer, subject) credential to an account for OIDC.
**Plan**
1. **A channel identity is a credential of an account.** Channel identities move into `identity_subjects` (issuer = the channel connector, subject = the channel's user id), the table OIDC subjects already use. One lookup resolves any answer, from the dashboard or a channel, to an account.
2. **Role alone gates approving.** The approvals module checks the account's principal against the access policies for `approve` on the request, exactly as every other permission is checked. Admins and owners can approve. Raising ceilings and policy, which `authority` gated, becomes the policy-management permission. No four-eyes rule. An org that wants a narrower set of approvers writes an access policy.
3. **Setup path: link your channels.**
- First-run setup gains a step after the admin account: for each installed channel connector that can link, show "Link your Telegram" as a deep link and QR code (`t.me/<bot>?start=<one-time code>`).
- Tapping Start sends the code to the bot. The connector emits an `account.link` event (like `approval.answer`) with the channel user id and code, and core binds that credential to the account that issued the code. The step shows "Linked as @name" live.
- Codes are single-use, short-lived and bound to the issuing account.
- The same step appears after a channel connector is installed later, and as "Linked accounts" on the account page.
4. **Unlinked answers say how to fix it.** A tap from an unlinked channel identity is refused as today, and the bot replies with the link to the dashboard's linking step, instead of failing silently.
5. **Connector contract.** A channel connector declares that it can link and returns the link URL for a code (Telegram knows its bot username from `getMe`). archipelago's Telegram connector implements it.
6. **Default owner and escalation name accounts.** They pick members, and #2094 becomes that picker.
7. **Delete the people model.**
- `governance.people`, `person_identities`, `/api/people`, the `/org/people` page and `org_people` capability, `governance.Verified`, the `People` interfaces in approvals and judgement, `AccountIdentity` and the `authority` flag all go.
- Migration: a person's channel identities are rebound to the account the person maps to unambiguously (the org's sole owner on a single-owner install). Anything ambiguous is dropped and relinked through the setup step. Default owner and escalation steps map the same way or are cleared.
- The `approve` checks stay security-seam tests.
**What stays**: the fresh passkey assertion for approving an irreversible action from the dashboard (#2072), and the #2093 question for channels.
**Done when**: on a fresh install, the admin who finishes setup can approve from the dashboard with no further configuration. Linking Telegram in setup lets the same admin approve by tap. A member without `approve` is refused on both paths. Nothing in the product or API mentions people records or `account:` identities. Manual check: run first-run setup on an empty database, install the Telegram connector, link from the setup step, trigger a held action, approve once by tap and once from the dashboard.
sam
added the featurehigh labels 2026-11-21 11:34:00 +00:00
Landed in 02227a0b2, e127b2b05 and 970fb2ab8 (merged at e3130d53e), with archipelago 7a7c518 and 890a1b9 for Telegram linking. Approve is gated by role on both paths, channel identities are account credentials linked with single-use codes from the account page that setup opens, and the people model is gone (migration 00049). Follow-ups: #2094 picker, #2101, #2102, #2103. The manual check moves to #2096.
Landed in 02227a0b2, e127b2b05 and 970fb2ab8 (merged at e3130d53e), with archipelago 7a7c518 and 890a1b9 for Telegram linking. Approve is gated by role on both paths, channel identities are account credentials linked with single-use codes from the account page that setup opens, and the people model is gone (migration 00049). Follow-ups: #2094 picker, #2101, #2102, #2103. The manual check moves to #2096.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: after #2072, answering an approval from the dashboard needs the signed-in account linked to a separate "person" record that holds authority, is the default owner or sits on the escalation path. That is a second identity model beside accounts and memberships, edited on its own page, and a fresh install can't approve anything from the dashboard until someone finds it. Who may approve is already decided by role: the shipped org policies (
modules/governance/roles.go) permitapproveto admin and owner. Approvers are accounts, and a channel identity (a Telegram user, say) is just another credential of an account, linked during setup.Today:
governance.peopleandgovernance.person_identities(00026) map channel identities such astelegram:1001to people with anauthorityflag.approvals.verifyresolves an answer throughPeople.Verify. The dashboard path (#2072) maps the session toaccount:<identity id>and needs that string linked to a person on/org/people. Default owner and escalation steps name person ids.judgement/facts.goresolves an owner identity throughPersonID. Accounts live ingovernance.identitieswithmemberships(role per org), andgovernance.identity_subjectsalready binds an (issuer, subject) credential to an account for OIDC.Plan
identity_subjects(issuer = the channel connector, subject = the channel's user id), the table OIDC subjects already use. One lookup resolves any answer, from the dashboard or a channel, to an account.approveon the request, exactly as every other permission is checked. Admins and owners can approve. Raising ceilings and policy, whichauthoritygated, becomes the policy-management permission. No four-eyes rule. An org that wants a narrower set of approvers writes an access policy.t.me/<bot>?start=<one-time code>).account.linkevent (likeapproval.answer) with the channel user id and code, and core binds that credential to the account that issued the code. The step shows "Linked as @name" live.getMe). archipelago's Telegram connector implements it.governance.people,person_identities,/api/people, the/org/peoplepage andorg_peoplecapability,governance.Verified, thePeopleinterfaces in approvals and judgement,AccountIdentityand theauthorityflag all go.approvechecks stay security-seam tests.What stays: the fresh passkey assertion for approving an irreversible action from the dashboard (#2072), and the #2093 question for channels.
Done when: on a fresh install, the admin who finishes setup can approve from the dashboard with no further configuration. Linking Telegram in setup lets the same admin approve by tap. A member without
approveis refused on both paths. Nothing in the product or API mentions people records oraccount:identities. Manual check: run first-run setup on an empty database, install the Telegram connector, link from the setup step, trigger a held action, approve once by tap and once from the dashboard.Landed in
02227a0b2,e127b2b05and970fb2ab8(merged ate3130d53e), with archipelago 7a7c518 and 890a1b9 for Telegram linking. Approve is gated by role on both paths, channel identities are account credentials linked with single-use codes from the account page that setup opens, and the people model is gone (migration 00049). Follow-ups: #2094 picker, #2101, #2102, #2103. The manual check moves to #2096.