Skip to main content
A project groups related tables, apps, and automations in one place. Each space can contain multiple projects, and each project has its own resources and collaboration permissions.
Project is the product name for the resource called base in the API and CLI. API fields such as baseId, the bse ID prefix, and /base/... URLs stay the same.
For users unfamiliar with projects, you can think of them as workbooks in Excel, where each workbook can contain multiple sheets.

​
Create and Manage Projects

​
Adding a Project

  1. Enter a space and click Projects in the sidebar
  2. Click “Create Project” in the upper right corner
Create a project When you start a chat in a new project, AI names the project based on your message. If the project already has a name, AI leaves it unchanged.

​
Creating a Project from a Template

The template center holds projects you can use as they are. Open it from Template in the space sidebar, or choose From template when you create a project. In the template detail, click Install, choose New project (a new project named after the template) or Add to an existing project (a project you can edit), then click Install. When you install from a share link, you pick the space first. Every template gets its own folder inside the project, and whether it comes with sample records is up to the template’s publisher. If the template’s automations need external platforms connected, the template detail lists those platforms. After installing, Teable opens the project’s chat and shows a Connect accounts to get the template running card above the input box:
  1. Connect accounts platform by platform. When a platform needs more than one account (for example, two YouTube channels), each account gets its own row and is bound separately. If you have connected only one account for a platform under Settings → Integrations, it is bound automatically; if you have connected several, click Authorize mine to choose which one to use. For a platform you haven’t connected yet, click Connect account to run an OAuth flow.
  2. Entries that need an API key are listed under Keys to enter. Click Enter to create one, or pick a secret you already saved.
  3. Click Start. Every workflow and routine whose credentials are complete is switched on. Those that run on a schedule take their first run right away, which you can follow in the run history; those triggered by a third-party app event wait for the first event.
Click Later to put the card away for now. As long as the project still has an integration that is not connected, the page shows N integrations are not connected; click Connect to fill it in at any time. See Credentials and Integrations.

​
Managing Installed Templates

In the space sidebar, click … next to a project and choose Installed templates to see the status of each template in the project (Needs setup, Running, Needs attention, or Off), switch its automations on or off, or click Uninstall. Uninstalling switches off and removes its automations and routines, moves the tables, apps, and other items it brought to the trash, and deletes its folder once the folder is empty.

​
Publishing to the Template Center

Click the project name in the top-left corner, or click … next to the project in the space sidebar, and choose Publish to Template Center. Fill in the name, description, and cover, choose what it includes and whether to include sample records, then click Submit for review. You can click Withdraw while it is under review. Once approved, the template is listed; if it is sent back, the notification includes the reviewer note. Later changes to the project need a new submission, and until that is approved, anyone who installs the template still gets the current version. To take a listed template down, click Unlist; existing installs are unaffected.

​
Renaming/Deleting a Project

  1. Enter a space
  2. Hover over a project
  3. Click the ”···” button to open the menu
  4. Click “Rename” or “Delete”
Rename or delete a project

​
Organize Resources in a Project

Click the Show resources folder button next to a project name in the space sidebar to browse its directory to the right of the chat. The directory contains tables, apps, automations, and routines, which you can organize in folders. Resources open in tabs; click + (New tab) at the top of the pane to return to the resource list. Common operations include:
  • Create folders: Create folders in the project directory to group related resources.
  • Move resources: Drag tables, apps, or automations into folders, or drag them to reorder.
  • Organize hierarchy: Folders can contain child nodes. Keep the hierarchy shallow enough for easy navigation.
  • Add descriptions: For tables, apps, and automations, click Add description under the resource name in the header. Use descriptions to record purpose, owner, handoff notes, or usage rules. Teable opens a description the first time you open its resource, and once more after it changes.
  • Check node info: Open a resource’s ... menu and choose Node info to view the folder, table, automation, or app ID, plus created and modified information.

​
Command Palette

Press Ctrl + K (Mac: Command + K), or click the search icon at the top of the left sidebar, to open the Command palette:
  • Jump to a resource: Type a name to find tables, views, apps, and other resources. With nothing typed, the palette lists Recently visited resources and views. If nothing matches, you can create a table with that name, or use Search in current table to look for what you typed.
  • Run a command: Type a command name to run it, or start with > to search commands only. Commands create tables, dashboards, apps, automations, routines, folders, or views, invite collaborators, switch the appearance, or open settings and keyboard shortcuts.
  • Ask Cuppy: Inside a project, type a question and choose Ask Cuppy to send it to AI Chat along with the current project, table, and view. See AI Chat.

​
Duplicate a Project to Another Space

Step 1: In the space, select the project you want to duplicate; Step 2: Click the menu icon and select the Copy Project option; Step 3: In the popup, choose the target space. You need Creator permissions in that space. For larger projects, Teable shows progress in the duplicate dialog while it copies the project structure, records, and attachments. Keep the dialog open until the copy finishes. Revision history and collaborators are not copied. If the project contains Link, Lookup, Rollup, Conditional Lookup, or Conditional Rollup fields that point to another Space, Teable shows the affected fields before duplication. If you continue, Teable converts those fields to Single line text in the duplicated project. Duplicate a project to another space

​
Move a Project Between Spaces

If you have the required Space permissions, you can move a project to another Space. If the move would leave relationship-based fields pointing across Spaces, Teable warns you and lists the affected fields. When you confirm, Teable converts those fields to Single line text as part of the move.

​
Move Resources to Another Project

You can move tables, folders, apps, automations, and routines to another project in the same Space. Their data and configuration stay the same; only the project they belong to changes.
The pre-move check cannot guarantee that it finds every reference. Some references in automation scripts or app code can be missed. After moving, make sure to check that your workflows are not affected, and adjust anything that is.
  1. In the project directory, open the resource’s ... menu and select Move.
  2. Choose a project under Target project. Teable first checks what the move will affect.
  3. Review the check results and click Move.
  4. After the move, check that the related automations, apps, and routines still run correctly, and adjust them as needed.
The check only reads the project’s configuration and does not change any data. It reports:
  • Whether the move is allowed: Teable shows the reason and blocks the move when the target project is in a different Space, either project is read-only, you lack permission, or the target project already has a folder with the same name.
  • Resources that may stop working: Automations and apps that stay in the current project but reference a moved table may stop working after the move. For example, an automation trigger or action points to the table, a script or HTTP request contains the table ID, or an app signs in with the table or references it in code.
  • Cross-project links: Link fields between a moved table and a table that stays behind become cross-project links and keep working.
Move everything referenced is on by default and moves the resources along the reference chain together, so no broken references are left behind. Linked tables do not move.
  • You need permission to delete the resource in the current project and to create the same type of resource in the target project.
  • When the Authority Matrix is enabled, permission rules bound to roles in the current project cannot move with the resources and are removed. The moved resources then follow the target project’s permission settings. To keep the same restrictions, configure them again in the target project.

​
Import and Export Projects

Connect & Migrate Everything

Use AI Chat to migrate Airtable, Baserow, NocoDB, SmartSuite, and other systems into Teable.

​
Import Project (Data Migration)

A Teable project export file (.tea) contains project structure and configuration, plus record data if it was included in the export. Import the file to restore a project or create it in another Teable instance. This is useful for:
  • Data Migration: Move projects between different Teable instances (e.g., from Cloud to Self-Hosted)
  • Backup Restoration: Restore a previously exported project
  • Template Sharing: Share complete project structures with other teams
Steps:
  1. Enter the space
  2. Click the 「···」 button at the top right corner of the space to open the menu
  3. Click 「Import」
  4. Choose Import from file and upload the .tea file.
Import a project from a .tea file
If you want to create a project from Airtable, choose Import from Airtable in the same import dialog.

​
Export Project (Backup & Migration)

Export a Teable project file (.tea) to back up its structure and configuration or import it into another Teable instance. Choose Include records if you also need the record data. Steps:
  1. Enter the space
  2. Hover your mouse over the project you want to export
  3. Click the 「···」 button to open the menu
  4. Click 「Export」
  5. Keep Include records turned on to export record data. Turn it off to export only the structure and configuration.
  6. Click Start exporting and wait for the export to finish.
  7. Click Download in the export dialog to save the .tea file.
Export a project to a .tea file
  • To transfer record data, turn on Include records when exporting.
  • Teable converts cross-project relation fields to Single line text fields in the exported file.
  • When you duplicate or move a project across Spaces, cross-Space relationship fields are converted to Single line text.
  • Authorize the required integrations after import. Exported integration and secret placeholders do not contain credentials.

​
Share a Project

Projects can be shared through public links. The sharing scope can be the entire project or the currently selected item.
  1. Enter the target project
  2. Open the share menu for the project or selected item
  3. Turn on Share to web
  4. Copy the share link or QR code
Open project sharing Sharing scopes include: In the share settings, you can configure link permissions, regenerate the link, or delete the share link. Expand Advanced to set Allow viewers to copy data, Restrict by password, and Embed config. When you turn on password access, Teable generates a random password; click Copy link and password to send both to visitors at once. See Share Link Protection. Project sharing settings with Advanced collapsed by default If the sharing scope includes an app, the app must be published before it can be accessed through the public link.

​
Features Within a Project

A project can contain multiple tables for recording and organizing work or business-related information. For example: A customer management project might have separate tables for “Customer Companies,” “Customer Contacts,” and “Customer Follow-up Records,” while a meeting room management project might have separate tables for recording “Meeting Room Management,” “Meeting Room Equipment,” and “Meeting Room Reservations.” Therefore, most features within a project are related to tables:
  • Creating Tables: Projects allow users to create new tables based on project-specific needs, where users can define table structure, fields, and data types.
  • Editing Tables: Users can edit existing tables within the project, including adding, deleting, and modifying records.
  • Exporting and Importing Data: Projects support exporting data to CSV, and importing data in both CSV and XLSX formats.
Refer to the Tables section for more information about tables.
Last modified on November 2, 2026