Users are grouped together under a common project, function, or role to create a team. Teams are used to organize and define the scope of access to the site hierarchy. 

A team is given access to any level of the site hierarchy. This is controlled by the site manager.

Note: Site Hierarchy: Space > Site > Floor > Survey Group (optional) > Survey

team2.png

 

In the example below, Team A has full access to Site A, which would automatically give them full access to all of its plans, survey groups, and surveys. However, Team B only has access to the survey group and therefore access is limited to only surveys within the survey group.

Graphics_for_user_manual__10_.png

While Multiple teams have access to a single survey, however, it is important to note that the 360 images (points) and data (tags, tracking tour, comments, etc) are separated. This means that even though teams A, B, and C all have access to survey A, any tags or comments created by team A is shared with Team A only. 

team.png

 

Example Scenarios

Example A

A team is created based on a single project.

For example, there is new construction of a data center with multiple cross-functional stakeholders. Some are internal and others are external. A team is created with all of the appropriate stakeholders with access given for that specific site only. 

Graphics_for_user_manual__15_.png

Example B

A team is created based on a wider scope.

This would generally be for a specific functional group that may need access to multiple sites for their work. For example, the marketing team of the organization needs access to certain areas across the entire portfolio so that they can feature it publicly. The scope is given or removed as needed.

Graphics_for_user_manual__16_.png

Example C

A team is also created based on a specific role.

When an organization has a large number of distributed buildings to maintain they can utilize the local teams on-site to capture and conduct the surveys of their respective sites. This information is then being shared with the rest of the teams in the Space without giving the local teams access to sensitive information that may be shared by other teams. 

In this case, creating a "surveyor" team that has full access to all of the sites, which allows them to capture as needed without getting access to the data of other teams. 

Graphics_for_user_manual__17_.png

Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.