A Shared View creates a publicly available URL that provides read-only access into a filtered subset of your data within an app. Enabling a Shared View allows you to publish a selection of data with Clients, Stakeholders, or the Public. This feature allows users to share data while hiding certain parts of their data that may be sensitive and proprietary.
When a user elects to share a view, the provided URL contains a unique access token. You can use this token to retrieve data in one of the following formats: CSV, JSON, GeoJSON, KML, and (Esri) Feature Service. Be cautious when sharing this URL as it contains all the record information available within that View. If you wish to append certain parts of your data being visible through the shared URL, make sure that you save the view to reflect what you want publicly visible. When a view is changed from “Shared” to “Private” the unique access token is deleted and the shared URL becomes invalid.
In order to share a view, first either “Save View” or select “Update View” while in the Record Editor.
Views are by default set to “Private”. If you elect to a “Shared” view make sure to save or finish creating the view for the URLs to be valid.
Plans & Permissions
Shared Views are currently available on all plans. In order to see, configure, and use Shared Views, a new custom role must be created in your organization and add the member permission "Change Organizational profile." By default, the only role to have the above permission is the Owner system role.
Accessing Media Files
Photos, videos, audio, and signature files are also accessible via a Shared View. This URL links to a landing page where you can view that record's media files individually.
Data Formats & Map Embeds
Shared Views provide direct data access in a variety of standard formats, which can be embedded into a website with an
iframe, shared via social media, and more.
A simple flat file format that can be used directly with common spreadsheet software like Excel or as an import into other database and analysis systems. CSV feeds are also great for scripting custom integrations.
The JSON option returns Fulcrum's standard record format, which is used by the REST API records endpoint. This is the format used for creating and updating records via the API.
GeoJSON is an open standard JSON-based format designed for representing simple geographical features, along with their non-spatial attributes. It's popular with desktop GIS and web mapping applications.
KML is an open standard XML-based format made popular by Google Earth.
This option provides an Esri Feature Service endpoint with a single Feature Layer, representing the view’s records. This read-only layer can be queried directly, referenced in a web map, or added to desktop GIS.
You may add
?repeatable=repeatable_data_name at the end of the url to get the view of the repeatable data. However, filtering the repeatable data is not yet available.