⚙️1. Mapping configuration
Learn how to create your first Skin CMS Mapping
Last updated
Learn how to create your first Skin CMS Mapping
Last updated
An account and a base in Airtable
Airtable personal access tokens for the base you want to connect
you must have Owner
or Creator
role for the given base in Airtable
3DVista virtual tour
Once you purchase a Skin CMS plan on 360creators.com, you will gain an access to the Skin CMS Mapper. Skin CMS Mapper is a simple tool you will be using to create and manage your mappings.
Mapping is essentially the connection between the Airtable table and your 3DVista virtual tour.
Mapping contains the information of which Airtable field (column) is mapped to which 3DVista component (skin element).
When you create a new mapping, first you need to set up the configuration:
Name of the Mapping. We recommend using something related to the project you are working on.
You can create Airtable personal tokens on Airtable's Personal access token management page. In order to create a mapping you need to create two personal access tokens - one for Mapper and one for 3DVista.
This personal token will be used by the Skin CMS Mapper to read your Airtable table's schema (structure) in order to access the names of the fields (columns), their types and configurations which are necessary for creating the mappings.
Create a personal access token with the following scope:
schema.bases:read
This personal token will be used in the virtual tour to fetch the data from the Airtable table. Therefore, as it's publicly available, it is extremely important to select the correct scope which in this case is:
data.records:read
With the data.records:read
scope the virtual tour visitors will be able to read the data from all tables within the base for which the personal token is created (on the example above the base is: Skin CMS - Matej demos). This might include giving away an access to other tables that are not being used in the virtual tour but are part of the base. That's why we recommend making sure that the base does not contain any sensitive information. Users won't be able to edit nor delete the data, only read it.
An Airtable link to your table looks something like this:
We are only interested in the first part after the https://airtable.com/
which in the example above is apphSS5HBXphqjWYw
- that's the base ID.
The Airtable table name in the example is Table 1
:
Once you are done, you can hit the Save and connect Airtable
button and continue to the 2nd step.
Whenever you change your Airtable structure, you will need to Save and connect Airtable
to see the updated fields in the Field Mappings
section.