Settings › Pinned menu lets managers add custom groups of links to the project's side menu — shortcuts to the pages a team uses most, a filtered listing, a custom collection, one document, a form's submissions, a setup document or a module's page. The system menu (the seven areas — Home, Studio, Content, Shop, SEO, Modules, Settings) is not editable; custom groups appear beneath it for every member, subject to the same capability gates. Opening a record from a pinned collection keeps you in the pinned menu — Back returns to the list with the pin still highlighted, and a page reload keeps it too.
Drag a group's handle to reorder the groups, and a link's handle to reorder the links. To move a link to another group, drag it onto one of that group's links (it lands just above it) or onto the group itself — its title row, even when it is collapsed or empty — and it is added at the end. A group holds at most 24 links. Each group can also have its own icon (the pencil on the group → Icon); without one it shows the pin.
From an agent or the API#
The pinned menu can also be set from outside the console — by an AI agent in the project's workspace (the MCP tools readConsoleSettings → writeConsoleMenu) or by the API (POST /api/project/console/menu, the SDK's project.console.menu(groups)). The write replaces the whole menu, so an agent reads it first and writes every group back; it can link exactly the pages this console has (the routes readConsoleSettings lists) and is refused on anything else. The menu is one for both environments — a change made from Demo shows on PROD too. Each such write appears in Activity with the source API token. Writing needs the owner role, or a project token with the console grant — Settings › Advanced › SDK & MCP offers to add it to the MCP token (the token value stays the same). A manager connected with a personal access token writes with the owner role of their membership. An invalid menu is refused as 400 console_invalid with the offending rows; when the console's settings store cannot be reached the API answers 503 console_unavailable — try again later.