Restricted Projects

Restricted projects add an extra layer of security to Kinship and allow you to mark projects as being confidential, so that they are only visible to administrators and the project team.

What is a restricted project?

If you need extra confidentiality for a project your can mark it as restricted. 

The project and models assigned to it will only be visible to administrators, and to the team members who are working on it (members who have performed at least one SwC from a model in that restricted project).

Project content, and the content of the models within a restricted project will not be searchable by other members.

Note: When security administrators are enabled, administrators are not able to view restricted projects. Throughout this article references to administrators will mean security administrators in the case that they are enabled.

• Restricted projects are only visible to team members and administrators.
• Projects which are restricted are marked with an icon of a blue lock, next to the name.

A user who does not have visibility of a restricted project cannot perform the following functions:

• Browse to the project’s page
• See the project or any of its models in the Browse Projects or Browse Models page.
• See the search results from the projects in the add-in search box or on the webpage search results
• Assign the project to a collection.

A user will be added to a restricted project when they do a SwC from a model which is part of that project.

Creating restricted projects

The visibility of the project and its content can be set in the following ways:

Directly from Revit

• When a model first registers with Kinship it can be specified as being restricted by the user. In this case it will always be assigned to a new project.

Using the web interface

By an administrator who can Set as Restricted from the webpage.

By an administrator who can Make Visible to Team from the webpage.