Support for Google IDP and SCIM. Improved support for signing in with Microsoft.

We’ve supported Single Sign-On with Microsoft EntraID (previously Azure AD) for some time. Now we’ve added support for signing in with Google Workspace accounts as well as automated provisioning of users via SCIM. For teams using EntraID, you can now use the Sign in with Microsoft button to access your SSO-enabled team without the need to navigate to your team subdomain first.

Get results from the library first.

When searching using the Kinship add-in for Revit, users will see results from their current project, the library, their available collections and other tracked projects. Users can then apply a set of filters to narrow down the source of their results.

Multiple customers expressed a desire for their users to start by seeing only results coming from the library, while still retaining the option to see results from other sources.

To achieve this, we’ve added a new option in Team Settings to “Show results from the Library tab first”. If an admin toggles that option, users will default to the Library filter when searching in Revit, while still having the option to click on the other source filters to see additional results.

Overwrite system families in models.

Kinship was always able to overwrite existing components in models. But due to API limitations, doing the same with system families required a bit more thought.

We’re happy to report that you can now overwrite system families in models as well. When loading a system family type that shares the same name and category with another system family, the existing family type will be renamed with the suffix “Obsolete”. The new family type will load into the model, and all instances of the obsolete type will be changed to the newly loaded type. Simply select and delete the obsolete type to remove it from the model.

Detect when a model is moved to Autodesk Cloud.

Models tracked in Kinship can be stored on a network server, in Autodesk’s BIM360/ACC cloud service, or in any other hosting environment. Previously, if a user moved a tracked model from their own server to the Autodesk cloud, Kinship would detect it as a new model. This would result in missing historical information and duplicate models.

You can now move a tracked model to Autodesk Cloud, and Kinship will give you the option to update the model’s location instead of adding it as a new model.

Improved sign-in and activation.

We have improved our sign-in and plugin activation processes from top to bottom. This includes a new interface, clearer instructions, and helpful options along the way.

You’re also now able to use the same email for more than one Kinship team. This feature is especially useful for BIM consultants and other service providers who help manage or support multiple teams using Kinship.

Improved management for collections and lists.

Collections now have a Recently Deleted section, where users can manage deleted content. This includes viewing, restoring, and permanently deleting content.

You are also able to load entire lists and collections in one go, instead of loading items individually or taking multiple steps to select all and load.

Improved handling of content with the same name.

Users can now merge, replace or skip items with the same name when adding or moving content to the library or a collection.

Press the Shift key to reveal the option to keep both items, and in turn, the copied item will be renamed.

That concludes our November round-up. We’ll be back with another edition in December or January as we get back into the swing of sharing monthly updates.

As always, if you have questions or feedback on these or other Kinship features, just hit the feedback icon in the Kinship web app or send us an email at support@kinship.io. We review all feedback carefully.