Airtable is a great place to manage customer data internally. You can track orders, support requests, subscriptions, documents, onboarding steps, payments, and account details in one flexible database.

But Airtable is not always the right interface for customers.

Most customers should not see your full base. They should not need to learn Airtable. And they should not need an Airtable account just to check an order, submit a request, or update their information.

With miniExtensions, you can create a customer portal connected to your Airtable base. Customers log in through a simple portal link and only see the records connected to them.

What is an Airtable customer portal?

An Airtable customer portal is a customer-facing interface powered by Airtable data.

Instead of giving customers access to Airtable, you use miniExtensions Portal to decide which records, tables, fields, and views they can access.

A customer portal can include:

  • Customer profile details
  • Orders
  • Support requests
  • Files and documents
  • Invoices
  • Subscriptions
  • Bookings
  • Account updates
  • Project or service status

Airtable remains the source of truth. miniExtensions becomes the front end your customers interact with.

Why not just invite customers to Airtable?

Inviting customers directly into Airtable usually creates more problems than it solves.

Customers may see too much. They may edit the wrong fields. They may find Airtable confusing. And if you have many customers, managing access can become messy.

A miniExtensions portal gives you a more controlled setup:

  • Customers do not need Airtable accounts
  • Customers do not need miniExtensions accounts
  • Each customer can see their own linked records
  • You choose which tables are visible
  • You choose which fields are editable
  • You can provide a login page, magic links, or email login links
  • You can embed the portal on your website or use a custom URL

This makes the experience easier for customers and safer for your internal Airtable workflow.

Example Airtable setup

A customer portal might use tables like:

  • Customers
  • Orders
  • Support Requests
  • Documents
  • Invoices
  • Subscriptions
  • Appointments
  • Messages

The Customers table is usually the users table for the portal. It stores the customer’s login information and profile details.

Other tables should link back to the customer. For example:

  • Each order links to a customer
  • Each support request links to a customer
  • Each document links to a customer
  • Each invoice links to a customer

When a customer logs in, miniExtensions can show the records connected to that customer record.

Common customer portal workflows

A customer portal can support many workflows.

For an ecommerce or operations team, customers might log in to view order status, shipment information, invoices, and documents.

For a service business, customers might view active services, submit requests, upload files, and track progress.

For a SaaS or membership business, customers might update account details, submit support tickets, review subscription information, or access private resources.

For an onboarding workflow, customers might complete required forms, upload documents, and track which steps are still pending.

The key is that all of this data can stay in Airtable while the customer sees only the parts designed for them.

Let customers update their own profile

The Portal profile feature is useful for customer account management.

It lets logged-in customers access their own record from the users table. You can decide which fields customers can view or edit.

For example, customers might update:

  • Name
  • Company
  • Email address
  • Phone number
  • Billing address
  • Shipping address
  • Preferred contact method
  • Account preferences

Internal fields can remain hidden or read-only.

This gives customers a self-service way to keep their information up to date without contacting your team.

Add support requests with child forms

A customer portal becomes more useful when customers can create new records, not just view existing ones.

For example, you can add a Support Requests table and let customers submit a new request from inside the portal.

A support request child form might include:

  • Subject
  • Description
  • Priority
  • Category
  • Attachment
  • Related order or product

You can also prefill fields that customers should not choose manually, such as status. A new request can start as “New” or “Pending” while your team handles routing inside Airtable.

This gives customers a clean support intake experience while keeping your internal team in Airtable.

Show different views for different customers

Not every customer needs the same portal experience.

A regular customer might only need orders and support requests. A premium customer might also need documents, onboarding status, or a dedicated account dashboard.

miniExtensions supports conditional tables and conditional views based on fields in the users table. For example, you can show different tables or views based on:

  • Customer type
  • Plan
  • Region
  • Account manager
  • Active/inactive status
  • Onboarding stage

You can also use conditional login rules so access is validated when a user loads the portal. If a customer no longer meets the conditions, they can be logged out.

When to use a Portal vs a Form

Use a Portal when customers need ongoing access to multiple records.

Use a miniExtensions Form when the customer only needs to submit or update one record.

For example:

  • Customer portal: view orders, support requests, invoices, and profile
  • Form: submit a one-time support request
  • Form with login: let a customer update an existing record after identifying themselves
  • Portal plus forms: let customers view many records and create new linked records from inside the portal

Many customer workflows use both.

Build a customer portal from the Airtable base you already use

A customer portal does not replace Airtable. It should make Airtable easier to use with customers.

With miniExtensions, you can keep your team’s operational data in Airtable and give customers a focused, controlled way to interact with it.

Customers get self-service access. Your team keeps its existing Airtable workflow. And you avoid adding unnecessary Airtable seats for every customer.

Create your portal with miniExtensions Portal and turn your Airtable customer data into a customer-facing experience.

How to set this up in miniExtensions

1. Create your customer users table

In Airtable, create a Customers table. This will be the Portal users table.

Useful fields include:

  • Customer name
  • Email address
  • Phone
  • Account status
  • Customer type or plan
  • Billing address
  • Shipping address
  • Internal customer ID

Use email as the main login field unless you have a clear reason to use another unique field.

Link customer records to operational tables

    Create or prepare the tables customers should access:

    • Orders
    • Support Requests
    • Invoices
    • Subscriptions
    • Appointments

    Each table should have a linked record field pointing to the Customers table.

    For example, every order should be linked to the customer who owns it, and every support request should be linked to the customer who submitted it.

    Create a Portal in miniExtensions

      Go to Create Extension and choose Portal.

      Select the Airtable base, then choose the first data table (e.g. Orders) and the field linking each order to the appropriate customer (e.g. Customer).

      Go to Users & Login to configure login fields and optional login rules. An email field is usually pre-selected for login, if detected.

      Add more customer-facing tables, if needed

        In the Portal Tables section, add the tables customers need:

        • Orders
        • Support Requests
        • Invoices
        • Subscriptions

        Each table added to the Portal creates a section customers can access. Each table will only show records linked to the logged-in customer by default.

        Configure read-only customer views.

          For tables like Orders, Invoices, or Documents, customers may only need to view records.

          Use child form settings to make fields read-only, or disable Allow users to expand records when you do not want customers opening or editing records.

          For a clean customer experience, create views like:

          • Open Orders
          • Completed Orders
          • Open Invoices
          • Paid Invoices
          • Shared Documents

          Add support request creation.

            For Support Requests, allow customers to create new records.

            In the Support Requests child form, include fields like:

            • Subject
            • Description
            • Priority
            • Category
            • Attachment

            Set internal fields such as Status to a default value like New or Pending.

            New records created within the portal will automatically be linked to the logged-in user.

            Let customers update their account profile.

              Go to the Portal Profile and enable Show logged in profile.

              Configure the profile child form to let customers update fields such as:

              • Name
              • Phone
              • Billing address
              • Shipping address
              • Contact preferences

              Do not expose internal customer fields such as account owner, internal notes, billing risk, or internal tags.

              Show different portal sections by customer type.

                Use conditional tables or views when different customers need different access.

                For example:

                • Active customers see orders and support
                • Premium customers see extra documents
                • Inactive customers only see billing records
                • Customers in onboarding see onboarding tasks

                Set these in Conditional Table or Conditional View using fields from the Customers users table.

                Share or embed the portal.

                  Use the Portal Share section to:

                  • Copy the portal URL
                  • Generate magic links
                  • Email login links to customers
                  • Embed the portal on your website
                  • Use a custom URL