Glossary

Platform vocabulary, with the distinctions that matter. Where two terms are commonly confused, they are explained together.

Where to find it

Architect Panel → Data:

• Datastores — where most of the vocabulary below becomes concrete

Architect Panel → Security:

• Permissions — grants
• Record Access Roles — row-level access

Architect Panel → Activity:

• Activity Log — the audit of changes
• Audit Chain — its tamper evidence

The two panels

• Architect Panel — where the application is built: datastores, pages, permissions, automation, integrations.
• Admin Panel — day-to-day administration, including User Administration where users and groups live.

Groups are created in the Admin Panel; what a group may reach is granted in the Architect Panel. This single split accounts for most early confusion.

Data

• Datastore — a description of a kind of record. The table, forms, views, API and audit derive from it.
• Field — one attribute on a datastore, with a type, validation and default.
• Record — one instance.
• Record link — a typed relationship between two records in any two datastores.
• Record numbering — the scheme producing a human reference such as TKT-00042.
• Activity stream — the business timeline on a record.

Two kinds of history

• Activity stream — the record's own story, written for the people working on it, with public and internal entries.
• Activity Log — the technical audit of every change, with before and after, read by administrators.

Similar names, different purposes. A customer question is answered from the first; "why does this field say that" from the second.

Access

• Security group — a collection of users. Permissions are granted to groups, not to people.
• Permission — a grant. Absence of a grant is a refusal.
• Record access role — controls which rows a person may reach, as opposed to which datastores.
• Field permission — access to an individual field.

Interface

• Page — a screen you have described.
• Browse view — a list of records.
• Dashboard block — a component on a dashboard.
• Row action — a button on a row in a list, and a common route to functionality that has no menu entry of its own.

Process

• Journey — a process a record moves through.
• Task — scheduled background work. Most ship disabled and must be enabled deliberately.
• User Input View — a form presented to somebody, often externally, whose submission creates or updates records.

Audit

• Audit chain — the hashes linking audit entries so that alteration is detectable.
• Sealing — periodically fixing the chain head, which is what anchors history in time.
• Record read log — who has read what, enabled per datastore.

Tenancy

• Tenant — an isolated organisation within one installation.
• Entity — a legal company within one tenant, used by finance for separate books and numbering.

These are frequently confused. A tenant is a customer of the installation; an entity is a company within a customer's own group. A single tenant may have several entities.

Integration

• Data source — an external system mapped onto a datastore. Not necessarily a database.
• Data extraction — ingesting structured files or payloads into a datastore.
• API client — credentials for programmatic access.

Worked example

A new administrator is asked to "give Sam access to complaints". Using this vocabulary the task decomposes cleanly: Sam goes in a security group (Admin Panel), the group is granted permissions on the Complaints datastore (Architect Panel, Permissions row action), and if Sam should see only their own team's complaints, that is a record access role rather than a permission.

Recommendations

• Learn the two-panel split first.
• Keep stream and log distinct in how you talk about them.
• Never say tenant when you mean entity.
• Look for a row action before concluding a feature is missing.