This diagram illustrates Sensat’s platform architecture and how its core elements - Content, People, and Workspaces - interact within a project.
You can also watch our quick getting-started video to understand how everything works together.
Project-level
At the highest level, within a Project, there are two core components:
Content
This is where all of your project data is stored and managed within the platform:
It includes all uploaded, synced, and streamed data - Learn more.
It also includes published markups - annotations or measurements that have been published from a workspace.
Data permissions - access to content is controlled here and applies across the entire Platform.
People
This is where you can view, manage, and invite new members to the project:
See all project members along with their details and assigned project roles.
A member’s project role defines what actions they can take at the project level, for example, creating workspaces or inviting new members.
User groups can also be seen and managed here.
These two project-level components (Content & People) feed into the Workspace-level.
Workspace-level
At the workspace level, projects can contain multiple workspaces. These are primarily used for visualisation and collaboration:
Access to each individual Workspace is controlled. Only those it has been shared with can see the Workspace, and what they can do within the Workspace is controlled by the level of access they are given - Learn more.
Workspaces contain a subset of curated data, chosen from the Content repository. Different Workspaces can have different sets of data depending on their purpose. The Content is not duplicated; it is consistent across all workspaces, so that a change made in one place is reflected everywhere.
If you want to make a copy of a layer or model, you can use the Duplicate functionality within a Workspace. Duplicates that are created within a Workspace live only inside that Workspace unless they are "Published" to Content, where they can then be pulled into any other workspace in the same way as other Project content.
Summary
Content and People are managed at a Project level.
Selected content and people are added to individual Workspaces for collaborative work and editing.
Markups made within Workspaces are unpublished by default, but you can choose to publish them back to the main content repository.
Access controls - including Data Access, Project Role, and Workspace Access -are applied at multiple levels to manage permissions and ensure security.