Database Hub (Enterprise)

You who are an Enterprise customer can administer your own database copies which, for example, can be used for training and testing and further development of your setup.

General information

As an Enterprise customer, you can create up to two additional databases that you administer yourself.

These can be used, for example, in internal training where you want users to be able to practice in the system without changing your actual database, and for further development of your setup where you want to test new nodes, views and reports before you implement them sharply.

The databases are based on your sharp / ordinary environment and becomes a copy of the sharp database when created.

Find the database hub

You access the database hub administration via the Platform Administration in the Stratsys left menu.

If you do not see this icon, you will miss the role "Super Administrator" in the platform. Contact your local Stratsys administrator for questions about your privileges.

Inside the Platform Administration, select Database Hub under the Enterprise menu:

Create a database

Either select "Copy" from an existing database, or press "Add database" - both paths leads a window where you get to choose the following

  • Which database you want to copy - once you have created a test or training database, you can also choose to copy one of those databases.
  • What name the database should have. The name of the database must be unique to all customers and may only contain letters [a-z] [A-Z] and numbers [0-9] - so do not use spaces, underscore etc. in the name, and feel free to include the name of your organization to ensure that it becomes unique.
  • What type of database it should be: Education database or Test database. There will be no difference depending on the type you choose, but this choice is there to make it easier for you to distinguish the purpose between your databases in this administration.

Following that simply hit the "Add database" button. It takes a while for the database to be copied - an indicator shows when it is ready.

Access and login'

All users who were in the database that you copied will be in the new database copy with the same permissions and can log in.

You log in to your new database through the "Log in" menu which you can find by pressing the three dots on the leftside of your database copy.

Alternatively you can also go directly to one of the following links:




where you thus replace YourNewDatabase with the name you have chosen for the copy.

Delete database

When the available space is empty, the possibility of creating new databases disappears. You may then delete one of your existing test or training databases to create a new database copy.

You can delete your database copys by pressing the three dots on the left of your database in the platform administration. 

Deleting a database is definitive. However, you can always make a new copy of your sharp database.

Other information and restrictions

The following applies to your test databases compared to your sharp database.

Users and password management

Users are managed centrally for all customer databases in the Platform.

The same password and password management therefore applies to all databases, both sharp and copies for testing and training. If a user changes a password, the change applies to all databases.

All users who were in the database that you copied will be in the new database copy with the same permissions.

However, it is possible to change the permissions (User group) for users in the test databases without this affecting the permissions in the sharp database, as permissions(User group) are linked to separate databases. For example, you can give a user a higher authority in the education database before an education without affecting the permissions(User group) in the sharp database.


Users are managed centrally for all customer databases in the Platform. Your user licenses apply to platform users. This means that extra added users in test databases will be counted as users in a licensed manner.

Single Sign On (SSO)

Login with SSO will work in the copies as well.

User synchronization (AD sync)

The user synchronization only goes against your sharp database, so changes made to user data via your AD sync will NOT work in the copies. To include changes by users to a copy, we recommend that you make a new, updated copy of the sharp database.

Email settings

No e-mails will be sent from the test databases - all outgoing e-mails will be automatically deactivated for the copies.

Resource planning

The Resource Planning product will NOT work in the database copies. If you need a test environment for Resource Planning, contact support for suggestions.


Meetings will work in the copies, but note that you get to the sharp Meetings environment and not a test environment in the database copies - so you can NOT consider Meetings as a test environment in these copies.