Skip to main content
Custom objects let you model entities not covered by Arya standard objects. Examples: Legal case, Asset, Policy, Supplier, Property, Machinery.

​
When to create one

If you track “Legal cases” with hearing date, judge, role, opposing party — no standard object fits. Create a custom object.
E.g. Contract linked to Customer + Project + Responsible employee with custom fields. Dedicated object keeps explicit relationships.
You want workflows on entity events (e.g. “case moves to In court”). Only objects (standard or custom) trigger workflows.
Before creating custom: check if a standard object + custom attributes suffices. E.g. Supplier often is just Company with type = Supplier.

​
Create a custom object

1

Settings → Objects → + New object

Admin-only.
2

Define

  • Singular name (e.g. Legal case) and plural (Legal cases)
  • Icon (Lucide / Font Awesome)
  • Description
  • URL slug (for API, e.g. legal-cases)
3

Attributes

Add fields: name, date, select, reference to other records. See Attributes.
4

Default views

Which columns, which filters, Kanban view (if has status) or table.
5

Permissions

Who can create, read, edit, delete records of this type.
6

Save

Object appears in sidebar. You can immediately create the first record.

​
Included features

Every custom object automatically has:

Multiple views

Kanban, table, calendar, Gantt (if has dates).

Filters and lists

Static and dynamic as for standard objects.

Automations

Triggers and actions as for standard objects.

AI

AryaChat sees the object and can answer questions.

Import/export

CSV, Excel.

API

Programmatic access via REST and webhooks.

​
Relationships with other objects

Add a Reference attribute to link the custom object to others:
  • Legal case → Customer (Company): every case has a customer
  • Legal case → Lawyer (Employee): who handles it
  • Customer → Legal cases (reverse lookup): on the customer see all their cases

​
Later modifications

You can always add/remove attributes. Caution:
  • Renaming an attribute is safe
  • Deleting an attribute with existing data requires confirmation (Admin)
  • Changing attribute type (e.g. from Text to Number) fails if existing data isn’t convertible

​
Object deletion

Deleting a custom object deletes all its records. Irreversible. Arya requires double confirmation and automatic backup export.

​
Limits

  • Max 50 custom objects per workspace
  • Max 100 attributes per object
  • Max 10 reference nesting levels (to avoid loops)
Extendable on Enterprise plans.

​
Frequently asked questions

Yes, export as JSON → import. Structure definition is replicated; data isn’t.
Yes. Chart builder sees them as any object.
Yes, template library in Settings → Objects → Templates — covers legal, real estate, maintenance, healthcare sectors.