Simplify and automate adding models to Kinship.

Overview

By default, when Kinship detects a new or non-tracked model, the user is asked if they would like to add the model to their team, and if it should become private. Learn more about adding models to Kinship.

This can be automated by setting Sync Rules that will perform a preset action depending on the path or filename of a given central model.

Note: Kinship will ignore Central models which are stored on a C:\ drive as it assumes that they are not shared. However these can be added explicitly by users from the Model Sync Status menu item in the Kinship add-in panel.

Each rule can be assigned one of the following actions:

• Never – never add models from this location to Kinship.
• Auto Private – automatically add models from this location to a private project in Kinship.
• Auto Public – automatically add models from this location as public to Kinship.
• Ask User – allow users to decide if the model should be added or not and if it should be public or private.

When the rule is set to Never, users are no longer asked if they would like to add the model to Kinship. Administrators can still add the model explicitly by clicking Model Sync Status button in the Add-in ribbon panel. 

When a regular member or content manager attempts this, they will see the following message.

Models that are added as Private (automatically, or by a user) will always be assigned to a new private project. Learn more about private projects.

Models that are added as Public (automatically, or by a user) will either: be assigned to an existing project, or will be added as unassigned. Learn more about how models are assigned to projects. 

Setting up Model Sync Rules:

1. Expand the Model Sync Rules section on the Settings & Administration page.
2. Type in the path or file name to which you would like the rule to apply into the box provided.
3. Select the action to take.
4. Click Add when done to add the rule.
5. The rule will appear in a table at the bottom of the section.

• Rules are tested in descending order. Action is taken on the first matching rule for a model and remaining rules are ignored. You can reorder rules by dragging them up or down in the table, and delete them with the cross to the left of the rule.

• Rules can be specified either as a path or as a file name but not both. For example:

  • *secret will match all models in any location, with the word “secret” in their filename.
  • *\eTransmit\* will match all models in a folder called “eTransmit” and all its sub-folders.
  • \\SRV-LON\* will match all models stored on SRV-LON.
  • \\SRV-LON\*secret is not a valid specification and will not match any models.

• Rules are matched against the UNC and not against mapped drives.