Skip to main content

Connect: Asite

Sync your data from Asite

Written by Holly Tyler

Our Asite integration allows you to connect your Common Data Environment (CDE) to Sensat to automatically access files so they can be visualised together seamlessly with all your other project data. This allows you to maintain a single source of truth and have confidence that content visualised in Sensat is always up-to-date, covers all disciplines, and retains its metadata.

Key features

  • Visualise geolocated data stored in your CDE seamlessly together.

  • Automated hourly sync to Sensat based on your approval workflow.

  • Eliminate the risk of data being outdated or missing entirely from Sensat.

How it works

An administrator must first enable the integration and configure which folders to sync (see the steps below).

Every hour, changes made to files in Asite will sync to Content in Sensat. This includes new files, revisions, changes to any file attributes, and deletions.

Once files have been synchronised to Sensat, they can be added to workspaces and visualised in the same way as manually uploaded files.


Set-up and Configuration

1. Create a Service Account

For security and stability, we require a Service Account.

  • Role requirements: The account must have "View" and "Download" permissions at a minimum for all folders intended for sync.

  • Project Access: Ensure the service account is invited to the specific Asite project(s) you wish to integrate.

  • API Access: Verify that API access is enabled for this account within your Asite environment settings.

2. Share credentials

Once the account is ready, provide the following details to your Sensat Contact:

  • Service account email/username

  • Password

  • Asite Cloud Instance (e.g., UK, US)

3. Map your folders

To ensure the right data lands in the right place, we use a precise folder mapping system. Only the folder you map will be pulled across. If you request an Asite sync, your Sensat Contact will provide a template to provide the folders you require and where they should map to in Sensat.

4. Connection

Once we receive your credentials and mapping template, our team will configure the backend bridge.


Working with synced content in Sensat

Viewing synced folders in Content

  1. Synced folders will be displayed in Content. They can be identified by the "sync" icon

  2. You can click on synced files to view their attributes

    • Any specified attributes will be shown if they are populated in ACC.

  3. To add a synced folder or file to your workspace, follow the usual add content flow. Learn how here.

Adding and removing synced content to Workspaces

When you add layers to a Workspace that are synced from a Common Data Environment (CDE), they stay synced with the source. Here's how updates and removals are handled:

Automatic updates

If a synced layer is updated in the CDE (e.g., a new version is available), those changes will automatically appear in all associated workspaces too. This happens the next time the CDE syncs with Sensat.

Adding new files

If you link a synced folder to a workspace, any new synced files will also update in the workspaces it is linked to. Learn more about adding content to workspaces.

Removing files

If a file is deleted from the CDE, it will be automatically removed from the Content page and any workspaces it's been added to. This happens the next time the CDE syncs with Sensat.

Access levels for synced content

Content synced from a CDE has more limited access options compared to uploaded content (e.g., it cannot be edited). However, its settings are managed in Content and apply across all Workspaces, just like other project content. Learn more about content permissions here.

Full access

Can edit

Can view

No access

Can view in Workspaces

✔️

✔️

✔️

X

Can download / export

✔️

✔️

X

X

Can manage access

✔️

X

X

X

Can move folder in Content

✔️

X

X

X

Can edit

X

X

X

X

Can add content to the folder

X

X

X

X

Can organise content or create subfolders

X

X

X

X

Can delete from project

X

X

X

X


Did this answer your question?