Tebelis gives you the building blocks for any field-work process — an organisation, locations, templates with rules, workflows, roles, records/forms, and dashboards. Configure them by hand, or just describe what you want and let the agent assemble it.
Model your company however it really works — divisions, regions, programmes, clients — then let access flow down it.
www.tebelis.ai/organisation
Any shapeBuild a tree of organisation nodes above your projects; nest it as deep as you need.
Cascading accessGrant a role on a branch and it cascades to every project beneath it — most-access-wins, and a direct grant on a project always takes precedence.
Per-person branch grantsGrant a person a branch once and every project beneath it follows. Access to the tree is assigned per person — deliberately, so it's always auditable who can reach what; groups grant roles and permissions instead.
Off by defaultSmall teams can leave the whole organisation layer off and just work in projects; turn it on when a portfolio appears.
Project locations
A spatial spine for every record/form.
Each project carries its own location hierarchy, so every record/form is anchored exactly where the work happened.
www.tebelis.ai
Your structureSite → Building → Floor → Zone, or whatever matches the job — define the levels per project.
Pin & reportAttach any record/form to a node, then filter and report by any level of the tree.
Fast at depthSubtree look-ups stay instant on deep trees (materialized paths), even with hundreds of thousands of records/forms.
Record-safeA node that has records/forms attached can be renamed but not deleted — so you never silently lose history. Turn locations off per project and records/forms simply file at the project level.
anchor to
SiteBuildingFloorZoneEquipmentProduction line
Templates & field types
Templates that fit the trade.
Build inspection, audit, incident, and sign-off templates from a rich set of field types — by hand or by describing them.
Describe to buildTell the agent what a record/form is for; it drafts the fields and you edit and publish.
Versioned on publishEditing a live template publishes a new version. Every record/form keeps the exact version it was filed under, so reporting stays correct over time.
DraftsWork on a template privately and publish it when it's ready.
field types
Short textLong textNumberSingle choiceMulti-selectToggleDate / timePhotoSignatureFile attachmentPerson
Rules in your templates
Templates that react as they're filled in.
Rules turn a static template into a smart one — fields appear, become required, or change their options based on the answers so far and the record/form's state.
Conditional visibilityShow or hide a field based on another answer — e.g. "if the gas test fails, reveal corrective action."
Conditional requirementMake a field required only when it actually matters, not on every record/form.
Field-effect rulesOne answer can set a value, set a default, or constrain the valid options of another field.
State-dependent fieldsFields can appear or lock depending on where the record/form sits in its workflow.
Honest validationRequired markers and value/option checks are enforced on submit — the agent fills only exact, valid values and never invents one.
rule types
Show / hideRequireSet valueSet defaultConstrain optionsLock by state
Workflows
States, transitions, ownership.
Give each template a lifecycle: who owns each step, what moves are allowed, and what happens automatically.
States & transitionsDefine the states a record/form passes through and exactly which transitions are allowed between them.
Owners & auto-assignName who's responsible at each state; the next actor is assigned automatically when the record/form moves.
Conditional & routedBranch the flow on a field value, or route a record/form to a specific person or role.
Edit-locksLock a record/form from edits once it leaves a state, so signed-off work can't be quietly changed.
See the flowThe whole workflow renders as a diagram in the builder and highlights the current state on each record/form.
Roles & permissions
Access in plain English.
A small, legible permission model — no sprawling checkbox matrix — that the agent obeys exactly.
Four built-in rolesAdmin, manager, user, and viewer cover most teams out of the box.
Custom rolesDefine your own role as a named set of permissions with an org-wide or project-only scope.
Groups elevateAdd people to a group to grant access; groups only ever add access, never remove it.
ScopeAccess is org-wide or limited to assigned projects, and the organisation cascade fills in the rest.
The agent inherits youEvery agent action is a permission-gated tool call — it can never do something you couldn't do yourself.