Settings
Fields, pipelines and stages, people and access, brands and legal entities, branches, reference lists, automation. · 13 articles
Settings: overview“Settings” is the one place in all of Helomi where you configure fields, pipelines, access, warehouse, finance, documents, and automation yourself, without a developer. The main “Settings” page shows all groups at once and searches by name and across the WIKI, and the page of the selected item fills the whole window; changes show up right away in sections, on the phone, and in what AI employees see.Data types and fields“Data types” is where you decide for yourself which fields make up a client, deal, product, task, additional contact, and “Finance” operation: which fields exist, which are required, what shows in the list, the creation form, and the card, and in what order. Change something here — and you see it right away in the section, on the phone, in imports, and in what AI reads, without a single code change.Pipelines, stages, transitionsA pipeline is a deal's path from creation to closing, split into stages such as “Created,” “Sent,” “Won,” and so on. Here you set up your own pipelines, stages with colors and roles, what happens to stock and payment when a deal reaches a stage, who can see the pipeline, and which stages a deal can move between.People, roles, accessThis is where an administrator decides who works in Helomi and what each person can see and do: which menu sections are open, whose deals and clients are visible, who can delete, see phone numbers, or make payments. The same permissions apply to AI employees — they work like regular people with limited access.RolesA role in Helomi is the default view for a job title: what a person sees on screen first. Managers get deals, clients, and tasks; warehouse staff get the warehouse and deliveries; accountants get finance and documents. A role sets the pinned menu, list columns, and the “Main” section of the deal and client cards; everyone can then adjust it to suit themselves. A role doesn't change permissions: who can open what is decided by the checkboxes in “Menu sections” and “Access.”Brands and legal entitiesA brand is what you sell under (a store, a website, a trademark), and a legal entity is the sole proprietor (FOP) or LLC in whose name invoices, documents, and fiscal receipts are issued. These are two separate directories: several legal entities can work under one brand, and one legal entity can serve several brands; a deal gets the right legal entity automatically based on your rules.Branches and structureA branch is an office, store, or warehouse: it holds stock, people work there, and deals are processed there — and every branch is also a warehouse. On the “Branches and structure” page you keep a single list of branches and mark which brands are sold from each one and which legal entities operate in it. Based on these links, every deal gets its brand, branch, and legal entity automatically, and the deal card shows where each value came from.DirectoriesDirectories are short lists people pick values from in cards: client and deal sources, tags, task types, wallets, finance categories, currencies, segments, branches, units of measure. You manage them yourself in “Settings”; renaming changes the name in all records at once, and a value that's already in use somewhere doesn't vanish without a trace — it's only archived.Transfer rules between sectionsПравила передачі роблять те, що інакше довелося б зашивати в код: поле одного розділу само потрапляє в поле іншого. Склад передає назву товару в «Назву Checkbox» прайс-листа й собівартість — у позиції відкритих угод, клієнт передає сегмент у свої угоди, угода дає назву своїм завданням, ремонт з власного розділу пише модель пристрою в картку клієнта. Налаштовує людина в «Налаштування → Інтеграції й автоматизація → Правила передачі», код тут не потрібен.TriggersA trigger is a rule: “when X happens in the CRM, do Y.” An order with “Prom payment” → fill in “Checkbox payment type”; a deal in “Received” → fiscal receipt; a deal in “Sent” → SMS to the client; a new deal → task for the manager. The server runs triggers on its own, without a person or AI, and every firing shows up in the log. The actions match KeepinCRM (section 3a).WebhooksAn incoming webhook is an address that a third-party service (a WooCommerce site, a Contact Form 7 form, Weblium, WIX, Facebook Leads) sends a lead or order to, and Helomi creates a contact, a deal, and a task from it on its own, based on your field mapping. Outgoing webhooks work the other way around — Helomi sends data to another service; they're set up with triggers.What's used“What's used” is a page that shows what people in Helomi actually open and click: pages, menu items, buttons, “⋮” items, settings toggles, card fields. It helps you decide what to keep on screen and what to move one click away so Helomi stays simple. Only numbers are counted — which element, who, on which day, and how many times; the contents of deals and clients, and any texts, aren't collected.Plan and billingYour company's Helomi subscription: you build the plan yourself in the calculator — people, “Full AI,” live Telegram and Viber accounts, volume, monthly or yearly billing — and see the price right away; the invoice comes in hryvnias at the NBU exchange rate, payment is by bank transfer, and you can change the setup at any time. Telegram and Viber bots are free. The first 14 days are free, no card required. This item is visible in multi-organization mode (when Helomi runs as a platform for many companies).