You can import settings from one clash test into another to quickly update a test with previously defined settings. Most settings can be imported into another test, however some settings will not be compatible between different types of tests which will be noted next to the setting in the "Import clash test settings" window. Settings available for import include: clashing type, rules for ignoring clashes, grouping and groups naming, clash naming, location tags, clash view/issue screenshot, advanced issue automation rules (and location filters), clash test access rights, level model, grid models, and labels. 

To import clash test settings:

1. At the bottom of the destination clash test's settings panel, click Import settings. 

1. • You can also click More in the toolbar, then Import settings from another clash test.
2. Under From the clash test, select the clash test you want to import settings from. 
3. Select the settings you want to import. 
4. Click OK. 

Imported settings will overwrite any settings in the same fields in the destination test. Each setting is described in further detail in the sections below.

This is the name given to the clash test. It can be edited by clicking Edit  in the upper-right corner of the "Clash test name" field or by clicking More in the toolbar, then Rename when the clash test is selected. Click OK to save changes.

The clash test’s name will automatically be included in issue titles when clash groups are published to the issue tracker. The recommended name format  for clash tests is "A vs B", where A and B describe the selections that are checked for clashes.

A clash test defines two sets of objects (selections A and B) that are tested for clashing against each other. Each object in selection A is tested for clashing with each object in selection B to perform clash detection.

Selections A and B are generated from search sets during clash detection and the chosen search sets will be listed in the "Selection" field. Selections can be changed by clicking Settings  in the upper-right corner of the field. Click Done at the bottom of the window to save changes. Any number of search sets can be selected under selections A and B, however the chosen search sets must be shared.

When creating or editing the selections:

• Selection A includes the search sets selected under "Search sets A" or "Object A" (depending on the clashing type). 
• Selection B includes the search sets selected under "Search sets B" or "Required objects B" (depending on the clashing type).

In the search bar of each selection pane, you can search for specific search sets. When choosing search sets for selection, you can search the name or partial name of the search set. You can also use the following wildcards:

• * any number of characters
• ? any character

You can specify conditions for ignoring clashes through selecting predefined conditions or creating conditions for certain search sets and objects. The number of applied conditions, which includes counting each search set as an individual condition, will be listed in the "Ignore clashes" field next to Active rules. 

Conditions can be added, removed, or edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes.

There are three sections in the ignore clashes settings:

• Simple conditions
• Advanced conditions
• Add conditions

Simple conditions

The first section of the "Ignore clashes" window lists simple, preset conditions for ignoring clashes. To apply or remove one, select the condition. These include:

Option	Description
Ignore duplicates	If a clashing object includes a part of a mesh that is fully identical to a part of a mesh in the other clashing object, the clash is ignored.
Ignore if both objects are in the same model	If clashing objects A and B belong to the same Revizto model, the clash is ignored.
Ignore room objects	If a clashing object is a room, the clash is ignored.  This condition is enabled by default for all clashing types, except "Object A requires object B".
Ignore area objects	If a clashing object is an area, the clash is ignored. This condition is enabled by default for all clashing types, except "Object A requires object B".
Ignore zone objects	If a clashing object is a zone, the clash is ignored. This condition is enabled by default for all clashing types, except "Object A requires object B".
Ignore space objects	If a clashing object is a space, the clash is ignored. This condition is enabled by default for all clashing types, except "Object A requires object B".

Advanced conditions

The second section of the "Ignore clashes" window has options to create advanced conditions for ignoring clashes. These advanced conditions allow you to select search sets to make them more targeted. When choosing search sets for a condition, you can search the name or partial name of the search set. You can also use the following wildcards:

• * any number of characters
• ? any character

To edit the selected search set in any of these conditions:

1. Click edit next to Search sets in the condition you want to apply. Condition types are listed in the table below.
2. Select your search sets.
3. Click Apply.

Option	Description
Ignore objects that are in the search sets	If an object belongs to any of the specified search sets, clashes with that object are ignored.
Ignore objects A that are in the search sets	If an object from selection A belongs to any of the specified search sets, clashes with that object are ignored.
Ignore objects B that are in the search sets	If an object from selection B belongs to any of the specified search sets, clashes with that object are ignored.

You can remove a condition by opening an existing condition for editing and deselecting any selected search sets.

Add conditions

The last section of the "Ignore clashes" window has the option to add conditions for ignoring clashes. There are three types of conditions available, however you can add as many of these conditions as you want, including repeating condition types. 

To add a condition:

1. At the bottom of the "Ignore clashes" window, click Add condition for ignoring clashes.
2. Select the condition type. Condition types are described in the table below.
3. Fill in the condition type fields using either the dropdown menu or Edit .

Option	Description
Both objects have the same property value	If clashing objects A and B have the same value of a specific property, the clash is ignored. To set up the condition, select a category and a property from the dropdown menus.
Both objects are in the same search set	If both of the clashing objects belong to the specified search set, the clash is ignored. To set up the condition, click Edit  and select a shared search set.
Object A and object B are in specific different search sets	If an object from selection A belongs to search set A and an object from selection B belongs to search set B, clashes with those objects are ignored. To set up the condition, click Edit  and select a search set for both Set A and Set B.

You can remove a condition by clicking X in the upper-right corner of the condition's box.

When creating a new clash test, you will need to select a clashing type. This will dictate what is treated as a clash by clash detection. The applied clashing type and basic settings will be listed in the "Clashing type" field. Clashing types and settings can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes.

The full list of clashing types is only available when creating a new clash test. The clashing types are:

• Clashes
  • Hard clash: Objects clash if they touch or intersect. 
  • Tolerance: Objects clash if their penetration depth is greater than the tolerance.
• Clearance
  • Clearance: Objects clash if the minimum distance between them is less than the clearance. 
  • Directly above: Objects clash if the minimum distance above the object is less than the clearance.
  • Directly below: Objects clash if the minimum distance below the object is less than the clearance. 
• Inside: Objects clash if one object is inside the other.
• Duplicate: Objects clash if identical objects are placed in the same location. 
• Object A requires object B
  • Object A requires object B in proximity: Objects clash if the required object (object B) is not near object A.
  • Object A requires object B directly above: Objects clash if the required object (object B) is not directly above object A. 
  • Object A requires object B directly below: Objects clash if the required object (object B) is not directly below object A.
  • Object A requires object B inside: Objects clash if the required object (object B) is not inside object A. 

Once a clash test has been created, the clashing type can be changed to another clashing type that operates the same way (determining if an object is nearby versus determining if there is a collision or intersection). This means clashing types under "Object A requires object B" can only be changed to other clashing types under the same category, while all other clashing types can be changed to any other type except those under  "Object A requires object B".

Each clashing type will have individual settings that vary depending on what the clashing type is testing for. Clashing type settings can be edited directly in the "Clashing type" window. 

Clashing types include the following settings:

You can set up automatic clash grouping to group clashes together by specified criteria. The applied groupings and some basic settings will be listed in the "Grouping" field. Grouping settings can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes. 

There are three sections in the grouping settings:

• Clash grouping conditions
• Clash group name
• Clash name

Clash grouping conditions

Grouping conditions are set in the "Group by" window and define how your clashes are grouped. Successful use of grouping conditions can reduce the time required for manual clash analysis and eventually fully automate the creation of clash issues. If no grouping conditions are used, each individual clash will be represented as a group. 

It's common to have multiple grouping conditions which compliment each other to help create targeted issues that assignees can resolve. For example, choosing "Level" and "Zone" grouping conditions will create groups that contain clashes from the same level and the same zone. The group "Ground Zone A" will contain clashes from level "Ground" and zone "Zone A".

All new clash tests will have a proximity grouping condition set to 15m (or 49.2126ft) added by default. This can be edited or removed. 

To add a new grouping condition:

1. Click Add grouping. 
2. Select the grouping type. Grouping types are listed in the table below. 
3. If required, choose any settings for the grouping type, then click OK. Settings for each type are listed in the table below. Not all grouping types will require you to choose settings. 

Some grouping conditions can be edited by clicking Edit  next to the condition. If the condition does not have an edit button, the condition is not editable. You can remove a condition by clicking X to the right of the condition. 

Conditions are applied in the listed order, from top to bottom. To change the order, drag a condition by the icon.

The following grouping types are available:

Clash group name

Clash group names are based on the chosen grouping conditions. Most conditions will automatically add a placeholder to the Clash group name field. Words in braces {} are placeholders that will be replaced with the parameter values. For example, {Room} will be replaced by a room name.

While certain conditions will add placeholders to the name field, the Clash group name field is fully editable. You can edit the clash group name by adding and removing placeholders or using custom text:

• To add a placeholder, click the placeholder's button above the Clash group name field.
• To remove a placeholder, put the cursor in the Clash group name field and delete the placeholder.
• To add custom text, type it in the Clash group name field.

The clash group name will become part of the issue’s title when it is synced to the issue tracker.

Clash name

Clash names are based on the names of the clashing elements or geometries. A mixture of Element A, Element B, Geometry A, and Geometry B placeholder buttons will be available depending on the clashing type. Clicking a placeholder will add it to the Clash name field. Words in braces {} are placeholders that will be replaced with the names of elements or geometries. For example, {Element A} will be replaced by the name of the element A in the clash.

The default clash name is "{Element A} vs {Element B}" (or "{Element}" for "Object A requires object B" clashing types), however the Clash name field is fully editable. You can edit the clash name by adding and removing placeholders or using custom text:

• To add a placeholder, click the placeholder's button above the Clash name field.
• To remove a placeholder, put the cursor in the Clash name field and delete the placeholder.
• To add custom text, type it in the Clash name field.

You can use location tags to help identify and categorize clashes. All location tags are added to clashes by default. Available location tags include: level, room, space, Revizto zone, area, and grid intersection.

Location tags that are in use will be listed in the "Location tags" field. Tag selections can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes.      

To change the location tags for a clash test:

1. Deselect Calculate all location tags. This will be selected by default.
2. Select the location tags you want to use. Location tags are listed in the table below. 
3. Click OK. 

Option	Description
Calculate all location tags	Select to add all available location tags to clashes. This includes level, room, space, Revizto zone, area, and grid intersections. This will be selected by default.
Level	Tag clashes with levels. For additional options, see Level model.
Room	Tag clashes with rooms. If a clash point is inside a room, the clash is tagged with the room. If a clash point is outside of a room, but there are rooms directly under this point, the clash is tagged with the closest of these rooms.
Space	Tag clashes with spaces. If a clash point is inside a space, the clash is tagged with the space. If a clash point is outside of a space but there are spaces directly under this point, the clash is tagged with the closest of these spaces.
Revizto zone	Tag clashes with zones. If a clash point is inside a zone, the clash is tagged with the zone. If a clash point is outside of a zone but there are zones directly under this point, the clash is tagged with the closest of these zones.
Area	Tag clashes with areas. If a clash point is inside an area, the clash is tagged with the area. If a clash point is outside of an area but there are areas directly under this point, the clash is tagged with the closest of these areas.
Grid intersections	Tag clashes with grid intersections. Depending on the settings in the Grid models section, a clash is tagged with one or several grid intersections that are the closest to the clash point.

You can choose the settings for the default clash viewpoint and clash issue screenshots in this section. Clash viewpoint and issue screenshot selections can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes. 

Clash viewpoint and issue screenshot are managed by the following settings groups:

• Clash color settings
• Section box settings
• Camera settings
• Issue screenshot settings
• Issue sync settings

Clash color settings

This section contains the settings for the colors of clashing elements. Each clashing element is given a color in clashes to better illustrate the clash. 

Colors are set for the following elements:

• Selection A: Clashing elements from selection A. This defaults to red.
• Selection B: Clashing elements from selection B. This defaults to green.
• Resolved/Approved: All elements from resolved and approved clashes. This defaults to blue.

To edit any of the colors, click either the color or Edit  next to the element then choose your desired color.

Section box settings

This section contains the settings for the section box for the default clash viewpoint which is built around the intersection point of the clash. The section box will always be oriented XY, with no option to control or change the orientation. 

To change the section box settings, select the section box fit from the dropdown menu: 

• Fit to clash: Section box tries to include the clashing objects based on the intersection points. This might be limited based on level if the Box height is defined by neighboring level option is used. 
• Fit to level: Section box boundaries are determined by the levels and offsets around the intersection points of the selected clashes. 

After selecting the section box fit, adjust the individual settings to refine the section box. These settings are different for each fit style, as described in the table below. 

Camera settings

This section contains the settings for the camera focus, angle, and zoom on the clash. 

Issue screenshot settings

This section contains the settings that affect the clash issue screenshots. You will not see the issue screenshots when reviewing clashes in clash automation. The screenshots are generated during the clash detection and during the sync with the issue tracker.

Issue sync settings

This section contains the settings for how clash issue screenshots and clash viewpoints are updated during the clash detection. To edit a setting, select an option from the dropdown menu.

Option	Description
Update screenshots	This setting defines which issue screenshots are updated during clash detection. All: Screenshots of all issues generated by this clash test are updated. For changed clashes: If a clash changed since the last clash detection run, the clash issue screenshot is updated. This is selected by default. Changed except manual: If a clash changed since the last clash detection run and the clash issue markup was not changed in the issue tracker, the clash issue screenshot is updated. None: No screenshots are updated. Keep in mind that screenshot generation takes time. "None" will be the fastest option during clash detection, while "All" is the slowest.
Update viewpoint	This setting defines which issue viewpoints are updated during clash detection. All: Viewpoints of all issues generated by this clash test are updated. For changed clashes: If a clash changed since the last clash detection run, the clash issue viewpoint is updated. This is selected by default. None: No viewpoints are updated.

You can set issue automation in this section. These are the rules and conditions that govern what issues are created when syncing with the issue tracker. If issue automation has been used to set up an issue template, the issue fields and their settings will be listed in the "Issue automation" field. 

You can edit, add, and remove issue automation rules and settings by clicking Settings  in the upper-right corner of the field. From here you can switch between simple and advanced issue automation. Click OK at the bottom of the window to save changes. 

We recommend using simple issue automation for your first clash tests. Once you are familiar with simple issue automation, you can switch to advanced issue automation for more flexibility.

• General issue automation settings
• Simple issue automation
• Advanced issue automation

General issue automation settings

These issue automation settings apply to all clash groups from the clash test and are available in both the simple and advanced automation windows.

Option	Description
Sync clash groups with the following statuses	This setting defines whether clash groups that have the "Not reviewed" status are synced with the issue tracker. Ask each time before sync: Before each sync, you will be asked if you want to sync clash groups with the "Not reviewed" status. Reviewed clash groups are always synced. This is selected by default. Reviewed and not reviewed: Clash groups with both the "Reviewed" and "Not reviewed" statuses are synced.
Add clash group number to the issue name	If this is selected, the clash group number (the value in the "#" column in the clash test results) is added to the issue name.

Simple issue automation

Simple issue automation is used to create an issue template for all issues created from the clash test. This will be listed in the "Issue automation" field in the clash test's settings and will be the "Default issue values" if you use advanced issue automation. You do not need to fill in every issue field to set up simple issue automation. 

• To edit an issue field, click Edit  to the right of the field name. Issue fields are described in the table below. 
• To return a field to its default or inherited value, open the field for editing then click Reset or Restore. If a field value is inherited from a stamp template it will be marked with the icon next to the field name.

Option	Description
Stamp	Select a stamp template to apply to new issues generated from the clash test. The stamp template's issue fields will be applied to the issue template here. All of the stamp template’s inherited fields, except the stamp abbreviation and color, can be overridden if you do not want to use the stamp's values. This includes type, priority, deadline, assignee, watchers, and tags. You can add additional watchers and tags on top of the inherited values. To clear an applied stamp template and all associated fields, open the stamp field for editing then click Reset.
Type	Select the issue type you want associated with new issues generated from the clash test. This will control the available statuses for the issue.  For more information on issue types and statuses, refer to Managing custom issue statuses.
Priority	Select the priority of new issues generated by the clash test. If a stamp template is selected, the priority will be inherited from the stamp template. An  icon next to the field name indicates the priority was inherited. Setting a priority in this field will override the priority from a stamp template. If this field is blank and a stamp template is not specified or does not have a priority, the priority is set to None.
Deadline	Set the deadline for new issues generated by the clash test. To set a deadline, input the value, select the timeline (days, weeks or months) by toggling the options, then click Apply. The weeks and months specified here are calendar weeks (starting on Monday) and calendar months. For example, if you specify a 1-week deadline, the actual deadline is set to the next Monday.  If a stamp template is selected, the deadline will be inherited from the stamp template. An icon next to the field name indicates the deadline was inherited. Setting a deadline in this field will override the deadline from a stamp template. If this field is blank and a stamp template is not specified or does not have a deadline, no deadline will be set.
Assignee	Select an assignee for new issues generated by the clash test. If a stamp template is selected, the assignee will be inherited from the stamp template. An  icon next to the field name indicates the assignee was inherited. Setting an assignee in this field will override the assignee from a stamp template. If this field is blank and a stamp template is not specified or does not have an assignee, the assignee is set to the user that runs the sync with the issue tracker.
Watchers	Select watchers for new issues generated by the clash test. Multiple watchers can be added.  If a stamp template is selected, watchers will be inherited from the stamp template. An  icon next to the field name indicates watchers were inherited. Watchers can be added if the field is blank or in addition to watchers inherited from the stamp template. To remove individual watchers, open the field for editing, deselect the watchers you want to remove, then click Apply. Watchers that are inherited from a stamp template cannot be removed.
Tags	Add tags to new issues generated by the clash test. If a stamp template is selected, tags will be inherited from the stamp template. An  icon next to the field name indicates tags were inherited. Tags can be added if the field is blank or in addition to tags inherited from the stamp template. To add a tag: Type a new tag and select the checkbox next to it, then click Apply. Select the checkbox next to an existing tag, then click Apply. Tags that are inherited from a stamp template cannot be removed, however any other tags can be removed.  To remove an individual tag, clear the checkbox next to it, then click Apply. To remove all tags, click Clear selected items, then click Apply.

You can switch to advanced issue automation at the bottom of the window by clicking Switch to advanced automation. Advanced automation adds the option to create multiple issue generation rules that include a condition governing when the rule is applied. The issue template configured in simple issue automation will become the default issue rule applied when none of the conditions in advanced issue automation are met.

Advanced issue automation

Advanced issue automation allows you to configure location filters and multiple issue generation rules for a single clash test. Each rule is listed under "Conditional values" and is built on an "If/Then/Otherwise" model that includes the following fields:

• IF: A condition that is checked for each clash group.
• THEN: An action that is performed when a clash group meets the condition. The action will be to either "Create an issue" which is based on a specific template, or "Don't create an issue". 
• OTHERWISE: An action that is performed when a clash group does not meet the previous condition. The action will be to either "Create an issue" which is based on a specific template, or "Don't create an issue".

The order of the rules determines issue creation. When syncing with the issue tracker, for each clash group, Revizto applies any location filters, then the first rule where the conditions are met, then skips the rest of the rules. If a rule's conditions are not met, Revizto will proceed to the next rule until it finds one where the condition is met or it gets to the final "Otherwise" condition which is populated with the "Default issue values" if it creates an issue.

To change the position of an issue automation rule, drag a rule by the icon in the upper-left corner of the condition to the desired position.

You can switch to simple issue automation at the bottom of the window by clicking Switch to simple automation, however this will remove all advanced issue automation conditions. If you just want to edit the default values without removing advanced issue automation, click Edit  next to the relevant issue fields under "Default issue values". This will also change the fields in the final "Otherwise" condition if it creates an issue.

• Filter by location
• Conditional values (issue automation rules)

Filter by location

Location filters allow you to limit the issues created from the clash test by specific locations in the project. Multiple location types can be added as filters, including level, room, space, zone, and area. Filter by location can be used by itself, without setting any conditional values or alongside conditional values. 

To add a location filter:

1. Click Add filter.
2. Select the location type (by level, room, space, zone, or area).
3. At the top of the filter window, select Include or Exclude. This will define whether an issue is created (Include) or not (Exclude) based on the location.  
4. Select the checkboxes next to the locations you want to filter by. 
5. Select the issue creation criteria. This will determine how many clashes in a clash group must match the filter location in order to create an issue: at least one clash from the clash group or all clashes in the clash group. 
6. Click OK to save your filter. 

A filter for each location type can be added. Existing filters can be edited by clicking Edit  next to the filter. To delete a filter, click X to the far left of the filter. 

"Filter by location" settings can be imported into other clash tests independently of other issue automation rules.

Conditional values (issue automation rules)

Issue automation rules can be edited, added, and deleted under the "Conditional values" section. Any part of a rule can be edited by clicking Edit or the field's dropdown menu. When adding a condition, the issue template will automatically populate with the "Default issue values", however these can be edited within each condition. 

To add an issue automation rule:

1. Under "Conditional values", click Add condition. This adds a placeholder for a conditional rule and a final "Otherwise" condition.
   
   
2. If you want to name the rule, click Edit  next to "Condition".
3. In the IF field, select a condition type from the dropdown menu.
   • If a condition includes "objects A" or "objects B", it is checked only for objects from Selection A or Selection B. 

   If the test's clashing type is "Object A requires object B", selecting an object B here will not do anything. In "Object A requires object B tests, only resolved clashes will have both object A and object B.

4. In the that match(es) the search sets field, click Edit  and select one or several shared search sets. If you have many search sets, you can search for partial names or use the following wildcards:
   • * any number of characters
   • ? any characters 

5. If you want to add a second part to the condition, to the right of the IF field, click Add and select a condition type and matching search set. 
   • Condition parts are joined with either the operator AND (the condition is true when both its parts are true) or OR (the condition is true when at least one of its parts is true). Click the operator to toggle between them.

6. In the THEN field, select the action from the dropdown menu.
   • If you select "Create issue", you can specify some of the issue fields. Edit a field by clicking Edit  to the right of the field name. For descriptions of these fields, see Simple issue automation. 
7. If you want to add additional rules (conditions), click Add condition and follow steps 1-6 to create the condition.
8. In the final OTHERWISE field, choose an action from the dropdown menu. 
   • If you select "Create issue", you can specify some of the issue fields. Edit a field by clicking  to the right of the field name. For descriptions of these fields, see Simple issue automation. Editing an issue field here will change that field in the "Default issue values".

   The final "Otherwise" field is the final rule that is executred if all previous rules cannot be executed. It cannot be moved or deleted.

9. Click OK to save your advanced issue automation settings.

To delete a rule or condition, click X to the far right of the rule or condition. The last condition (the final "Otherwise" field) is only deleted when the last rule is deleted.

This section lists the project members and their rights in the clash test. Project administrators  and users with the “Clash administrator” access right can view, edit results, and edit settings for all clash tests in the project. The clash test access rights for these users cannot be changed here. Additional users may have access rights granted to them in a specific test from this setting. For more information on available clash test access rights, see Clash test access rights. 

Users with access rights to the clash tests and the privacy settings of the test will be listed in the "Access rights" field. Some access rights settings can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes. 

To edit a project member's access rights in the clash test:

1. Select the project members whose access right you want to edit. Some project members, such as project administrators, cannot have their clash test access rights changed. 
2. Click More  in the upper-right corner of the field. 
3. Select the new role for the project member from the available options. 

The user's clash test role will be automatically saved. 

You can also set the privacy of the clash test using the Clash test privacy dropdown menu:

• Private: The clash test will only be visible to project members with a project administrator role, "Clash administrator" rights from their project role, or the "Test administrator" or "Test results editor" role in the specific clash test.
• Public: The clash test will be visible to all project members with the "View public clash tests" access right as well as project members with any administrator roles or the "Test administrator" or "Test results editor" role in the specific clash test.

This section contains the labels assigned to the clash test which can be used for filtering. Active labels will be listed in the "Labels" field. To add or edit labels:

1. Click Settings  in the upper-right corner of the field to open the labels menu. 
2. Create, edit, or remove labels.
   • To create a label, type the label name, then select the checkbox next to it.
   • To add an existing label, select the checkbox next to it.
   • To remove a label, clear the checkbox next to it.
   • To remove all labels, click Clear selected items.
3. Click Apply.

Multiple labels can be added or removed at a time. Removing a label will not delete it from the entire project as, currently, labels cannot be deleted from a project.

This section contains the settings for the levels that are used as location tags in the clash test. The level model will be listed in the "Level model" field. Levels can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes. 

When setting levels to use as location tags, there are two options:

• Use project levels: The clash test uses the levels defined in the project. 
• Use custom levels: The clash test uses levels chosen for the clash test. You might want to use this option if your project includes several buildings, each with its own levels. 

To edit either level option, click the edit or configure button then choose the level settings described in the table below.

This section contains the settings for the grids that are used as location tags in the clash test. The grid model  will be listed in the "Grid models" field. Grids can be edited by clicking Settings  in the upper-right corner of the field. Click OK at the bottom of the window to save changes. 

When setting grids to use as location tags, there are two options:

• Use project grids: The clash test uses the grids defined in the project. 
• Use custom grids: The clash test uses grids chosen for the clash test.

To edit either grid option, click the edit or configure button then choose the grid settings described in the table below.