Documentation / Projects

Projects Overview

Link a Rhino file to a project, see what the project holds, and keep it private.

The Wrengler panel opens on Projects. Switch to Systems at the top for the analysis studies; the panel remembers your choice.

  1. Open or create the Rhino file.
  2. In the Wrengler panel, on Projects, choose Link project.
  3. Pick one of your projects, or type a name to create a new one.
  4. Save the Rhino file. The link is stored in the file itself.

From then on the file opens already linked. The link survives renaming and moving the file.

The link is an id stored in the Rhino file, so renaming or moving the file doesn't break it.
ℹ️

Save As makes a copy that stays in the same project and shows up there as its own file, so you can see both versions side by side.

To move a file to another project, choose the project name in the panel and pick a different one. Unlink removes the file from its project; linking it again later finds the same file.

Where projects live

Every project sits in a workspace, and every workspace in an organization:

  • Organization: the people, their roles and the rules, such as limits, the audit log and housekeeping.
  • Workspace: a team, client or programme of work. It decides who can open its projects, and it holds the knowledge they share.
  • Project: the work itself: its Rhino files, uploaded files, studies and conversations.
An organization holds workspaces, and a workspace holds projects. Workspaces decide who can open what.

The dashboard's sidebar walks down this path one level at a time. An organization lists its workspaces, a workspace lists its projects, and the link at the top of the sidebar goes back up a level. Your personal organization is just you, so it skips the workspace level: your projects sit directly under it until you add a second workspace.

What a project holds

WhatWhere it comes fromWhere you manage it
Rhino fileslinked from the panelthe panel (link, unlink)
FilesPDFs, Word files, notes and images you upload (supported files)the project page on the web
Tagskey/value facts: gfa = 12000 m², typology = residentialthe project page on the web
Studiesanalyses saved to the project — saving runs from the panel is comingthe project page on the web
Conversationschats with the assistantthe panel and the web — the same threads

In the panel, the database icon next to the project name opens the project's data: every linked Rhino file, uploaded file, tag and study, by source. On the web, the project page has a Chat tab and a Data tab.

Tags make projects comparable. On your projects list, filter by a tag (gfa ≥ 10000) to find every project that matches.

Supported files

A project accepts these files. Anything else is refused when you attach it, with a message listing what is accepted.

FormatExtensionsThe assistant can read it
PDF.pdfYes — the text in the file. A scanned PDF is only pictures of pages, so it has no text to read.
Word.docxYes — the text of the document
Markdown.md, .markdownYes
Plain text.txtYes
CSV.csvYes
Images.png, .jpg, .jpeg, .webpNo — stored and shown, not read

The assistant quotes what it reads from these files, and still takes numbers from the project's tags and studies rather than from a document's text.

💡

Have a file in another format? Save or export it as one of these first: a spreadsheet as .csv, an older Word .doc as .docx, a drawing as .pdf.

Files attached before this list existed stay in the project. Rhino files are never uploaded; they are linked.

Who can see a project

A project is private to your account.

The file carries only an id. The database checks every request, so a copy of the file opens nothing for someone without access.
  • The Rhino file only carries the project's id. It never carries the project's name, its files, or any key.
  • If someone opens a copy of your file, the panel tells them it is linked to a project they don't have access to. It never shows them the project's name, and they cannot read it or add to it. They can unlink the copy and link it to a project of their own.
  • Access is checked by the database on every request, not by the panel, so a modified file or plug-in cannot get around it.

Sharing is coming. Inviting a colleague into a project is planned; until then each person links their copy to their own project.