Requesting access

If someone opens a link to a private file, they do not hit a dead end — they see a request-access screen. The owner gets a notification, approves or declines, and the requester is let in with view rights — the same flow you know from Figma or Google Docs.

Pin comments on the canvas

Feedback works best next to the thing it is about. With the comment tool C, click anywhere on the canvas to pin a comment to that exact spot — a specific image, a material, a corner of a render. Replies thread under the pin, so discussions stay organized.

  1. Press COr pick the comment tool from the toolbar.
  2. Click where the feedback belongsThe pin anchors to that spot.
  3. Mention teammates with @

    Type @ and a name — they get notified and can jump straight to your pin.

A pinned comment thread on the canvas
Threads live exactly where the conversation belongs.

Notes vs. comments

Notes N and comments solve different problems. Notes are part of the canvas — use them for annotations, labels and context you want everyone to see as part of the work. Comments are for discussion — questions, feedback and decisions that get resolved and archived.

Note

A good rule of thumb: if it should still be visible when the discussion is over, make it a note.

Inviting teammates

For people you work with regularly, invites beat links: workspace members see every project, while project invites scope access to a single project. Invited teammates can edit, comment and generate — link viewers can only look.