November 2026 Changelog
Covering releases from 1 to 6 November 2026.
Project services
- Group Update. Select several services on a project’s professional services or managed services page, then click the pen icon beside the selected count to change them together. The resource, phase, service category, quantity and hours you fill in are applied to every selected service, and a field you leave blank keeps each service’s own value. Selected subservices take quantity, hours and resource only, and managed services have no phase. If an item fails to update, it stays selected so you can try again.
- Hide services from documents. On a project in Building status, choose “Hide from documents” from a saved service or subservice’s menu, or “Show in documents” to restore it. A crossed-out eye marks hidden lines. Their hours and pricing still count, and document templates must check
do_not_printto leave them out.
- Fields changed from the standard. Fields that differ from their catalog standard now have an orange border in the current project services editor. Hover over a changed short field to see the standard value, or choose “View standard” beneath changed description or language text; “Hide standard” closes it. Saving or updating a standard refreshes the comparison and keeps unsaved rows.
Blueprints
- Readable governance calculations. A blueprint’s “Governance” tab now shows “Percent of Total Hours” and “Fixed Hours” as calculation names. Percentage rates include a percent sign, so a stored rate of 0.2 appears as 20%.
- Service phases stay in place. Opening and saving an older blueprint in the current editor now preserves its services’ catalog phases, using the approved version’s phase when available. Saving a blueprint keeps each service in its phase unless you move it, and moving a service no longer leaves a broken phase reference that causes it to be skipped when the blueprint is applied.
- Governance settings follow the catalog. When a blueprint adds a governance item, it now inherits the catalog item’s service filter, effort allocation and choice of assigning effort to services or reporting it separately, unless the blueprint saved its own values. A phase or category that cannot be matched on the project keeps the default setting so the item can still be added.
- Project details apply without unrelated field errors. Applying a blueprint’s project details no longer fails because the project has an unrelated required user defined field left empty.
Service catalog approvals
- Saving, copying and importing standards. “Save as Standard”, “Update Existing Standard”, catalog “Duplicate” and API imports from the pre-built Service Catalog now follow the acting user’s catalog approval rules, including for subservices. Changes needing approval stay Pending, while eligible Active services publish their latest approved versions after their rates and subservices are saved. A pending edit leaves the last approved version available for projects.
- Current approved versions. API v2 reads of approved services and subservices now return the current approved version consistently, instead of sometimes returning a superseded version when a page reloads.
- Activating archived services. Activating or approving an archived catalog service now clears its archive marker, including when its state is changed through API v1 or v2. The service can be used again and its approved version can be saved.
Forms and navigation
- Searchable tags. The “Tags” field on project, catalog-service, blueprint and survey-template forms now lets you search and select existing tags. Creating a new tag requires “Tags” at Manage under Settings Permissions; new names are trimmed and duplicates are ignored. Saving a survey without editing its tags keeps the existing tag names.
- Your Managed Services label. Your account’s Managed Services label now appears in project and Settings navigation, the services page heading, pricing summaries, blueprints and project-duplication dialogs. Accounts without a custom label continue to see “Managed Services”.
- Account labels in the project menu. The project menu now uses your account’s labels for “Customer Summary”, “Terms & Conditions”, “Vendor Quotes” and “Governance”. Vendor quote labels use the same plural forms as the previous navigation.
Surveys
- Default sections stay removed. Saving or renaming an existing survey template no longer adds another default section after the original section has been renamed or removed. New templates still start with a default section.
- Dragging sections and questions. Dragging a section or question now saves the order where you dropped it, including moves between sections. Another move waits for the saved lists to reload; if that reload fails, a message asks you to refresh before reordering again.
- Finding recommendation items. The “Item” picker for a survey recommendation now searches the selected item type’s catalog as you type and loads more results as you scroll. Saved recommendations show their item names correctly, including items outside the pages already loaded.
Push to PSA
- First push to an existing project. The first push into an existing ConnectWise or HaloPSA project now completes the normal setup for the selected project instead of treating it as already linked and skipping that setup.
- Resubmit error fixed. “Resubmit to PSA” no longer fails with “the resource object does not contain a key”.
- Unreachable PSA hosts. When API v2 cannot reach the PSA while loading a settings list, it now returns a 422 response with “PSA unreachable” and the reason, instead of a server error.
For integrators
- Project status is read-only on API update. API v1 and v2 no longer accept
statuswhen updating a project: a request that includes it returns 400 and changes nothing. A create may still include it. Use PUT on the project’s status-action endpoints:request_approval,cancel_approval,rescope,deal_wonanddeal_lostin v1, orapproval-requests,approval-cancellations,rescope-requests,deal-winsanddeal-lossesin v2.
- MCP scope locks and status transitions. MCP changes to project details, scope and project service language now require Building status. Send a status change separately from other edits:
technical_approvalrequests approval through the workflow, andbuildingcancels an approval in progress or re-scopes an approved project. The approval workflow setsapproved,sales_approval,business_approvalandcanceled; these cannot be written directly.
- Catalog subservice language over MCP. MCP can now read and update document language on catalog subservices, including subservices created with a catalog service. Send
languagesentries withfieldandvalue; omitted language fields are preserved, and unrecognized keys are reported inignored_fieldswhen valid keys are also supplied. Readpermitted_language_fieldsfromscopestack_tool_guidancefor your account’s accepted keys.
- Creating catalog services over MCP. New catalog services that do not need further approval now publish their approved versions after their subservices are saved, so they appear in the service picker. An unknown phase is rejected before the service is created.
- Find governance by name. API v2 governance lists now accept
filter[name]to find items whose names contain the supplied text, without regard to case.
- Project-resource relationships. API v1 and v2 now correctly save project-resource relationships that point to a vendor or an internal resource.
- Users assigned to roles. API v1 and v2 can now read the users assigned to a role without a server error. The existing user-visibility restrictions still apply.
- Invalid filters and unresolved users. An unrecognized
filter[active]value no longer causes a server error and leaves the collection unfiltered by that value. Actions that require a role permission now deny requests without a resolved token user instead of failing with a server error.
Fixes
- CRM details when duplicating a project. Choosing a CRM opportunity in “Duplicate Project” now fills the new project’s name, client, service-location address and matching assigned people from that opportunity. Clearing the opportunity keeps the filled-in fields so you can edit them.
- Adding project resources. The project Resources page now shows the server’s reason when a resource cannot be created and blocks a second submission for the same row while its save is in progress. If the result cannot be confirmed, the message asks you to reload before trying again. A resource that saved successfully is no longer reported as a failed create because a later local update fails.
- Vendor quote lines. Removing a vendor quote line no longer overwrites its project service with the removed line’s old values. A quote line that fails validation no longer creates a project service.
- Single-resource Work Breakdown summaries. Work Breakdown now shows the resource name correctly when a service summary has exactly one resource.
- Whole-number managed-service terms. Managed-service contract terms now require a whole number. Blank or fractional terms return a validation error.
Getting Help
Have questions about any of these? Our Support Team is here to help.
📧 support@scopestack.io 📚 Visit our Help Center
New to ScopeStack?
ScopeStack automates scoping, pricing, and SOW generation for IT services teams. See how it fits your process.
Last updated on