AirTable accounts#
Mostly deprecated
The only thing we actively use AirTable for is tracking team salaries and contracts. Most other historical content in AirTable is no longer maintained.
This page covers our AirTable account, how to access it, and what we use it for.
Read-only access to the AirTable#
Here’s a link to our primary AirTable workspace.
This is a read-only link, valid for any @2i2c.org address.
If you need edit permissions, use the shared AirTable account.
Edit access to the AirTable#
We have a single account on the “Pro” plan of AirTable. It is the only account with edit permissions.
To access this account, use our shared passwords account for credentials.
Salaries base#
We use a single AirTable base to track team salaries and internal contracts.
The base has three linked tables:
- People
Everyone who currently or has historically worked at 2i2c.
- Roles / Titles
Roles and levels at 2i2c with a start/end date and salary, capturing how roles evolve over time.
- Contracts
Internal team contracts that link a person to a role and represent an active contract.
For our salary policy, bands, and benchmarking process, see Compensation and Benefits.
How to update roles and contracts#
Every year, we update our roles to reflect cost of living (COLA) adjustments and changes to descriptions. Follow these steps:
For each role and for each contract that will continue:
Duplicate it
Update the Start / End date (usually July 1st -> June 30th of the next year)
Update the salary / description if necessary
Link the old item to the new item via the “Renewed by” field in the old item.
AirTable structure overview#
The rest of this page describes an overview of AirTable’s structure in general.
Bases#
A base is the highest unit of organization in AirTable. They are generally categorized by a broad topic that might have a number of related datasets inside.
Each base has three types of elements in it: data, automations, and interfaces. Each is described below.
Data#
Contain tabular datasets that make up the content in a base. These are kind of like databases, in the sense that they have typed columns, and each row represents a single “record” within that table.
A base usually has many tables of data, and these can then be interlinked with one another.
For example, we have our Contracts table as well as our Invoices table in the same base.
This lets us link records in Invoices with those in Contracts based on a unique ID in each.
Views#
Views are ways to filter, group, and subset your data for visualizing purposes. They do not change the underlying dataset, they merely provide a way to look at it a different way. For example, our Invoices table has two views:
URL structure#
The URL structure of data generally looks like this:
https://airtable.com/< BASE ID >/< TABLE ID >/< VIEW ID >
Automations#
Allow us to perform certain actions on a schedule or repeated after a certain condition.
For example, we have a Link Invoices automation that automatically links new records of Invoices with their respective Contract every hour.
Interfaces#
Are dashboards that provide quick and visual summaries of the tables in a base. For example, we have a Monthly Invoices dashboard that summarizes major financial invoicing and contracts activity each month.
Example screenshot#
Below you can see an example of the Accounting base, with the three major sections for Data, Automations, and Interfaces at the top.
Below these, you see multiple tables corresponding to different kinds of data (Contracts and Invoices, for example).
For the active table, we can see multiple views of that table to the left, corresponding to different subsets of data.
