Effective collaboration relies on giving the right people the right level of access. Our platform uses a tiered permission structure—Team, Project, and 3D Map—to ensure your data is secure while allowing your team to work freely.

This guide breaks down what each role can do at every level of your organization.

The Hierarchy: How Permissions Flow

Before diving into specific roles, it helps to understand how our platform is structured:

1. The Team: The overarching organization. Settings here affect everyone.
2. Projects: These act as folders to organize your work.
3. 3D Maps: The actual scans and data residing inside your Projects.

Permissions often cascade down. For example, a Team Admin automatically has full access to Projects and 3D Maps.

1. Team Administration

Who holds the keys to the organization?

Team administration is the highest level of access. These permissions are strictly reserved for the Team Admin.

The Team Admin is the only role capable of managing the organization itself. This includes adding new team members, creating or editing user groups, and adjusting global team settings. Perhaps most importantly, the Team Admin is the only user who can create new Projects.

• Key Takeaway: If you need to change a team setting, invite a new colleague, or start a brand new Project container, you must be a Team Admin.

2. Project Permissions

Who can manage folders and capture data?

Once a project is created by a Team Admin, the day-to-day management happens here. Project permissions control who can organize, share, and add new data (captures) to a project.

• Team Admin: Has full control over all project functions.
• Project Admin: Can’t create new projects, but has full autonomy within existing ones. They can share projects with others, share specific 3D maps, and capture new data (including OmniNotes).
• Project Member: Designed for contributors. They cannot share projects or maps, but they can view everything and Capture new 3D maps.
• 3D Map Editor & Viewer: These roles generally do not have project-level management or capturing capabilities.

3. 3D Map Permissions

Who can interact with the data?

This level controls what users can do inside a specific map. This includes tools like measurements, bookmarks, and annotations.

Full Access Roles

Team Admins, Project Admins, Project Members, and 3D Map Editors all share the same high-level capabilities here. They can:

• View and navigate the 3D Map.
• Export the map data.
• Save measurements.
• Create bookmarks and annotations to highlight key areas.

Read-Only Access

The 3D Map Viewer role is designed for stakeholders who need to see the site but shouldn't alter the data.

• View & Export: They can fully view and export the map.
• Measurements: They can take measurements, but they cannot save them permanently.
• Bookmarks & Annotations: They can view existing ones to see what the team is highlighting, but they cannot create new ones.

4. Published 3D Maps (Public Access)

Sharing with the world via a Published Link

Sometimes you need to share a map with someone outside your team who doesn't have a login. You can do this by generating a Published Link.

Anyone with this link is considered an Anonymous User. Their access is similar to a Viewer, but slightly more restricted to ensure data integrity:

• Viewing: Full access to walk through and view the map.
• Exporting: Allowed.
• Tools: They can take temporary measurements (unsaved) and view existing bookmarks.
• Restrictions: They cannot create annotations, save measurements, or create bookmarks.