Project settings in Models

1. From the Setup menu, select Project Settings.
2. Click Models.
3. Configure the available project-wide settings as required.

Configure Model Stack Fields

• Under 'Registered model stack fields' customize which fields are shown when viewing Models uploaded from the document register.
• See Configuring Model Stack Fields.

Allow other organisation's to manage Model Coordination activities

This setting is available for Model Coordination projects only. It allows Project Owning Organizations to nominate who can manage the following:

• Project viewpoints
• Clash spaces
• Zones
• Project object saved searches (from the March 2024 release.)

Granting management access

There are two steps to allow someone to manage Model Coordination activities:

1. Add their organization to the list of orgs under Model Coordination Management. Note: By default, the project-owning organization is already listed and cannot be removed.
2. The user must also have the Model Coordination Administrator (formerly Design Issues Administrator) permission granted to their user role, otherwise, they will not be able to manage viewpoints, object saved searches, clash spaces, and zones. They may need to ask their Organization Administrator to grant this permission. Note: this permission must also be granted to users in the project-owning organization.

Disable local file model stacks

• Ensures the project team upload and manage models using the Document Register, providing audit trails, and inclusion in workflows.
• Under the Models heading uncheck Enable local file Model Stacks to remove the ability to upload local files.
• This means users on your project can only use the Document Register for uploading Models. 
• Older local file Model Stacks are still visible, but cannot be updated with new revisions. Use the Document Register for uploading Models. 
• You can re-enable Local file Model Stacks if access is required, however, we recommend you plan to disable this feature permanently.