Skip to main content
Auxilian organizes data in a simple hierarchy. Understanding it makes permissions and limits predictable.

Workspaces

A workspace is a group of people. The first time you sign in, Auxilian creates a personal workspace for you and makes you its owner, unless you are joining someone else’s workspace through an invitation. You can belong to several workspaces. Each workspace member has one role: The overview and sidebar list projects from all of your workspaces. When you belong to several, the active workspace decides where new projects go and which workspace Settings manages. Switch it from the account menu at the bottom of the sidebar. See Workspaces and Members and roles.

Projects

A project is a database. Behind the scenes, each project is its own Postgres schema, isolated from every other project. A project belongs to exactly one workspace.
  • Only the workspace owner and admins create projects.
  • The person who creates a project is its creator and always has write access to it.
  • Workspace owners and admins have write access to every project in their workspace.
  • Anyone else needs the project shared with them, with read or write permission.
Workspace membership is required for any project access, including the creator’s. Removing someone from a workspace removes their access to every project in it.

Tables and columns

A table has the columns you define plus two system columns that Auxilian adds to every table: You choose from seven column types: text, integer, numeric, boolean, timestamptz, uuid, and jsonb. A uuid column can be a foreign key to another table’s id. See Data types and Foreign keys.

Rows

Rows are your data. You and anyone with write access can insert, edit, and delete them in the web app, and an AI assistant can do the same through MCP tools. Inserts accept up to 100 rows at a time.

Surfaces

Every change comes from one of two surfaces, and the activity log records which: An AI assistant never has its own identity or permissions. It acts as the person who approved the connection, so it can do exactly what that person can do and nothing more.

Activity log

Every project keeps an activity log of schema changes, row writes, sharing changes, and refused writes. Each event records who acted, from which surface, and what changed. See Activity log.