- Getting started with Airtable
- Introduction to Airtable basics
- Contacting Airtable Support Updated
- Airtable home screen
- Glossary of Airtable terminology
- Airtable technical requirements
- Feature differences between Airtable on desktop and mobile
- Airtable keyboard shortcuts
- Using Markdown in Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Airtable Automations
- Automations Overview
- Automation feature walkthroughs
- Integrated automation walkthroughs
- Airtable automation walkthroughs
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Automation Triggers
- Airtable Triggers
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Airtable automation trigger: When record updated
- Airtable automation trigger: When record enters view
- Airtable automation trigger: At scheduled time
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received Updated
- Integrated Triggers
- Airtable Triggers
- Automation Actions
- Airtable Actions
- Airtable automation action: Send email Updated
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Airtable automation action: Run a script Updated
- Airtable automation action: Generate with AI
- Integrated Actions
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Airtable Actions
- Airtable Bases
- Using Airtable Cobuilder
- Airtable bases overview
- Creating and managing Airtable bases
- Structuring bases in Airtable
- Moving bases between workspaces in Airtable
- Creating and managing tables in Airtable
- Creating Airtable base share links
- Importing third-party data into Airtable
- Using insights in Airtable
- Troubleshooting Airtable base performance
- Airtable Betas
- Collaborating in Airtable
- Airtable Enterprise Support
- General Enterprise information
- External badging in Airtable
- Using app library and components in Airtable Updated
- Ask an Expert beta overview
- European data residency at Airtable
- Airtable user groups overview
- Airtable Enterprise API
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Accessing Enterprise audit logs in Airtable
- Set up Jira Server / Data Center to connect with Airtable
- Admin panel pages
- Airtable admin panel overview
- Users - Airtable enterprise admin panel
- Airtable admin panel user details
- Groups - Airtable admin panel
- Workspaces - Airtable Enterprise Admin Panel
- Bases - Airtable admin panel
- Interfaces - Airtable admin panel
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Reports - Airtable admin panel
- Settings - Airtable admin panel Updated
- Managing Enterprise organizations
- Managing Enterprise admins in admin panel
- Using Organizations
- Organization branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub: Org unit assignment with user groups Updated
- Deactivating, removing access, and reactivating users in the admin panel
- Managing user access to workspaces and bases
- Airtable Enterprise Key Management Updated
- Custom terms of use New
- Enterprise SSO
- General Enterprise information
- Airtable Extensions
- Airtable Fields
- Fields Overview
- Attachment
- Date-based fields
- Formula
- Getting Started with Formulas
- Formula Foundations
- The essentials of Airtable formulas
- Formula writing tips for beginners
- Troubleshooting formulas
- Basic calculations
- Conditional statements
- Logical arguments
- Working with dates
- Displaying DATETIME_FORMAT using the date field in Airtable
- Working with date functions in Airtable
- Calculating the difference between dates in Airtable
- Supported DATETIME_DIFF unit specifiers in Airtable
- Supported DATETIME_FORMAT format specifiers in Airtable
- Using the DATETIME_PARSE() formula in Airtable
- Working with timezones
- Record functions
- Text functions
- Numeric functions
- Common Solutions: Beginner
- Common Solutions: Intermediate
- Common Solutions: Advanced
- Long Text Field
- Linked Record Field
- Linking records in Airtable
- Limiting linked record selection to a view in Airtable
- Dynamic filtering in linked record fields
- Linking to one, many, or a subset of Airtable records
- Converting existing fields to Airtable linked records
- Reordering record links in Airtable
- Understanding linked record relationships in Airtable
- Number-Based Fields
- Other Fields
- Rollup, lookup, and count fields
- Select and user fields
- Integrating with Airtable
- API
- Getting started with Airtable's Web API
- Creating personal access tokens
- Airtable Webhooks API Overview
- Service accounts overview
- Airtable Web API - Using filterByFormula or sort parameters
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- URL length limitations for web API requests
- Integration services
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Developer tools
- API
- Airtable Interface Designer
- Interface Designer overview articles
- Interface layouts
- Interface elements
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Learning and Resources
- Managing Airtable
- Airtable Policy
- Airtable Records
- Airtable Sync
- Airtable Views
- Airtable Workspaces
- Print
- Share
- DarkLight
- PDF
All paid plans | |
| |
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading | |
Extension - Extensions are modular components that add visuals or functionality to a base, and were shown in the base's dashboard. Users can create custom extensions, or they can use extensions created by Airtable or other open-source extensions. |
Create a linked record field
The org chart extension can visually represent the hierarchical relationships between like items. You can use it to map the relationships between individuals at an organization. In this article, we'll use the Marketing org chart template to demonstrate this feature.
To use the org chart extension, you'll need to have a table containing at least one linked record field configured to link to the same table (e.g. a self-linking linked record field). In our example, this field will be used to associate, or link, employees to their managers.
If you don't have an existing linked record field, start by clicking the + button (next to your last existing field) to create a new field. Choose the "linked record" field type, and make sure to choose the same table where you're adding the field to link records to (as opposed to linking to a different table).
The org chart extension only works with records linked in the same table; it is not intended for use with records on different tables.
Decide on the linked record relationship type
Once you've added the linked record, you'll need to decide on its relationship type in the context of the organizational chart. Because an organizational chart is a hierarchy, a common way to describe the relationship between one record and another can either be as a "child" or as a "parent". Using our employee org chart as an example, there are two scenarios you could choose from.
Scenario 1: Parent field
An employee (the "child") can be linked to their manager (the "parent"). In this scenario, the linked record field for any given employee will contain a link to the record with their manager's name. The linked record field is considered a "parent" field (which will be covered more in the org chart settings).
Scenario 2: Child field
The other scenario is to link managers (the "parent") to each of the employees (the "child"). With this approach, each employee would be added as a linked record next to their manager. The linked record field is considered a "child" field in this scenario.
How you configure the linked record field is up to you and what works best for the information in your base. Once you've decided you can link the appropriate records and add the org chart extension.
Add the org chart extension - Click the "Extension" button at the top-right-hand side of your base. Then, select "Install an extension" and install the org chart extension from the extension marketplace.
Configure the extension settings - After installing an org chart extension, you'll automatically get brought to the new extension's settings page. From here, you can specify the table and view containing the records that you'd like to map onto your org chart.
Choose scenario- Next, you'll need to pick a self-linking linked record field to serve as the Relationship field, and specify either Children or Parent as the Relationship type. We'll use the same two scenarios as described above.
Scenario 1: If the record(s) that are being linked to are hierarchically above the record that is being linked from, pick "Parent" as the relationship type. In our example, this means that the linked record field would contain a link to each individual employee's manager.
Scenario 2: If the record(s) that are being linked to are hierarchically below the record that is being linked from, pick "Children" as the relationship type. In our example, this means that the linked record field would contain a list of employees linked to individual managers.
Record coloring - If the view associated with the org chart has conditional record coloring, you can also choose to color-code the org chart cards with the same colors.
Secondary fields - Lastly, you can choose to add secondary fields, which will add some additional information onto each record card based on the field of your choosing. You can change the order in which the secondary fields appear on the cards by clicking and dragging the drag handles or remove a secondary field by clicking the X button.
View your org chart
You can navigate your org chart by clicking and dragging, and you can zoom in or out by clicking the zoom buttons in the top left corner of the extension.
Clicking on a record card will open up the expanded version of that record. This is where you can update fields such as Name, Title, and Department on the record from within the Org chart extension itself. You can also update these fields on the grid view, and they will automatically update the Org chart extension.
You can expand or contract records by clicking the chevron buttons below the parent records/above the child records. If you hold down the key while clicking, it will expand/collapse all nodes in a subtree.
Exporting and printing your org chart
To download your org chart as a PDF, click the Export PDF button.
Once you've exported the PDF, it'll appear in the default downloads folder designated by your internet browser or in the preferences for the Airtable desktop extension. You can then open this PDF (using your preferred PDF reader application) and print it.
How to fix loop errors
If you accidentally link a record to itself, you'll receive a message that there is a loop error. This error occurs because in the org chart extension, a record must be linked to a different record other than itself (more details about this relationship are covered above). For example, if your org chart is setup as a manager <> employee relationship, an employee cannot be their own manager.
This error can be fixed by removing the linked record(s) that is linked to itself.
FAQs
How do I remove someone from the Org chart I'm building?
While setting up the Org Chart extension you have the option of choosing the view you'd like the extension to pull data from. If you'd like to exclude someone from your Org Chart you can create a new view that filters out individuals based on a condition you set. Then, in the Org Chart extension's settings page you can choose the newly created filtered view to display in your extension.