Company Blueprint gives your coding agent published company guidance. Purchase Desk's Team edition brings purchase requests, reviewers and records into a shared app, while Team launch tracks whether people complete the workflow. Optional App Security checks add release evidence before deployment, and new examples and guides make it easier to get started.
Company Blueprint publishes the guidance every build starts from
Administrators can draft and publish company guidance in Workspace settings → Company Blueprint, including brand styles, interface and code patterns, authentication guidance, frameworks, starters and data-product references. Coding agents can retrieve the current publication or a specific version, and releases can record which version they used. Published versions stay available for review. Data references respect the reader's permissions; access grants, security checks and release policies are enforced separately.
Why we built it: Teams should not have to repeat the same company instructions in every build conversation. A published version gives builders a consistent starting point and reviewers a record of the guidance used for a release.
Purchase Desk Team edition, with shared records and assigned reviewers
The new Team edition uses SpringRoll accounts and a managed PostgreSQL database for shared purchase requests, private attachments, notifications and decision history. An owner assigns reviewers who already have app access. Requesters can submit, receive a request for changes and resubmit; reviewers cannot approve their own requests. Records survive app restarts and redeployments, and removing a member's access blocks their next protected request, including at the direct hosting address. The app starts private and empty, and requires configured application sign-in and managed database hosting.
Why we built it: A team needs to work on the same request and retain the decision after an update. Shared storage, explicit reviewer assignments and access checks let colleagues complete that workflow with their own accounts.
Team launch follows the work through to an outcome
App owners and administrators can record a department, workflow, participants, intended outcome, acceptance criteria and review date in Team launch. Starting a launch fixes the original participant group for reporting. The report brings together the Company Blueprint version, sign-in, participant access, deployment and release security evidence. A two-person milestone requires one participant to submit and another to approve the same request. Apps that report workflow events also show activation, returning participants and completed workflows. Time saved is labelled as an estimate based on owner-entered before-and-after timings; missing evidence remains Not measured.
Why we built it: Deploying an app is only the beginning of a team trial. Owners need to see whether colleagues can finish the intended work and have enough evidence to decide what to improve at the review.
Optional App Security checks before deployment
Settings → App Security lets administrators choose the apps, environments and checks covered by a versioned policy. Available checks cover source code, dependencies, embedded secrets, built apps and AI behavior, with findings and coverage gaps shown on the app's Security page. The same gate applies to deployment, promotion, rollback and hosting migration. Warn permits deployment with the report after checks finish or reach their deadline; Block stops a release when required evidence fails or is missing. App Security starts off and requires an operator-configured scanning service, with synthetic test profiles for checks that need authenticated access. A release approval cannot override a blocking security result.
Why we built it: Reviewers need evidence tied to the release they are about to run. Explicit coverage gaps and policy choices let a company introduce checks gradually without treating an untested app as a security pass.
Try an example, then create your own copy
Examples now includes Deal Desk, Purchase Desk, Support Room, Campaign Room and Operations Queue. Try their fictional workflows in the browser, download the source or create a private copy in your workspace. Creation follows your workspace's direct or staged deployment workflow and respects its hosting settings. Returning to an example reopens your existing copy without overwriting it. These original examples keep edits in the browser; choose Purchase Desk's Team edition when you need shared purchase records.
Why we built it: A working example makes it easier to explain the app you want and test a first deployment. Clear storage behavior helps you choose a starting point that fits a demonstration or a real team workflow.
Let your AI connection submit a proposal you have approved
You can separately opt in to agent confirmation when authorizing a ChatGPT connection. With that permission, the connection can submit an exact saved proposal after your explicit approval, without another browser confirmation. The submission records the connected member, delegated action and approval note. Existing connections keep their current permissions, changed or expired proposals need a fresh review, and company governance decisions still require a person.
Why we built it: People who choose to delegate the final submission can finish an approved action in the conversation. Separate consent and a recorded proposal keep that convenience tied to the change they actually reviewed.
