Skip to content
Guides

Lark Base: what it handles well, and when a business needs its own system

Vetrox · Published

The short answer

Lark Base is the database-style table inside Lark: each row is a record, each column is a field of a set type, and the same records can be shown as a grid, a Kanban board, a Gantt chart or a form, with dashboards and automations on top. It handles the records one team works through every day well, such as leads, jobs, orders and assets. Plan for a system of your own when a table will pass its record limit (2,000 a table on the free Starter plan, 50,000 on Enterprise before add-ons), when customers or several other systems need the same records, or when your own rules must decide who may change what.

What Lark Base is

Base is the database part of Lark, the workplace app that also holds chat, meetings, documents and approvals (what Lark is, and how a team gets started). Lark's Help Center calls it a versatile data management platform (opens in a new tab). It looks like a spreadsheet, but it works like a simple database:

  • Records and fields. Each row is a record: one thing you track, such as a job or a client. Each column is a field of a set type, such as a person, a date, a single option or an attachment, so a date column only takes dates.
  • Tables. A base holds several tables, one for each kind of record, and link fields join them: a job links to its client instead of repeating the client's details.
  • Views. The same records can be shown as a grid, a Kanban board grouped by status, a Gantt timeline, a calendar, a gallery or a form, and each view keeps its own filters, groups and sorting.
  • Dashboards. They turn the records into charts.
  • Automations and workflows. They act when something happens: a Lark message to a task's owner when it is assigned (opens in a new tab), or a reminder when a date in the record arrives (opens in a new tab).
  • Base apps. Screens built over the data with a drag-and-drop builder; one app can draw on several bases.

The plans and limits in this guide are Lark's. Feishu, the separate product for mainland China, is covered in Lark Suite or Feishu.

Base or a spreadsheet

Lark also has Sheets, its spreadsheet, and Lark's own comparison of Base and Sheets (opens in a new tab) draws the line: Base suits building databases for work such as project and order management, and Sheets suits processing and analysing large amounts of numbers, such as a budget. Base has automations built in and Sheets has none. Sheets has more than 500 functions, a Base formula field more than 100, and Base cannot merge cells.

A simple test: if every row is one thing that moves through stages, such as a job, an order or a lead, it belongs in Base. If the sheet is a calculation that people change numbers in to see the result, keep it in Sheets.

Base imports Excel and CSV files of up to 20 MB and turns text and numbers into matching field types. Moving records out of a shared spreadsheet is a job of its own, covered step by step in replacing spreadsheets with a proper system.

What Base handles well

Base is at its best when one team works through the same kind of record every day and everyone involved already works in Lark. Typical uses:

  • Leads and deals. A form adds each new enquiry as a record, each salesperson works from a view of their own leads, and an automation tells the team when a deal changes stage. Lark lists collecting leads and business opportunities (opens in a new tab) among the uses of forms.
  • Jobs and projects. A Kanban view grouped by status shows what is waiting, in progress and done, a Gantt view shows the timeline, and the owner gets a Lark message when a job is assigned.
  • Registers of assets, contracts, licences or equipment. An automation sends a reminder when a date in the record arrives, such as a renewal date, and a formula field can set that date ahead of the expiry.
  • Requests from inside and outside the business. A form collects requests, reports or survey answers straight into a table, and its link can be limited to invited people or to your organisation, or opened to anyone with the link.
  • Reports on approvals. Requests from Lark Approval can be synced into a base (opens in a new tab), every hour once automatic sync is on, for reports such as expense claims by month. Setting up the approvals themselves is covered in the approval workflow guide.

What these have in common: one team, records that fit in tables, a handful of rules, and people who already spend their day in Lark. That is where Base saves the most work: there is nothing new to sign in to, and its messages arrive in the chats people already read.

Setting up a base for one process

A base that lasts is planned like a small database, not typed into like a spreadsheet:

  1. One table for each kind of thing: clients in one table and jobs in another, joined by a link field, instead of the client's details copied into every job.
  2. A field type for every column: a single option for the status, a person for the owner, a date for the due date. Fixed options stop the same status being spelt three ways.
  3. A form for new records, so nobody types into the table directly. Required questions make sure each record arrives complete.
  4. A view for each way of working: a Kanban board for the team, a filtered grid for each person, a calendar for due dates.
  5. Access before sharing: decide who can manage, edit or view the base, and keep link sharing to the people who need it.
  6. Automations last, once the records are clean: a message to a new owner, a reminder before a due date, a weekly summary to the team's group chat.
  7. A dashboard for the numbers someone asks for every week.

Give the base an owner: the person who changes its fields and automations, and whom everyone else asks. A base that anyone can restructure soon looks like the spreadsheet it replaced.

The limits on each Lark plan

Base's limits are set by the Lark plan, and a plan covers the whole organisation: Lark does not let some members use Pro while the rest stay on Starter (opens in a new tab). The limits that matter most, from Lark's overview of paid features for Base (opens in a new tab):

  • Records in a table: 2,000 on Starter, which is free, and on Basic; 20,000 on Pro; 50,000 on Enterprise. New records cannot be added to a table that has passed its limit.
  • Automation runs: 1,000 a month on Starter and Basic, 50,000 on Pro and 500,000 on Enterprise, counted across the whole organisation, workflows included. When the limit is reached, every workflow and automation pauses (opens in a new tab) until the first day of the next month.
  • Record and field permissions, which let a role see or change only some rows and columns: Pro and Enterprise only.
  • Syncing data between bases: Pro and Enterprise. Archiving old records (opens in a new tab), which keeps them read-only and frees up record capacity: Enterprise only.

On Basic, Pro and Enterprise, an organisation can buy add-ons that raise a table's record limit (opens in a new tab) through Lark's account team, up to 2 million records a table and 10 million a base; Lark marks the feature as beta. Lark also notes that Basic is sold only in some countries and regions.

Some limits are the same on every plan: a table holds up to 300 fields, of which no more than 100 can be formula and lookup fields, and up to 200 views; up to 200 people can edit a base at the same time (Base limits FAQs (opens in a new tab)).

Do the arithmetic before you build. A table that gains 10 records each working day passes 2,000 in under a year. An automation that sends a message for every new record uses one run each time, so 50 new records a day use up 1,000 runs in about 20 working days, and then every automation in the organisation waits for the next month.

Access, history and data location

Sharing a base gives each person one of three levels: manage, edit or view. On Pro and Enterprise, advanced permissions (opens in a new tab) add roles that control tables, records, fields, views and dashboards, and who may copy or download. Lark's own example: sales staff see only their own clients, and managers see the whole set.

The three sharing levels apply to the whole base, so a filtered view is a convenience, not a restriction. Keeping some records or fields from some people takes advanced permissions.

Base keeps an edit history (opens in a new tab): who changed a record, when and what, kept for 180 days, and versions of the whole base that can be restored. A restore applies to the whole base, not to one table or view.

Records about people raise the same questions as any internal tool: an account for each person, the least access each role needs, and a record of changes. The internal tools guide goes through them.

Lark's privacy policy (opens in a new tab) says information may be stored on servers outside your country, including in Singapore, Japan and the United States. If a contract or your industry says where certain records must be kept, check that before they go into Base.

Connecting Base to other systems

Base does not have to stand alone. It reaches other software in three ways, from the simplest to the most work:

The usual pattern is that one system holds each record and the other follows it. A won deal in the CRM creates a job in Base; an invoice stays in the accounting software, and Base keeps only its number and status. Deciding which system holds what, and making sure an integration never fails quietly, is covered in connecting the systems you already use.

Lark Base vs Airtable

Airtable is a standalone product of the same kind: tables of typed fields, several views, forms, automations and interfaces. The difference that matters most is where it sits. Base is part of Lark, so its automations post to the chats people already use, and staff sign in with the Lark account they already have. Airtable is a separate product, with its own accounts and plans.

Their limits are counted differently, so compare like with like. Airtable's Free plan (opens in a new tab) allows 1,000 records per base and 100 automation runs per workspace a month, with two weeks of revision history; Lark's free Starter plan allows 2,000 records in each table and 1,000 automation runs a month for the whole organisation. On paid plans, Airtable's Team plan allows 50,000 records per base and Business 125,000, while Lark allows 20,000 per table on Pro and 50,000 on Enterprise.

For a team that already works in Lark, Base is the natural first choice: no second app and no second set of accounts. A team on Microsoft 365 or Google Workspace without Lark would compare Airtable with the builders in its own suite, covered in the internal tools guide.

When to move to your own system

Base is being stretched when workarounds appear: a second base for last year's records, a spreadsheet beside it for what it cannot do, an automation nobody dares to touch. Start from where the records should live:

Where should these records live?

  • 01

    Lark Base on its own

    • Records for one team
    • Tables under the limit
    • Everyone is in Lark
  • 02

    Base, connected to other systems

    • Another system has them too
    • An integration keeps both in step
    • Staff work in Lark
  • 03

    A system of your own

    • Tables pass the limit
    • Clients and suppliers sign in
    • Your rules decide who changes what
Start with the first option, and move to the next only when one of its conditions applies.

The signs that point to a system of your own:

  • A table will pass its record limit, and archiving or add-ons would only put the problem off.
  • The business depends on automations running on time, and a monthly cap that pauses them all is not acceptable.
  • Customers or suppliers need to sign in and work on their own records. Base can take a form from anyone with the link and, where your settings allow it, share a read-only view (opens in a new tab) outside the organisation; a place where outsiders sign in to their own records is a customer portal.
  • Several systems hold the same records, and keeping them in step through automations has become a job in itself.
  • The rules are your own: what has to be checked before a record is saved, who may change it at which stage, and what must happen next. Formulas and automations can do some of this, but rules that decide what people may do belong in software built to enforce them.
  • The records must be stored in a particular country, or their full history kept for longer than the edit history covers.

Leaving Base is not a dead end. Every table can be exported to Excel or CSV (opens in a new tab), so its records can move into a database with the same columns. It does not have to be all at once either: a custom system can hold the records that need its rules while the team keeps its day-to-day lists in Base, the two linked through the API.

Where Vetrox fits

Vetrox is an Australian IT company and an official Lark partner in Australia. For teams in Lark, we set up Base with the views each team needs, dashboards that turn records into charts, and automations that send a Lark message to the right person when a record changes. Before a plan is chosen, we look at what your bases will hold and how much they will automate, and recommend a plan in writing. We connect Base to the systems you already run through the Lark Open Platform, and every sync is logged, so a failure raises an alert instead of going missing quietly. When a process outgrows Base, we build the system it needs: we map the columns to database fields, with validation, search and permissions, and you approve a clickable prototype before any code is written. If Base is enough for the job, we will say so.

Sources

  1. Lark Help Center: Get started with Base (updated 27 October 2026) (opens in a new tab)
  2. Lark Help Center: Use automations in Base (updated 21 October 2025) (opens in a new tab)
  3. Lark Help Center: Triggers and actions for Workflow and Automations (updated 11 May 2026) (opens in a new tab)
  4. Lark Help Center: Differences between Base and Sheets (updated 12 November 2025) (opens in a new tab)
  5. Lark Help Center: Use form views in Base (updated 3 September 2026) (opens in a new tab)
  6. Lark Help Center: Sync Approval data to Base (updated 28 October 2026) (opens in a new tab)
  7. Lark Help Center: Overview of Lark plans (updated 8 September 2026) (opens in a new tab)
  8. Lark Help Center: Overview of paid features for Base (updated 9 July 2026) (opens in a new tab)
  9. Lark Help Center: Base Workflow and Automations FAQs (updated 2 March 2026) (opens in a new tab)
  10. Lark Help Center: Archive records in Base (updated 15 September 2026) (opens in a new tab)
  11. Lark Help Center: Expand the record limit in Base (updated 9 November 2026) (opens in a new tab)
  12. Lark Help Center: Base limits FAQs (updated 8 April 2026) (opens in a new tab)
  13. Lark Help Center: Use advanced permissions in Base (updated 20 August 2026) (opens in a new tab)
  14. Lark Help Center: View edit history in Base (updated 13 July 2026) (opens in a new tab)
  15. Lark: Privacy Policy (last updated 13 November 2026) (opens in a new tab)
  16. Lark Help Center: Use Base to automate the sending of HTTP requests (updated 15 September 2026) (opens in a new tab)
  17. Lark Help Center: Set receiving a webhook as a trigger for Automations and Workflow (updated 27 August 2026) (opens in a new tab)
  18. Lark Developer: Server API, Base overview (updated 28 July 2025) (opens in a new tab)
  19. Airtable Help Center: Airtable plans overview (opens in a new tab)
  20. Lark Help Center: Share a Base view independently (updated 9 October 2026) (opens in a new tab)
  21. Lark Help Center: Import or export a base (updated 16 July 2026) (opens in a new tab)

Show us how your business runs today.

A 30-minute call to discuss the software you use, the work it handles and what needs to change.