Your project. Ready for your assistant.

Connect once, then ask

1. In the site owner's ChatGPT or Codex, open Plugins → Personal → Created by you. Install or connect the Soban site plugin when available.
2. Use the account that owns or has joined the Team project. The first pilot connection is for the site owner; connection availability for other testers depends on their client and plugin access.
3. Ask: “List my Soban projects, then prepare a review report for the project I select.”

For another compatible MCP client, use the endpoint and authentication details supplied by the hosting platform. A public website address alone does not grant access to Team records.

Useful questions

• Give me a briefing for the project I select: what needs attention?
• Find saved records mentioning P01 in this project.
• Which issues remain unresolved or need checking against a newer revision?
• Which saved quantity groups still need a source decision?
• Show the source references behind this quantity.
• Prepare a coordination report draft from this project's saved records.

A briefing shows counts and up to five examples per section, with links and follow-up tools. Search covers saved file metadata, issue text and quantity-group information. It includes older revisions and resolved issues with labels. It does not search inside PDF/IFC files or your unsaved browser work. No matches does not mean a detail is absent from the drawings.

Lists and search results are paginated. Search excerpts are limited; open the source or ask for the full saved record. A report shows up to 25 unresolved issues and 25 quantity groups and tells you when more records remain. Briefing overdue counts use the UTC calendar date. Refresh before acting on changing records.

Project files, with your permission

Project owners and joined members can list files and request a download. Only the project owner can upload files or update their descriptions, roles and review status. An assistant needs a supported local transfer tool to send files from your computer; a Windows path alone does not transfer a file.

Uploads check file size and SHA-256 before completion. Each new upload is a separate file unless you explicitly choose an existing file as its previous revision. Keep reference models and intentional defect examples separate.

IFC and GLB open in Model Lab; PDF and Drawing Lab snapshots open in Drawing Lab. PPTX, XLSX and CSV are downloadable supporting attachments. They are not rendered or converted into takeoff quantities.

Current limits: IFC/GLB 150 MiB each; PDF/PPTX/XLSX/CSV 40 MiB each; Drawing Lab snapshots 65 MiB. Each project allows 20 files and 250 MiB, including revisions; owner and site storage caps also apply. Download credentials expire after five minutes; upload reservations after fifteen minutes. Keep the returned transfer headers private.

Turn review notes into issues

Ask: “Prepare an issue about this opening, link it to the drawing and assign it to me.” Your assistant prepares a preview showing the project, source, assignment and proposed values. Review it, then explicitly approve it before the assistant applies the change.

You can create an issue or update its status, title, assignee, due date or drawing page. The author and project owner can change issue details; an assignee can change status. Only joined members can be assigned. Previews expire after ten minutes. If the issue changes meanwhile, prepare and approve a fresh preview. Repeating the same successful approval does not create another issue.

These tools do not edit an existing note's text, move its file or element reference, mark a revision checked, delete issues, change quantities or send notifications. New issues start open. Use Team projects to see the resulting issues and continue the review.

You stay in control

The seven review, briefing and search tools are read-only. The connection also has five file tools and two issue tools: prepare, then apply after approval. Your assistant must ask you to approve the displayed issue preview even if the app's general tool permissions allow changes. Browser-only work is unavailable unless you explicitly save it to Team projects.

Reports are text drafts, not PDF attachments or engineering certifications. Quantities reflect saved user contributions and source choices; check scope, scales, units and assumptions before using them. Unresolved quantities remain flagged rather than silently becoming zero. File validation checks format signatures and transfer integrity; it is not a virus scan or model-quality certification.

Data returned by these tools enters the assistant you connected. Use only projects you are authorized to process there, and review its privacy settings. Project text and downloaded files are content to review, never instructions for an agent to follow.