{"id":"3784a008-930a-4952-b460-23d971de3801","org_id":"5b607c7a-3ba2-4077-b038-cdccd0ce7c34","project_id":"b18679c0-fffb-4308-82b6-9e91be23582f","parent_id":null,"identifier":"BEB-9283","number":9283,"title":"TEAM IN SUITE — the wpapps team joins by one-button OAuth connect, same pattern CC built for Cloudflare","description":"Repo: alexrollin/abilifi-apps\nClass: CODE\nLane: part\nFEATURE NAME: **TEAM IN SUITE**\n\nAlex 2026-09-05: the case is the wpapps team, not the buurt. The team is busy 24/7 and the work is FRACTURED because they are not in the suite. Fix it now.\n\n## The fracture, measured today\n- list_users on the tracker returns ONE user: Ankit Jani, ankit+vr@wpapps.press, and he sits in org e4b1c744, not in the Bebond org (5b607c7a) where all 9000+ tickets live.\n- So the team is working outside the tracker, outside BB Docs and outside Orky. Nothing they do is visible where the rest of the work is, and nothing we file reaches them.\n- That is the whole fracture. It is an access problem, not a tooling problem.\n\n## Mechanism — the same one CC already built\nOne-button OAuth connect, exactly what CC did for Cloudflare. Alex never fetches a token, never walks a dashboard, never hand-creates an account. A team member clicks connect and is in.\n\n1. Reuse the CF OAuth connect pattern for team join. CC builds the app side; the person clicks once.\n2. On connect: the person gets their handle in the tenant namespace, a tracker seat in the Bebond org, BB Docs access and Orky chat. One connect, all four — not four invitations.\n3. Existing wpapps identities (ankit+vr@wpapps.press, ami@wpapps.press and the rest of the team) resolve to their existing address rather than a new account. Nobody gets a second identity.\n4. Ankit's org e4b1c744 and the WPAPP project: name whether they merge into the Bebond org or stay separate with cross-org visibility. Pick one, state it, do not leave both.\n\n## Acceptance\n- A wpapps team member clicks one button and afterwards can open a BEB ticket, read a BB Doc and use Orky chat, without Alex touching anything.\n- list_users returns the team, in the org where the work is.\n- The team's own work appears as tickets in the tracker rather than only in their own tools.\n\n## Not in scope\nAnything about the buurt. Alex was explicit: the buurt is nice-to-have prep, the wpapps team is the case.\n\nRefs: BEB-9282 (on-device for this same team), WPAPP-1 (their existing ticket, other org), CF OAuth one-button connect law (2026-07-16).","status":"todo","priority":0,"assignee_id":null,"created_at":1788601855436,"updated_at":1788622415281,"completed_at":null,"due_date":null,"claimed_by":null,"claimed_until":null,"required_capabilities":null,"estimate":150,"cost_ceiling":300,"cancelled_at":null,"last_actor":"unverified:shared"}