Projects

Each project has its own models and records, pages, sidebar, dashboard, media, AI keys, public API, customers and — for a website — analytics. Nothing in one project shows in another, so a client’s website and your internal CRM can sit side by side without touching.

Each member opens every project, or only the ones chosen for them when they were invited (or later, on Members). Projects someone can’t open don’t show for them at all.

All three get the same builders, public API, webhooks and customer sign-in. A website just starts further along.

An API project has the same models and records as an app; what changes is what it puts first. Its sidebar starts with API: Public API (which models are open, and the reference with example requests), Webhooks and Customers. Its dashboard opens on the API itself:

• The base address your app calls, to copy.
• The endpoints that are on, with their methods, and which need a signed-in customer.
• Calls in the last 24 hours and how many failed, and the 20 latest calls (kept a week — method, path, answer, never what was sent).
• How many webhooks are on, and their latest deliveries.

Widgets from the dashboard builder go underneath. An API template starts the project with its models, endpoints and webhooks already set up.

1. On Projects press New project.
2. Give it a name and choose App or Website. A description is optional.
3. For a website, list its domains — example.com, www.example.com. Only visits from them are counted in analytics. You can add them later.
4. Choose its media library: its own, or the organization’s shared one.
5. Press Create project. It opens straight away.

• An app — start from a template (a CRM, finance, inventory, clients & invoices and more), build your first model step by step, or describe it to your AI.
• A website — start from a website template, or set it up yourself in three steps: its name, logo, favicon and colour; its home page (headline, introduction, a button and the search description); and, if you know them, its domain and Google Analytics ID. Then build the rest yourself, or with your AI.
• An API — start from an API template when there is one, or build your models as for an app.

Every template — app, API or website — works the same way. It asks a few questions first (your business name, say) and can add sample records to try it with. Then it builds the whole thing in the background, usually within a minute: models, pages, sidebar, dashboard, roles and sample records. You can leave the page while it works. Everything it makes is ordinary and changes like anything you built yourself. A template only goes into a new project, once. You can pick one in New project already. More in Starting from a template.

Every step can be skipped. Come back any time from the dashboard (Get started) or at /<project>/get-started. Setting a project up needs the Build permission.

Every record created, changed or deleted — who did it, when, and for a change each field’s before and after — and the project’s building: models built, changed or deleted, features and templates, the public API switched on or off, the site setup changed. Filter by kind, by what was done, by person and by date, or search for a name or code. Open goes to the record, unless it was deleted.

A record’s own history is on its page, in the History tab. Anyone whose role has Records: View can read the History; nobody can change it.

Inside a project every address starts with its public name: /acme-store is its dashboard, /acme-store/clients its Clients table, /acme-store/clients/… one client, and /acme-store/model-builder its models. Bookmark or share any of them — they open in that project. Organization pages (Projects, Members, Roles, Settings) have no project in the address.

Open another project from the switcher at the top right, or from its card on Projects. Each tab keeps its own project, so two projects can be open side by side. Dashboard on the home page takes you back to the project you worked in last.

Finding one. On Projects, the search box beside the kinds narrows the cards by name, address, description or domain (Enter opens the only match). The navbar search (the magnifier, or ⌘K) finds projects too: on the organization’s pages it lists them first — every one before you type — and inside a project it lists the others once you type. Projects in your other organizations show with their organization’s name; opening one switches you there.

Pinning one. Pin to top in a card’s menu (⋯) moves the project into Pinned, above all the others — the one you pinned last comes first. Unpin puts it back. Pins are yours alone: everyone in the organization keeps their own, and anyone who can open a project can pin it.

Edit… changes the name, description, media library and, for a website, its domains.

About this project sums it up: its kind, its address and public API address (each with a copy button), how many people open it (a link to Project → Members), its models, which media library it uses, the template it was built from, and who made it and when.

Below that, the project’s name and description, and its business details: logo, business name, address, phone, email, website and tax / VAT / BIN number. Its invoices, bills and receipts print these (see PDF templates). Upload logo picks one from the media library, uploads a new one or takes a link.

A new project starts with the organization’s business details; from then on they’re the project’s own, so two projects can print different addresses. The PDF designer’s Business details change the same ones.

Open any record and go to Comments. Everyone who can see the record reads the thread and can add to it. You edit or delete your own comments; people with Manage projects can delete anyone’s.

Type @ to mention someone: pick them from the list and they get a notification that opens the record’s Comments tab. Who you can mention follows who can see the record:

To answer a comment, click Reply under it. Replies sit indented under the comment they answer, the latest two showing and the rest behind View earlier replies. Replying to a reply adds to the same thread and starts with @ and their name, so they’re told. Whoever wrote the first comment, and everyone who replied since, gets a notification for each new reply, as long as they can still see the record. The notification opens the thread at that reply. Deleting a comment deletes its replies too.

Web addresses in a comment (https://… or www.…) become links that open in a new tab.

Each page has its own switches: Build → Pages, open the page, Fields & rules → Comments and mentions, then Publish. Deals can take comments while Products don’t. With comments off, the comments already written stay readable; with mentions off, comments still work without the @ list.

Switching later moves nothing: files stay in the library they were uploaded to, and switching back shows them again. Deleting a project deletes its own library, never the shared one. Either way the media is your organization’s alone.

The name is made from your organization’s and the project’s names when you create it — acme-store for the “Store” project of Acme — and doesn’t change when you rename either. Your site and the snippets name the project by its project key instead (API → Keys):

The Public API page shows the full addresses for the open project, ready to copy.

Archive (card menu) puts a project away without losing anything: it disappears from the switcher, its public API and widget stop answering, and AI keys can’t build in it. Show archived on Projects lists it again, and Restore brings it back exactly as it was.

Delete… removes a project for good. A project without models can be deleted by anyone with Manage projects. Once it has models, only the organization’s owner can delete it, by typing its name to confirm.