📖 Stacker Terminology

A guide to the language used in the Stacker ecosystem.

Term

Description

Example

Workspace

This is essentially an account for your entire business. It contains all your apps, data sources, and team members.

Each workspace can have multiple users and apps.

Acme Corporation will invite its team members to the Acme Corporation workspace.

Data source

A connection to a service or platform where you store your data.

Airtable, Google Sheet, Intercom, Stripe

App

A single application inside a workspace.

Your support team's CRM, your sales team's prospecting task management system

Widget

Components that can be added to a layout that a user will interact with.

Fields, Highlights, Banner, Record List, Embed

Table

Data organized in columns (fields) and rows (records). You can think of this like a tab of a spreadsheet.

A table of customers in Airtable, a table of tickets in an Airtable base, a tab of orders in Google Sheets, customers in Stripe, subscriptions in Stripe

Field

One type of data in a table

Visually, this is typically a column of data.

A customer's email, a client's phone number, an order number, a drop down of a user role, a project description.

Linked Field

A field that's been linked to another field in a different table to indicate a relationship.

Configuring the "emails" field in a customers table as a linked field with "emails" from a payments table will allow you to configure Stacker so a user only sees payment data related to their email.

Configuring the "project name" field in a project table as a linked field with "project name" in a task table will allow you to configure Stacker so a user can easily view different tasks for a particular project.

Configuring the "emails" field from a leads table as a linked field with "customer email" in a customers table will allow you to configure Stacker so a user can view lead data related to a particular customer.