Managing iTwins

iTwin Studio has preliminary support for creating and editing iTwins.

Configuration

iTwin management functions can be enabled with the iTwinManagement key in app.config.json.

Users may select templates to use as a base when creating iTwins. You can configure which project type’s templates are available by setting the iTwinManagement key in app.config.json.

You can see the list of available project types from the Project Provisioning Service API.

App developers can also choose which features of iTwin management to enable (e.g. enabling media indexing). Note that some features require additional scopes.

Note: The projectTypes array must contain at least one project type. An empty array will fail validation.

Here is a sample configuration from app.config.json:

"iTwinManagement": {
  "enabled": true,
  "projectTypes": ["DesignBuild"],
  "features": [],
  "qa": {
    "projectTypes": ["DesignBuild"],
    "features": []
  }
}

Scopes

In order to enable iTwin management functions the following scopes are required in app.config.json:

itwin-platform openid enterprise provision-service product-settings-service

Additional Scopes for specific features

The configureMediaIndexing feature requires the synchro-media-indexing-service scope.

Permissions

The “Create” and “Modify” options will only be shown if the user has permission to complete those actions.

Some apps allow all their users to create iTwins, so users with entitlements to these apps will be able to create iTwins regardless of their RBAC roles. See the Wiki for details.

In all other apps, individual users must have the itwins_create permission. See the create-itwin API documentation for more information.

In order to modify iTwins, users must have the itwins_modify permission on the iTwin they would like to edit.