Building new tabs with Levi

Levi, your AI teammate · nineloops support

A worked example, the field types you can use, who is allowed to build, and what happens to your data if you remove one.

When your workspace needs to track something the apps do not cover, you do not have to bend an existing module or keep it in a spreadsheet. Levi can build a tab for it.

A worked example

Ask in plain words: add a tab to HR where I can track external contractors, with their agency, day rate, contract end date and the manager they report to.

1. Levi checks what your workspace has already built, so it extends an existing tab rather than quietly creating a second one.
2. It writes the definition: what one record is called and what many are called, which module the tab belongs to, and each field with a sensible type. Agency becomes text, day rate becomes currency, contract end becomes a date, and the manager becomes a person from your workspace.
3. Because building changes what everyone sees, Levi asks first by default. The request waits under Settings, then Levi approvals, with every field attached so you can read it before you agree.
4. Once approved, the tab is there. It appears the next time the module loads, with a table view of all records ready to use. There is no deployment and no release to wait for.

What you can put in a field

Nineteen field types: text and long text, number, currency, date, date with time, dropdown, multi select, a person from your workspace, checkbox, URL, email, phone, progress, tags, a link to a record in another app, a rollup, a formula, and a file. One tab can hold up to 60 fields, and you can add more fields later without rebuilding it.

Who is allowed to build

Building or reshaping a tab is a configuration change, so it needs an owner or an admin, or someone with the manage settings permission. Adding records to a tab that already exists is ordinary data entry and follows the normal edit permissions for content.

Who can see it

A built tab exists only inside the workspace that built it. Nobody else can see it, and no other workspace is affected by it. You can narrow it further so that only admins see it, or only named roles.

Removing one

Removing a tab archives it rather than destroying it. The records stay exactly where they are and the tab stops accepting changes, so tidying up never costs you data, and undo brings it back with everything in it.

This is why a built tab is safe: it is rows in a registry, drawn by one runtime, rather than code generated and shipped to everybody. It cannot alter an existing table, an existing permission or an existing screen. Built tabs appear in the HR rail today, which is the module wired to show them, and other modules are being connected the same way.

More in Levi, your AI teammate

• What Levi can do in your workspace
• How Levi's permissions work
• Approving what Levi wants to do
• Seeing and undoing what Levi did
• When Levi needs a platform build

Still stuck?

Raise a ticket and a person who works on nineloops will pick it up.

<a href="/support">All support articles</a>