Files, apps and operations · AutessaDB

Backend for custom apps

AutessaDB is the database behind Autessa custom apps. Apps read and write tables through the built-in app SDK, apps with their own sign-in keep their users in an AutessaDB table created for them, and row rules with $CURRENT_CUSTOMAPP_USER_ID or $CURRENT_CUSTOMAPP_USER.<column> show each visitor only their own rows.

Goes beyond a typical managed database

Create a free database

Client Portal · My orderssigned in: kim@harbor.exampleSAMPLE

orderstatustotal

5531shipped1,240.00

5540open86.00

Only Harbor Freight’s rows. The app asks for orders; the database applies the visitor’s rule.

Role · Portal customers → ordersSAMPLE

assigned to: CUSTOM_APP  Client Portal
row rule:    account_id EQUALS $CURRENT_CUSTOMAPP_USER.account_id
writeCheck:  SAME_AS_READ

-- the problem

Client portals need per-customer data isolation

A portal where every customer sees only their own orders usually means a custom backend and careful code on every query. With AutessaDB, the app asks for rows and the database applies the visitor's rule, so isolation does not depend on every page getting it right.

What you get

Internal apps act exactly as the person using them, with that person's rows and columns.
Public and sign-in apps are limited to their own permissions and to what the person who saved them can access.
To give visitors a table, the saver must see every row and column of it, or the app gets an AutessaDB role instead.
Custom Auth apps and personal access link apps get an auto-created users table; add your own columns such as region.
Visitors cannot change the columns on their own user row, so they cannot widen what they see.
Rules that match a visitor's email apply only once the email is verified.
Analytics queries power dashboards inside apps.

-- how it works

How does backend for custom apps work in AutessaDB?

Build the app
Create an app in Custom Apps and register the tables it uses.
Choose who uses it
Default (your team) or a hosting mode with its own sign-in.
Scope visitors
Give the app a role whose row rule uses $CURRENT_CUSTOMAPP_USER_ID or a user column.

-- every option

App placeholders

option	what it does
$CURRENT_CUSTOMAPP_USER_ID	A Custom Auth visitor's account id.
$CURRENT_CUSTOMAPP_ACCESS_LINK_ID	A personal access link visitor's id; never matches Custom Auth ids, so a mode switch cannot expose rows.
$CURRENT_CUSTOMAPP_USER.<column>	A column of the visitor's own row, such as region.
Users table	Created for the app; follows the app's sharing and cannot be shared on its own.
App permissions	Read, write or delete per table, set in the app's settings.

-- example

Query from inside an appts

import { AutessaDbService } from '../autessa/services';
import { getAutessaResourceId } from '../autessa/utilities';

const res = await AutessaDbService.query({
  tableId: getAutessaResourceId('tables', 'ORDERS'),
  whereGroups: [{ logicalOperator: 'AND', conditions: [
    { columnName: 'status', operator: 'EQUALS', value: 'open' },
  ] }],
  pageSize: 25,
});

Full reference in the AutessaDB CLI docs and the API reference.

-- permissions

Who can do what?

access	can
App visitor	The rows and columns the app's role allows for them.
App admin	Set the app's table permissions, within their own access.

-- relations

How it connects

autessa platform

Custom apps

Build the app on top of your tables.

autessadb feature

Row-level security

Per-visitor rules.

autessadb feature

Security roles

Assign a role to an app.

-- faq

Questions about backend for custom apps

Can a customer portal show each customer only their own data?

Yes. Give the app an AutessaDB role whose row rule uses $CURRENT_CUSTOMAPP_USER_ID or a column of the visitor's row, and each visitor sees only matching rows.

Where are app users stored?

In an AutessaDB table created for the app, which you can extend with your own columns.

Can a public app see everything I can?

No. Public and sign-in apps are limited to the permissions you give them, and never beyond what the person who saved those permissions can access.

Also in Files, apps and operations:Drive on AutessaDB Soft delete and restore

$ autessa autessadb tables create

Try backend for custom apps in AutessaDB

Custom apps read and write AutessaDB tables, keep their sign-in users in AutessaDB, and scope each visitor to their own rows with role placeholders.

Create a free database

Read the AutessaDB guide or install the CLI.

100% customizable, code and all

Make AutessaDB fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours