> For the complete documentation index, see [llms.txt](https://docs.multiset.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multiset.ai/quick-access/changelog/v2/version-2.1.0.md). # Version 2.1.0 Team members and RBAC, vps-2 Deep Search query mode, georeference API, MapSet add without picking an overlap, partial map updates. ### v2.1.0 11-July-2026 **Added** 1. **Team members and multi-account RBAC.** Accounts now support multiple members with **Owner**, **Admin**, and **Viewer** roles. Invite teammates to your account by email, switch between accounts you belong to, and roles are enforced across all routes. Owners manage billing and membership, Admins manage content and API credentials, and Viewers have read-only access. Manage your team from the new **Members** tab in the Developer Portal. [Team Members](/fundamentals/team-members.md) 2. **New `vps-2` query mode for the Single Frame Query API.** The single-image Map Query endpoints now accept a `queryMode` parameter that selects the localization engine per query. `vps-2` runs the new Deep Search engine with up to **15% higher recall** and improved accuracy, at the cost of higher latency (\~3 to 4 seconds) — ideal for offline or background workflows where accuracy is preferred over speed. Existing integrations are unaffected: when `queryMode` is omitted, queries run on `vps-1`. [Query Mode](/fundamentals/localization/query-mode.md) 3. **VPS-2 in the simulation viewer.** Deep Search can be tested on your own simulation datasets from the Developer Portal simulation viewer using the new **VPS-2** option, alongside the existing Single Frame and Multi Frame runs. [Simulation Data](/fundamentals/rest-api-docs/simulation-data.md) 4. **Georeference 3D maps via API.** New API to georeference 3D maps using a pair of 3D and WGS 84 points. [Georeference Map](/fundamentals/rest-api-docs/georeference.md) 5. **Add maps to a MapSet without picking an overlapping map.** When you add a new map to an existing MapSet, it is now aligned against the entire MapSet automatically — you no longer choose which existing map it overlaps. [MapSet : Multiple Maps](/fundamentals/mapset-multiple-maps.md) 6. **GravityAligned merge for MapSet.** MapSet merging now supports a **GravityAligned** merge, recommended for most merges where the maps share the same plane. [MapSet : Multiple Maps](/fundamentals/mapset-multiple-maps.md) 7. **Partial map updates in Map Versioning.** Map versioning now supports multiple active maps, so you can push updates to a section of a map instead of replacing the full map. Localization queries run against all active maps in the version and return a pose in the base map's coordinate frame. Choose which maps participate with the new **Query Active** toggle in the Developer Portal. [Map Versioning](/fundamentals/map-versioning.md) 8. **Moving-object masking in 360-to-VPS.** The 360-to-VPS pipeline now masks moving objects such as vehicles and people in the splat, improving metric scaling accuracy. [Insta360 Scans](/fundamentals/third-party-scans/360-videos/insta360-scans.md) **Fixed** 1. Geo-referenced E57 files can now be uploaded directly, and MultiSet geo-references them automatically on upload. [Georeferencing Maps](/fundamentals/georeferencing-maps.md) 2. E57 to Mesh now produces a more accurate mesh with less noise. 3. Human masking in mesh texturing: people captured during scanning are now masked out when the mesh is textured. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.multiset.ai/quick-access/changelog/v2/version-2.1.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.