Bases ships eleven field types today.
A Base holds tables with typed fields, saved views, record comments, and file attachments. It is where the CRM or the applicant tracker lives, on your server rather than in a bolted-on Airtable. Grant an AI Employee the Base and it gets 21 tools over the same rows you edit, with every write in the audit log.
Five templates ship, from CRM to Applicant Tracker.
Multi-table workspaces with 11 field types, saved views, comments, and attachments, plus 21 built-in tools for a granted AI Employee.
Eleven field types, including links to sibling tables
Eleven field types: text, number, checkbox, dates, email, URL, selects, and link fields that reference rows in sibling tables. Renaming a field never migrates data, because values key on field IDs.
Save one view for finance and another for sales
Each table keeps saved views that combine type-aware filters (is before, has any of, is empty…), multi-key sorts, and hidden fields, so the sales view and the finance view stop fighting.
Any row opens as a form with one comment thread
Open any row in a side drawer and you get its field values as a form, a comment thread, and file attachments. Each comment is attributed to a human Member or an AI Employee in one shared stream.
Five templates, from CRM to Applicant Tracker
Five templates ship built in. Blank, CRM, Applicant Tracker, Content Calendar and Project Tracker each arrive seeded with linked tables and starter rows, ready to edit.
The Base Assistant knows the schema and suggests changes
A slide-over chat hands your question to an AI Employee loaded with the Base's schema, and it comes back with suggested changes. Applying them stays your call, which keeps the blast radius small.
One Grant covers every table in that Base
Access is per employee, per Base. One Grant opens read/write on every table in it, and revoking removes those tools from the employee's next spawn. AI uploads cap at 5 MB, so a runaway call cannot fill the disk.
Granted employees get 21 Base tools.
A granted AI Employee gets the full Bases surface as built-in tools — schema, rows, comments, and attachments — with pagination, audit trails, and caps designed for autonomous use.
Schema and data alike
Employees create tables, add fields of all 11 types, and read or write rows — paginated up to 500 at a time — the same surface humans get in the grid editor.
They can start from zero
An employee can create a brand-new Base on request and is auto-granted on it, so “set up a tracker for this” is a one-message job.
Deliverables attach
Exports from the Resources library and other tool output can be filed onto a Base record as an attachment — reports land next to the rows they describe.
Readers ask 5 questions about Bases.
How do I control which AI Employees can touch a Base?
Access is per-employee, per-Base via a Grant, managed from the Base's access panel. One Grant gives read/write on every table in that Base, and revoking it means the employee's next spawn doesn't see the Base tools at all.
Can an AI Employee change the schema, or only the data?
Both. Granted employees have tools to create tables, add, update, and delete fields of all eleven types, and read and write rows — the same surface humans get. Every write is validated and recorded in the audit log.
What field types are supported?
Eleven: text, long text, number, checkbox, date, datetime, email, URL, single select, multi-select, and link fields that reference records in another table of the same Base. Renaming a field never migrates data because cell values are keyed by field ID.
How is this different from Explore or the Airtable integration?
Bases are structured workspaces your company owns natively inside Genosyn. Explore is BI over external database Connections, and the separate Airtable Integration connects employees to an external Airtable account. Bases keep the data on your own instance.
Do I have to start from a blank table?
No — five templates ship built in: Blank, CRM (Contacts, Companies, Deals with cross-table links), Applicant Tracker, Content Calendar, and Project Tracker, each seeded with fields and starter rows.
4 more products share one database.
Notes
Markdown pages in nested notebooks, with read or write Grants that cascade from a notebook down to every sub-page.
Resources
One ingested URL, PDF, or EPUB that every granted AI Employee can search, export, and attach to a Gmail draft.
AI Employees
Teammates that carry a markdown Soul and work Routines on a schedule you pick, with every Run transcribed and costed.
Workspace
Channels, DMs, and 25 MB file uploads where AI Employees are members you can @mention.
Tomorrow one thing is finished before 09:30.
Install Genosyn, register an AI Model, write one role, and put it on a schedule. The company grows from there.