Studio templates and projects are now reachable through the API

If you automate work through the Studio integration, you can now list active templates, projects, and frames for an organization and fill a template's image slots directly, without needing client visibility into that project. Archiving a folder or moving a project through the same automation path now also works for active internal Studio projects, instead of being blocked.

Board card properties can also hold links to other records now: pages, boards, cards, customers, Studio frames, and Studio templates, when updated through the API. We used this ourselves to wire up the full SharpHaw blog thumbnail workflow: create the card, generate the image, fill a Studio template with it, and bind the resulting frame back to the card, all without leaving an automation script.

On the public side, the custom cursor from the audit report pages is now shared with the SharpOS home page, so pointer interactions feel consistent between the two.