Skip to end of metadata
Go to start of metadata

To be able to work together on a model package, the model package must be saved to a central storage place that can be accessed by all participating users. The Team Server forms the basis for the primary storage place. Model packages and projects are stored and managed there. The users working on the model packages and projects are registered and managed there too. The Team Server is installed before users start working on model packages.

The Team Server also acts as the licensing server for the BiZZdesign licensing system. Activating the licensing system requires registering a license key in the Team Server, which is provided by BiZZdesign.


On this page:


Sections of the Team Server

User page

The user page shows various information about the user, divided into different sections.

The Info section shows the user's details like e-mail address, registration date, and the user's roles in the Team Server.

The Package and project invitations section shows the model packages and projects the user has created or has an invitation for. These can be direct (individual) invitations and invitations via groups. Any groups the user is part of are shown in the Groups section. If a user has been invited for a model package or project more than once, the model package or project is shown more than once in the invitations list.

The list of invitations and list of user groups show a limited amount of items. The Load more button can be clicked to view all items.

The Shared sites section is only available if HoriZZon is used. It shows sites in HoriZZon the user has created and sites that are shared with the user.


Example of a Team Server user page

Model packages

The model packages stored on the Team Server are shown on the Model packages page. On this page, users with the Administrator or System Administrator role see all model packages available in the Team Server. Users with only the Designer or Lead Designer role only see the model packages they are invited for directly or through a user group, and the model packages of the projects they are invited for directly or through a user group.

Any projects a user is invited for can be viewed via Projects in the sidebar menu on the model package page.


Model packages overview page in the Team Server

Users and user groups

Users in the Team Server are represented by a colored round icon with their initials in it. Users can be added manually to the Team Server, but can also be imported via an external identity provider like Windows Active Directory or Azure AD.


Users overview page in the Team Server


Groups can be created to assign permissions to groups of users.


Groups overview page in the Team Server


The information a user or group can see on the Team Server pages and the operations they can perform depends on the permissions the user or group has in the Team Server. The Team Server distinguishes different user permissions.

Team Server settings

The Team Server has a number of configuration settings, like e-mail settings, setting a limitation on inviting users, changing the Team Server database configuration, and viewing the Team Server audit log. The Team Server settings also host the configuration of several identity providers like Active Directory and Azure AD. The Team Server settings are only accessible to users with the System Administrator role. For more information about the Team Server settings, see Team Server configuration options.


Team Server settings page

Registration with the Team Server

To be able to register with the Team Server, a user will receive an e-mail with an invitation containing a link that will direct the user to the registration page of the Team Server.

If the user has been assigned the Designer or Lead Designer role, a configuration file can be downloaded via the Team Server toolbar, and then added to Enterprise Studio. The configuration file is used to make the Team Server available in Enterprise Studio as a storage place for model packages and projects.

Team Server installation

The Team Server must be installed before users can work together on model packages and projects. Installation is usually performed by an application manager.

Using multiple Team Servers

Basically, one Team Server is sufficient for working together on model packages and projects. However, multiple Team Servers may have been defined. When working together on different servers, each Team Server should be available as a storage place in Enterprise Studio.

Team Server as a hosted solution

The Team Server may be installed on a central location within your organization, but it may also be available as a hosted solution. This is the case if you are working with Enterprise Studio Online (the hosted solution). A hosted Team Server can also be available with Enterprise Studio locally installed.

When working with Enterprise Studio Online, the Team Server is automatically available for use. There is no need to download the configuration file and add it to the application to make it available as a storage place. It is automatically available in Enterprise Studio Online.

When working with Enterprise Studio Online, the Team Server toolbar has an option for starting a new remote session of Enterprise Studio.


Team Server home page when working with Enterprise Studio Online


When working with a hosted Team Server (with a local Enterprise Studio or with Enterprise Studio Online), the System Administrator role is not available. Also, the Settings menu, which is only available to System Administrator users, is not present in a hosted Team Server.