Pasar al contenido principal

Frequently asked questions about the Project Settings Management Console

Modified: 22 Mayo 2026 Tekla Structures - Not version-specific
Not version-specific
Tekla Structures

Find answers to frequently asked questions about the Project Settings Management Console, project settings, environments, collections, dependencies, and the order in which settings are read.

What is the Project Settings Management Console

The Project Settings Management Console is a web-based tool that lets you manage your project settings, environments, and other project files in the cloud.

You can create custom cloud-based environments to enhance collaboration and ensure uniform settings for users who open Tekla Structures models using Tekla Launcher.

For more information, see Project Settings Management Console (Preview).

What is a collection?

A collection is a reusable group of settings that belong to the same category.

You can combine different collections to build project settings. Each collection can hold files that are organized into categories and optional Tekla Structures extension packages (.tsep packages).

For more information, see Create collections.

What categories are used to organize content in a collection?

Content is organized into catalogs, documents, analysis, advanced options, modeling, applications and components, interoperability, and user interface customization and branding. Each category includes more specific subcategories.

For more information, see Add content to a collection or a company collection manually.

Is there an automated way to categorize my files when uploading?

Yes, you can use AI tools in the project settings sandbox to upload and automatically categorize content in files.

The AI tools analyze the files and suggest a category and subcategory for each file. If the file cannot be categorized based on the analysis, the file is categorized based on the file extension.

For more information, see Use AI to automatically categorize content in a collection.

How can I find a specific file in the settings editor?

You can use the Locate file search box in the settings editor. The search shows a list of files that match your search input across your content. The search also shows the category, subcategory, and collection of the files.

What is a company collection?

A company collection is an alternative to the firm folder for users who start Tekla Structures using Tekla Launcher.

You can use a company collection to enforce standards for all users in your company. Company collections are available in Tekla Launcher under Apply company settings when users create new models.

For more information, see Create a company collection.

What are project settings?

Project settings are a collection of customized settings that let you distribute an environment to users who start Tekla Structures using Tekla Launcher.

Project settings can be based on an existing official Tekla Structures environment with customizations, or fully customized with collections and dependencies.

For more information, see Create project settings.

What is a classic environment and can I still use it?

A classic environment is a package that contains uncategorized settings used by Tekla Structures. A classic environment can be an official Tekla Structures environment or your own custom environment.

Classic environments make the transition to using the Project Settings Management Console easier. You can upload an existing classic environment to the Project Settings Management Console to distribute the environment and extensions to users who start Tekla Structures using Tekla Launcher. You can also pin the classic environment as a dependency in your project settings to include the settings from the classic environment in your project settings.

For more information, see Publish a classic environment in the Project Settings Management Console.

What are private collections?

Private collections are groups of configuration files, such as .xml, .xmp, and .inp files, that belong to a category or subcategory. Private collections can only be used in the project settings where they are created.

For more information, see Create private collections in project settings.

What is a collection dependency?

A collection dependency is a published collection that contains settings at the subcategory level that your project settings requires. The collection dependency is automatically included in the installation.

What happens if a dependency is missing?

If a dependency is missing, the Publish and Test actions are not available. The editor shows a warning about the missing dependencies.

What is the difference between a collection dependency and a pinned environment?

A collection dependency references a published collection by ID and version. A pinned environment references a classic environment that contains uncategorized settings.

How do I add a TSEP extension to my project settings?

You can add TSEP extensions In the TSEP extensions section of the settings editor. You can search for and add extensions from Tekla Warehouse, or manually enter the extension ID, name, and version of the extension.

For more information, see Add TSEP extensions to project settings.

How does extension versioning work?

You can specify an exact version, a version that allows compatible major version updates, or the latest version.

  • Exact version: Use only the specified version.

  • Allow major version updates: Use the most recent compatible major version.

  • Latest version: Always use the most recent version.

In what order does Tekla Structures read the inheritance of settings?

Settings are read in this order:

  1. Company collections

  2. Project settings

  3. Dependencies are resolved and merged.

  4. Extensions are added.

If the same file exists in multiple places, the first one that is read is used. Other duplicate files are ignored.

Can I change the order of private collections, dependencies, and TSEP extensions in project settings?

Yes, you can drag and drop private collections, dependencies, and TSEP extensions in the settings editor to change their priority order. Private, dependencies, and TSEP extensions collections have priority based on their order in the list.

What happens when private collections or dependencies have files with the same name?

Private collections and dependencies have priority based on their order in the list. If the same file exists in multiple places, the first one that is read is used. Other duplicate files are ignored.

What are roles used for?

You can use roles in project settings to enable or disable specific settings within the project to provide a customized experience for different end users.

Roles represent user profiles, such as detailer or project manager. Each role maps to a subset of settings that are customized for the type of work that different types of users do.

For more information, see Add roles to project settings.

Can a user have multiple roles?

A user typically works with one role at a time, but different roles can be assigned in different projects, and users can change between roles.

How does publishing work?

Before publishing, the dependencies and the package definition are validated.

After validation, you provide a semantic version number, an optional minimum compatible version of Tekla Structures, and write a description of the changes. Then, the package definition is packaged into a .zip file and uploaded.

For more information, see Publish project settings.

How does semantic versioning work when publishing?

Semantic versioning is used to keep track of changes to the content, and prevents you from overwriting an existing published version.

The version number follows semantic versioning 2.0 format (major.minor.patch), such as 1.0.0 for the first version of the content.

This version number is used to keep track of changes to the content. We do not recommend using a Tekla Structures version number in the version number of the content.

What is the file validation that runs before publishing?

File validation ensures that all of the files that are referenced exist in the sandbox storage. If any files are missing, the validation tool shows a list of the missing files. You can replace or remove missing files.

You can also run the validation tool manually before you publish a collection or company collection.

For more information, see Validate a collection or company collection.

Can I delete content after it has been published?

Private content can be deleted by the content owner at any time. Public content can be archived, but it cannot be deleted or changed to private.

Archived content is hidden from search results and browsing, but it remains accessible to any project or workflow that already references it.

For more information, see Deleting Tekla customer content.

How do I test my settings before publishing?

With Tekla Launcher running on the same computer where you use the Project Settings Management Console, you can test your project settings in the project settings sandbox.

Open your project settings, click Test, and select the version of Tekla Structures where you want to test your project settings. Testing creates a model using your project settings and generates a log file if there are errors.

For more information, see Test project settings in the project settings sandbox.

Why is the Test action not available?

To test project settings, Tekla Launcher must be running on the same computer where you use the Project Settings Management Console.

The Test action is not available if:

  • There are unsatisfied dependencies.

  • Tekla Launcher is not running on the same computer where you use the Project Settings Management Console.

  • Tekla Launcher cannot communicate with the Project Settings Management Console.

For more information, see Test project settings in the project settings sandbox.

How do I share my project settings sandbox to collaborate with others?

In the project settings sandbox, you can invite users to collaborate using their email address.

You can give collaborators different permissions that allow them to do different actions:

  • Content viewer: The user can only view content.
  • Content contributor: The user can modify content, but they cannot add content, publish content, or share content with others.
  • Content manager: The user can add and publish content, but they cannot delete content or share content with others.

For more information, see Share your project settings sandbox.

How do I control who can use my published content?

In the Permissions dialog for your project settings, collections, or company collections, you can add permissions that allow or block access to your content.

You can add permissions for individual users, groups of users, or all users in a company's account.

For more information, see Define which users have access to your content.

What does migration do?

Migration updates your package definition to the latest definition schema version. It automatically applies changes to file usage types and expected subfolder structures.

Enviar

Table of Contents