Skip to Content
ChangelogOctober 2026

October 2026 Changelog

Covering releases from 1 to 31 October 2026 and the permissions review on 19 October.

October brings better controls for the approval queue, more ways to scope projects through an AI assistant, signed webhooks, and fixes to project creation, duplication, attachments and catalog editing. On 31 October six features and the new Project List switched on for every account. If you maintain an API or MCP integration, check the first three items under For integrators.

On for every account from 31 October

These features left early access on 31 October and are now part of every account:

  • Push to PSA V2. The redesigned Push to PSA screen, with ConnectWise service tickets, refreshable PSA settings and default companies taken from the client’s mapping.
  • Site Navigation V2. The reorganized navigation, with live record counts beside project sections.
  • Project Blueprints V2. Blueprints that carry professional and managed services, products, resources, governance items and expenses.
  • Service Hours Feedback. Compares the hours you estimate with the hours your team records in ConnectWise, Autotask or HaloPSA.
  • Adaptive Governance. Minimum hours on governance items, and percentages that change with project size or pricing model.
  • Approved Services Management. Keeps the last approved version of a catalog service in use while an edit waits for approval.
  • The new Project List. Export now includes every project that matches your tab, search and filters, in place of the Include archived projects in CSV checkbox. To export archived projects, open the Archived tab first. The export also ends with a Change Request Of column, which is empty unless your account uses Change Requests. Duplicate in the right-click menu always opens the Duplicate Project dialog, where you choose the sections to copy. Create New Project now needs Project Overview at Create or higher, Archive and Unarchive need it at Manage or higher, and Purge needs it at Purge. Users without the level don’t see the option. See Project List.

The accounts and users still on the previous Settings design have moved to the current one. The Line of Business section of the project sidebar, which grouped a project’s services by line of business, is now hidden. It is no longer maintained.

Permissions reviewed on 19 October

On 19 October we reviewed permissions across the application to make sure each one was being enforced correctly, and closed some gaps we found. The actions below now check the user’s role, in the app and through the API. A user whose role doesn’t allow one of them gets an error; through the API, and on some screens, it reads “Your role(s) do not have permission to complete the requested action. (403)”. The project header hides Cancel Approval, Re-Scope, Archive, Un-archive, Deal Won, Deal Lost and Update CRM from users whose role sets the permission below Manage.

To let someone run an action, give one of their roles the permission listed at that level or higher, in Settings > Users & Groups > Roles. A permission left unset on a role counts as its lowest level. A user with several roles gets the highest level any of them grants, except that View Only users get View at most. API requests and integrations run as the user who owns the token, so that user needs the permission too.

Under Project Permissions in the role editor:

  • Request Approval at Manage. Cancel Approval in the project header, Cancel when reviewing a Business Approval, and re-scoping a project with Re-Scope in the project header menu or Rescope on the Project Overview page. Your account may use its own name for Re-Scope.
  • Project Overview at Manage. Archive, Un-archive, Deal Won, Deal Lost and Update CRM in the project header menu.
  • Duplicate at Manage. Duplicating a project.
  • Service margins at Manage. Adjust Project Margin on the Overall Pricing page.
  • Professional Services at Create. Applying a blueprint to a project.
  • Professional Services at Manage. Refresh, Duplicate, Duplicate for all locations, Save as Standard and Update Existing Standard on a service in the current project services editor. To see Save as Standard and Update Existing Standard, a user also needs Professional Services at Manage under Settings Permissions.
  • Terms and Conditions at Manage. Switching a project’s terms and conditions between Included and Excluded.
  • Versions at Manage. Reverting a project to an earlier version.

Under Settings Permissions:

  • Professional Services at Manage. Un-Archive on the Archived tab of the Professional Services and Managed Services catalogs.
  • Professional Services at Create. Duplicate in the Professional Services and Managed Services catalogs.

In the Managed Services catalog, a user also needs Managed Services under Settings Permissions to see these options: at Manage for Un-Archive, and at Create or higher for Duplicate.

Approvals work differently. Only the approver an approval is assigned to can use Approve, Decline, Adjust Scope or Adjust Price on it, and no role setting changes that. If that approver is unavailable, see Project Approval Levels for your options.

Through the API, duplicating a project service needs Professional Services at Create, synchronizing a project subservice to its standard needs Professional Services at Manage, and moving a project governance item with move-to needs Project Governance at Manage. All three are under Project Permissions.

Pending Approvals shows the longest waits first

Pending Approvals now has page controls and a choice of how many rows to show. It starts with the longest-waiting approvals; click Time Waiting to reverse the order. Time Waiting now counts from when you were asked to approve, not from when the project was submitted. Canceled or declined steps, earlier steps replaced by a resubmission and archived projects no longer leave stale rows in the queue.

Shared survey links now stop accepting responses 14 days after the survey was shared, including links sent before this change. To collect a response after that, share the survey again.

What’s new in Push to PSA, Blueprints and Site Navigation

These changes reached early-access accounts during October and have been on for every account since 31 October.

  • Push to PSA V2. Users whose role permits creating PSA pushes can choose Refresh PSA settings on the Push to PSA form for a project that has not been pushed yet, to update the cached lists without waiting for the daily refresh. That form shows when the settings were last refreshed, which lists failed to load, and a warning when no ConnectWise project boards were found. When you pick a Company on a ConnectWise or HaloPSA push and the client has no company mapping for that connection, the choice is saved for later pushes. An existing mapping is kept.
  • ConnectWise service tickets and default companies in Push to PSA V2. A ConnectWise service-ticket push now requires a service board and creates service-desk tickets without creating an empty PSA project. Resubmitting adds tickets for newly added services and leaves existing tickets unchanged. A selected ConnectWise ticket priority is now honored. For ConnectWise and HaloPSA, the default company now comes from the client’s mapping for the selected PSA connection. A company from the project’s CRM opportunity is used only when the opportunity comes from that same connection.
  • Blueprints V2. When a blueprint adds a governance item the project does not already have, a fixed-hours item takes its catalog hours if the blueprint did not set its own, and an item with no resource takes the catalog resource. When it adds a standard resource the project does not already have, a zero rate takes the project rate table’s rate, while a nonzero saved rate is kept.
  • Site Navigation V2. The project sidebar now shows live record counts beside its sections.

For integrators

The first three changes below can stop an existing integration from working.

  • Account selection for API actions. The API acts on the token user’s current account. A few API v1 calls, such as document downloads, approval actions and audit-log revert, now return 404 when the URL names a different account’s slug. If your integration user belongs to several accounts, switch it to the account you need before making calls.
  • Retired MCP tools. The older MCP tools deprecated for removal on 30 September have been removed. Use the consolidated tools and the migration map for any calls in a custom client. The last deprecated tool, list_service_categories, has now been removed too. For the flat list of service categories, with each category’s parent and line of business, use scopestack_list_settings with model: "service-categories". The nested category tree and the option to include services have no replacement yet.
  • Retired count routes. The deprecated per-section /count routes in API v1 and v2 have been removed. Read meta.record-count from a collection response, applying the filters for the records you need.
  • AI instructions for catalog services. Catalog services and subservices can carry AI scoping instructions through the API or MCP. MCP can return the instructions with catalog-service details and project scope. Use them for guidance, such as questions to ask or companion services to consider, and keep them out of client-facing text. Changing only the AI instructions or Guidance Language of an existing service through the API or MCP usually no longer sends it back for approval.
  • Rate tables and project phases over MCP. An assistant can now change a project’s rate table and list or add project phases, including a custom phase. Service writes can use the names of project-specific or renamed phases. Changing the rate table reprices standard resources and removes a resource if the new table has no rate for it.
  • A default document template through the API. Set default: true on a document template through API v1 or v2 to pre-select it on new projects that don’t name a template, including projects created from the New Project form. Only one template per account can be the default. You can filter templates with filter[default].
  • More complete v2 reads. V2 project, line-of-business and service-category reads keep their relationship links regardless of which include request filled the cache first. Product accounting codes can be read and written at /v2/products/{id}/product-accountings, and GET /v2/account now honors include and fields.
  • Signed webhooks. Deliveries now include webhook-id, webhook-timestamp and webhook-signature headers, following the Standard Webhooks  spec. Existing subscriptions already have a signing secret, and receivers that don’t check the signature keep working. To verify deliveries, copy the Signing secret from the subscription’s edit page in Settings, which has Show, Hide and Copy controls for it. Viewing the secret requires Webhooks at Create or higher under Settings Permissions.
  • Resource pricing in V1 templates. Use resource_pricing_with_third_party in a V1 document template to include vendor-resource rows for one-time third-party services. Its total row includes their hours and customer revenue.
  • Descriptions for repeated services in V2 documents. V2 documents generated through the API now provide unique_descriptions and formatted_unique_descriptions for professional services. Use them with unique to show each service name once while keeping descriptions from the other occurrences, in phase and service order.

Fixes

  • Creating managed catalog services. Creating a standard managed service in Settings now saves without a phase-field error. The form uses Billing Frequency in place of Phase.
  • Project details after a survey error. When creating a project from a survey, your project details now stay in place if its recommendations cannot be applied.
  • Ask Support chat. Ask Support in the user menu now opens the support chat inside the app.
  • Password rotation stays off when you set it to zero. In Settings > Account Preferences, Password Rotation Interval now shows 0 when it is unset or disabled. Changing another preference no longer writes 90 into that field and turns password rotation on.
  • Attachment types and failed uploads. Editing an attachment now also hides types already used by an active attachment on the project. If an archived attachment holds the type, the error tells you to restore it from Archived or choose another type. Upload validation now gives the reason a file could not be saved, and a failed upload attempts to remove the empty attachment so you can retry with the same type.
  • CRM addresses when creating a project. Missing or whitespace-only address fields from a CRM opportunity now count as empty, so the form asks you to fill them in. If the location save fails, you see the reason and can retry without creating another project. ConnectWise opportunities now carry the site’s country with the address. Saving now updates a location already created from the opportunity instead of trying to add it twice.
  • Service locations in the project editor. In the current project services editor, the Location column now appears when the project has more than one active location, including a location no service uses yet.
  • Service list and delete confirmation. The current project services editor reloads its service list when you reopen it after adding services. Deleting only subservices now counts the subservices in the confirmation, instead of saying you are deleting zero services.
  • Product search and editing. In Settings > Product, starting or clearing a search returns to the first page. Saving a variable rate or accounting code keeps you on that tab instead of sending you back to Details.
  • Restoring catalog services. Un-Archive on the Archived tab of the Professional Services and Managed Services catalogs now restores the service. It previously showed an error and left the service archived.
  • Formatted contact phone numbers. When adding or editing project contacts, phone numbers with parentheses, dots, slashes and extensions such as ext. 21 are now accepted.
  • Rejected ConnectWise reads. Rejected opportunity-list reads retain the last successful sync time and report the reason. A rejection (any 4xx response other than 408 or 429) puts the connection in Connection Error. ConnectWise opportunities now take the contact’s name, email, phone and title from one person: the opportunity’s contact, else the company’s default contact, else the bill-to contact. A failed PSA settings refresh keeps the last good lists, and rejection of every list marks the connection in error.
  • Disabled CRM syncs stay stopped. CRM syncs stop when the connection or its CRM option is disabled, even if a job was already waiting to run.
  • Version history and user reverts. New version-history entries from API v2 writes, including template uploads, are now recorded under the account. Reverting a user edit preserves sign-in fields instead of failing, and a conflict with existing data returns a validation message.
  • Project duplication. Duplicating from the project header now preserves service order within each phase and edited service and subservice values, including names, language, rates and custom hours.
  • Classic Create Blueprint. Creating a blueprint through the project header’s classic form now saves the quantities and resource assignments chosen on that form.
  • Approval review. Assigned approvers can open Review from their row in a project’s approval details.
  • Terms and Conditions saves. An Included / Excluded toggle that fails returns to its saved position. A failed content save keeps the form marked as changed, and a load failure asks you to refresh the page.
  • Vendor lists. In vendor-resource and vendor-quote forms, scrolling the vendor dropdown loads more options. Typing two or more characters searches the list.
  • Connection activation and history. A new connection no longer stays at Activating because its sign-in started before the connection was saved. Deleting a connection keeps the service actuals already recorded and cancels any still waiting to be collected.
  • Variable rates saved to standards. In the current project services editor, Save as Standard and Update Existing Standard now correctly copy each variable rate not based on hours from services and subservices.
  • Survey evaluation. Unanswered Date questions no longer interrupt survey evaluation. A recommendation condition now counts as unmet when it compares values that can’t be put in order, such as a true/false calculation result, or two values of different types.
  • Blueprint lists. Blueprint lists on catalog service pages, in the current project services editor and in Settings now load when a V1 blueprint includes a catalog service that has since been permanently deleted. That service is skipped.
  • Live project pricing. Pricing that updates live on a project page now resumes after a dropped connection, as do the record counts in Site Navigation V2.
  • Archive and CRM actions for Purge-level users. Purge is the highest Project Overview level, above Manage. Since the permissions review, the project header menu had hidden Archive, Un-archive, Deal Won, Deal Lost and Update CRM from users at Purge. They show again.

Stricter browser security

On 31 October ScopeStack began enforcing its Content Security Policy, which lets the app load scripts, styles, images and fonts only from ScopeStack and from secure https:// addresses. Most users will see no change.

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.

Book a demoBrowse the docs
Last updated on