Add your own blocks to a managed stack
Orgs can now add, edit and delete custom blocks on managed stacks, from the Build page, fact insights, the API, MCP and the assistant, for everyone shaping their fact layer in NOAN.
Until now a managed stack was fixed. If one of NOAN's managed stacks almost fit what you were tracking but was missing a block, your only option was to start a new custom stack for the one thing you wanted to add. Over the API this showed up as a 403 ResourceNotAllowed the moment you tried to add a block to a managed stack.
What's new
- Add blocks to a managed stack. Create your own blocks on a managed stack from the Build page, from fact insights, over REST, over MCP, and through the assistant.
- Edit or delete them from the block card. Your custom blocks on a managed stack are yours to change; NOAN's managed blocks stay read-only.
- Private to your org. A block you add to a managed stack belongs to your org, so other orgs never see it.
- Over the API.
POST /stacks/:id/blocksnow accepts managed stacks instead of returning 403, and the OpenAPI descriptions say so. If a stack already has a block with that title, the existing block is returned rather than a duplicate created.
Why it matters
When a managed stack covers almost everything you track about a customer or a deal but misses the one field your team actually asks about, you no longer have to split that into a separate stack. You add the block where it belongs and keep the whole picture in one place.
Where to find it
Open the Build page in NOAN and add a block to any managed stack, or do the same over REST and MCP. The endpoints are documented at api.getnoan.com.