Words used in kvyk.ai

Administrator: the management role that may do everything in an organisation. See Roles and access.

Allowance: how much of the assistant your organisation’s plan gives it in each window, in credits. See Assistant use and limits.

Allowed service: a service outside kvyk.ai that your automations may call, approved by an Administrator. See Allowed services.

App: a page or small website on your organisation’s data, built by the assistant. See Build an app with the assistant.

API key: lets another system use your organisation’s API in one stage, as its machine member. See API keys and webhooks.

Assistant: helps you in plain words and acts as you, with your access. See The assistant.

Audience: who can open an app: all members, chosen data roles, departments or members, or anyone. See Choose who can open an app.

Automation: work kvyk.ai does by itself when something happens, at set times, or when someone starts it. See Automations.

Builder: the management role that changes the data model, data roles and apps, and publishes them.

Connector: links your organisation’s own account at an outside service, such as Mollie for payments, to kvyk.ai, so your apps can use it. An Administrator adds it in Settings, then Connectors, and connects it there, for Preview and for Live separately. See Connectors.

Credit: the unit the assistant’s work is counted in: the more it does for a message, the more credits it takes. See Assistant use and limits.

Custom domain: a domain of your own, such as shop.example.com, on which a published app opens too. See Put an app on your own domain.

Customer: someone your organisation keeps for its apps. A customer never signs in to the dashboard and never holds a management role; the data roles you give them say what they see in your apps. Each has a record of the built-in Customers entity. See Customers.

Data model: what your organisation keeps track of: its entities, their fields and the links between them. See Build your data model.

Data role: says which records its holders may read, add, change, delete, share and assign, entity by entity.

Department: a part of your organisation, such as a shop or a kitchen. Access can follow departments. See Departments.

Deployment: the page that lists the data model’s changes waiting in Preview one by one, where you can take them back before they are published.

Entity: a kind of thing you keep records of, such as Customers or Shifts.

Event log: everything that happened in the organisation, and who did it. See The event log.

Field: something each record of an entity holds, such as a name or a date.

Link: connects the records of two entities, such as each order to a customer, or many to many, such as products and their ingredients. A link to people holds members or customers instead, such as a shift’s volunteers.

Live: the stage with your real records, where your team works. See Preview and Live.

Machine member: a member with a name and no email address that never signs in and works only through its API keys, with the data roles you give it. See API keys and webhooks.

Management role: Administrator, Builder or Member: what someone may set up.

Member: someone in an organisation; also the management role that works with records but sets nothing up.

Not signed in: the built-in data role for visitors of a public app who have not signed in. It shows them nothing until you give it read access. See Choose who can open an app.

Note: something the assistant remembers. See What the assistant remembers.

Options field: a field that offers a fixed list to choose from.

Organisation: your business on kvyk.ai, with its own data, people and settings.

Owner: the person a record belongs to. See Owners and sharing.

People: the page that lists everyone in an organisation, its members and its customers. See Invite people.

Placeholder: a place in a template that is filled in with a record’s detail, such as the customer’s name. See Templates and documents.

Plan: what your organisation has of kvyk.ai, Free or Pro, such as how many apps and members and its assistant allowance. Plans belong to the organisation, not to its members. See Plans and their limits.

Preview: the stage for trying changes, with test records only.

Publish: take what you tick in the publish panel from Preview to Live, all at once; what you leave unticked keeps waiting. See Publish and discard changes.

Record: one of the things you keep track of: one customer, one shift.

Run: one time an automation ran, with what each step did. See Runs.

SBOM: a version’s software bill of materials, the full list of the packages it is built from. See Publish an app.

Secret: an entry of Variables and secrets that never reaches a browser; only kvyk.ai’s servers use it, and its values are never shown again once saved. See Variables and secrets.

Share: give one person access to one record.

Sign-in page: the page on a public app’s own address where your customers sign in with a code from a mail in your organisation’s name. One sign-in opens all your public apps. See How customers sign in to your apps.

Stage: Preview or Live.

Step: one change the assistant made to an app, which you can undo. See Build an app with the assistant.

Template: an email or a document, such as an invoice, designed once and filled in with the details of one record. See Templates and documents.

Variable: an entry of Variables and secrets your apps may read in the browser, with a value for Preview and one for Live. See Variables and secrets.

Version: an app as it was built once from one of its steps, never changed after. Preview serves the newest, Live the one you published, or another one it served before that you put it on. See Publish an app and Go back to an earlier app version.

Webhook: an address another service calls to start an automation, checked with a secret. See API keys and webhooks.

Status: the field every entity has, Active or Inactive to begin with.