Linear Detail Integration Block for React

read is the default and Linear always includes it. Comment adds comments:create, which lets an app create issue comments. Create issues adds issues:create, which lets it create issues and their attachments. These are the targeted scopes Linear documents as alternatives to the broad write scope, and admin is never requested. Scopes go in the authorize request as one comma-separated list, for example scope=read,comments:create. Edit SCOPES and PERMISSIONS at the top of the file to match what your app really asks for.

Each permission in PERMISSIONS has a rank: 0 appears from Read only up, 1 from Comment up, 2 only at Create issues. The checklist, the chips and the count ("4 of 6 permissions") all derive from those ranks and the selected level, so adding a permission is one object. LEVELS holds each level's label and the sentence read out by the status line.

No. Both buttons are links (href="#"): point Connect Linear at your Linear OAuth authorize address with the scope list the chosen level produces, and View docs at your setup guide. The level control changes this page only, and the status line says "Nothing is sent to Linear". Connect Linear is a Shine Button, the block's one primary action; View docs is an outline button. Both buttons render the link they're given with render, with nativeButton={false}.

The block names Linear in text, the way any integration page says what it works with, and ships no Linear logo, colour or wordmark. Its tile is a neutral lettermark, Li in a muted square, in an icon slot that a code comment marks: drop in the official logo only if you have the rights to use it, under the owner's brand guidelines, and never redraw it. The pair is hidden from assistive technology because the heading already names both products.

The level control is a real segmented radio group named by its heading: arrow keys move between the three levels and the choice is announced. A locked permission is marked in words ("Not at this level") as well as by its tint and lock icon, and each scope chip carries a hidden "requested" or "not requested". The status line is a polite live region that is in the page from load, so a change of level is spoken once.

On a phone the level control fills the panel, the steps stack between rules and the scope chips wrap. The panel holds one height across levels because every permission row is always drawn, locked or not. Scopes stay left to right inside a right-to-left layout while the rows flip. The header and panel fade up once on load; with reduced motion they simply appear.