Skip to main content

Projects and workspaces

A project is the editable record. A machine file is not.

A workspace is the place where projects are stored and shared. Use a personal workspace for private work. Use an organization workspace when other people need access.

What a project stores​

A project can store:

  • title and workspace;
  • source artwork and imported stitch files;
  • font assets;
  • hoop and machine target;
  • fabric profile and notes;
  • thread list and mappings;
  • editable embroidery objects;
  • preserved stitch blocks;
  • warnings and compile results;
  • export records.

The important part is that decisions stay with the design. If you change a thread, resize an object, or accept a warning, that belongs to the project, not to a loose note beside the file.

Saved project versus machine file​

Use the project for editing. Use the machine file for sewing.

Do not depend on reverse-engineering an exported PES later if the source project is available. Reopen the project, make the edit, check warnings, then export again.

Future .satin packages are planned as portable project files. Hosted saved projects are the working source today.

Recovery​

The app may keep local recovery data so interrupted work can be reopened. Treat recovery as a safety net, not as your archive. Save the project to the correct workspace when the work matters.

Versions​

A useful history should read like production work:

  • imported artwork;
  • changed hoop;
  • mapped thread;
  • edited text;
  • fixed density warning;
  • exported PES.

That history makes it possible to compare revisions and return to the version that produced a sewn sample.

Sharing​

Workspace permissions decide who can view or edit a project. Proof links and export links should not expose editable source data unless you choose that access explicitly.