AppsAutessaDB

Row-level security and access · AutessaDB

Sharing and access levels

Every AutessaDB table starts private to its owner and is shared with people, teams, company roles or everyone at your company at READ, WRITE, PUBLISH or ADMIN. Access adds up, so someone covered by several grants gets the highest one, and security roles then narrow which rows and columns each person sees.

A database essential, built in
Share · customersaccess adds upSAMPLE
wholeveldefault role
Everyone at NorthwindREADRegional sales
Team · Revenue opsWRITERegional sales
dana@northwind.examplePUBLISH—
Role · Data adminsADMIN—
Contains sensitive records · without a default role, people you share this table with won’t see any rows.

-- the problem

Data should be shareable without being exposed

Teams need to share a table to work together, but sharing should not mean everyone sees every row. AutessaDB separates the two dials: sharing decides who can use the table, roles decide what each person sees in it.

What you get

  • READ views the schema and reads rows; WRITE inserts, updates and deletes; PUBLISH adds triggers; ADMIN changes the schema, shares and deletes.
  • Share with individuals, teams, company roles or the whole company, each at its own level.
  • The tables list shows All Tables, My Tables, Company Shared and Shared With Me.
  • get-sharing-details shows exactly what share and update-settings would change, without changing anything.
  • Ownership transfer is owner-only, and the owner always has ADMIN.
  • Tables managed for you, such as a connector's tables or an app's sign-in users table, follow their parent's sharing.

-- how it works

How does sharing and access levels work in AutessaDB?

  1. Open Share

    From the table, open the Share dialog.

  2. Pick who and how much

    Add people, teams, roles or the company, and choose a level for each.

  3. Narrow with a default role

    For sensitive tables, set a default role so grantees see only their rows.

-- every option

Access levels on a table

optionwhat it does
READView the schema and read rows: get, query, join and semantic search.
WRITEInsert, update and delete rows.
PUBLISHAdd triggers (not row writes; editing or disabling triggers needs ADMIN).
ADMINChange the schema, share the table and delete it.
Data lake tablesREAD queries, WRITE loads and appends, ADMIN changes schema and semantic layer.

-- example

Share a table company-widebash
autessa autessadb tables get-sharing-details --tableId ayXduiaLeFKh
autessa autessadb tables share --tableId ayXduiaLeFKh --level COMPANY --accessLevel READ

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

-- permissions

Who can do what?

accesscan
OwnerEverything, including transferring ownership.
ADMINShare and set table security settings.

-- relations

How it connects

-- faq

Questions about sharing and access levels

Does PUBLISH let someone write rows?

No. PUBLISH adds triggers. Writing rows needs WRITE or ADMIN.

What if someone has two grants?

Access adds up: they get the highest level among their grants.

Can I see what a share change would do first?

Yes. get-sharing-details is a read-only view of exactly what share and update-settings would modify.

$ autessa autessadb tables create

Try sharing and access levels in AutessaDB

Tables start private and are shared at READ, WRITE, PUBLISH or ADMIN, with a default security role applied to everyone you share with.

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