---
title: "Build business apps with ChatGPT. Keep the rules in the database."
description: "Design relational business apps with ChatGPT: tables, permissions and interfaces on gtable. Explore workflows and connection requirements."
language: en
canonical: https://gtable.app/build-with/chatgpt
source: gtable website
---
# Build business apps with ChatGPT. Keep the rules in the database.

Work through the app's structure with ChatGPT, then connect a compatible MCP client to the records you are allowed to use. The conversation helps you design; gtable holds the tables and permissions.

## Start with the business, then shape the app

A useful brief names the people, the records they work with and what each person is allowed to do.

- **Make the brief concrete.** Ask ChatGPT to turn your workflow into a list of tables, relationships and user groups. Include examples of who must not see a record.
- **Connect deliberately.** Keep designing the app as a builder separate from working in an app as an invited user. Each uses its own identity and machine surface.
- **Ask focused questions.** Start with a bounded question such as which assigned projects are overdue. The connection returns only the rows and fields available to your identity.

## Give ChatGPT a way to work as you

Where your ChatGPT account and client support a remote MCP connection with OAuth, use the suite's server address. A conversation without a connection does not have live access to your app.

- **Builder access.** The Studio's machine surface is for the app definition: tables, fields, groups and permissions. Connect using a builder identity when designing an app.
- **User access.** A suite connection is for the apps you may use. It carries your identity and can be narrower than your account, never wider.
- **Review changes.** The in-app assistant asks before applying its proposed writes. External clients must follow their own approval workflow; an API credential still obeys your permissions.

Remote connectors depend on ChatGPT's current client, account and settings. gtable does not promise that every ChatGPT account can connect.

## A brief worth giving your agent

“Design a client-delivery app with Clients, Projects and Tasks. Link tasks to projects and projects to clients. Consultants work on their assigned projects. Clients see only their own projects. Add an overview of overdue tasks.”

Treat this as a starting brief, not a command that bypasses setup. Review the proposed schema and permission rules before using real data.

## Your assistant can change. Your access rules stay.

- **One model.** The grid, generated interfaces, REST and MCP all ask the same permission compiler. Switching clients does not create a new route around it.
- **What is available.** gtable is not open yet. These pages explain workflows for the product being built, not an invitation to sign up or a promise of a provider-specific integration.

Read the [connection guide](https://gtable.app/for-agents) and the [developer documentation](https://gtable.app/docs) for the exact API surface.

## Keep exploring

- [Claude](https://gtable.app/build-with/claude)
- [Gemini](https://gtable.app/build-with/gemini)