# Getting started with the console A tour of the brand-side console screens, in the order in which you use them. Source: https://docs.sealtrust.io/en/console-prise-en-main/ --- By the end of this page, you will know how to open the console, set up what has to be set up before creating anything, produce your first items, and then find each monitoring screen. The walkthrough follows the real order of use, from the first sign-in to the screens you consult every week. This page describes your brand's console. Every screen shows only your data. ## Signing in The sign-in screen asks for your email address and your password. If two-factor authentication is enabled on your account, a second screen asks for the six-digit code. Once signed in, you land on the **Dashboard**. If your session expires while you are working, the sign-in page states explicitly that your session has expired, and you then return to the screen you had left. ## Understanding what the menu shows The sidebar is collapsed to its icons. It opens on hover, and the pin at the top keeps it open. Entries are grouped by section, and each section collapses. Two settings decide what you can open: your usage profile and your plan. Both produce the same behavior in the sidebar. The entry stays visible, grayed out, with a "Pro" mention and a padlock. Clicking it opens a pre-filled message to talk to us about it. Nothing is removed from the sidebar. You change your usage profile at any time from **Settings** then the **Brand** tab. Four profiles exist. | Profile | What it opens | | --- | --- | | Basic anti-counterfeiting | Read-only mint tracking, certificates, consumer verification. Minting and encoding are operated by SealTrust. | | Anti-counterfeiting + EU DPP | The previous one, plus digital product passports. Minting and encoding remain operated by SealTrust. | | Full traceability suite | The previous one, plus the supply chain, the connectors, ownership transfers, and mint and encoding orders. | | Custom | Everything, with no filtering. | The tab bar of **Settings** behaves differently from the sidebar: it really removes the tabs your profile does not open. The Integrations tab disappears for the Basic anti-counterfeiting profile. The Multisig tab disappears for the Basic anti-counterfeiting and Anti-counterfeiting + EU DPP profiles. > [!INFO] A shortcut that is useful right away > Ctrl + K, or Cmd + K, opens the command palette. There you search for a screen or a product without going through the menu. ## Getting started, the commissioning checklist The **Getting started** screen is the first entry in the menu. It presents eight steps, in this order: Account setup, Product catalog, Choose the carrier then mint, Digital identity, DPP compliance, ERP integration, Analytics & tracking, Consumer experience. Each step expands and contains sub-steps, and most offer a button that takes you to the screen concerned. Six steps out of eight check themselves off: the console verifies that data of that kind already exists on your side, and marks the step as done without your having to click. Watch out for the ERP integration step, which checks itself off as soon as an API key exists on your account, without looking at whether a connector is plugged in. The last two steps, Analytics & tracking and Consumer experience, are checked off by hand. A progress ring at the top shows where you stand. > [!ATTENTION] The button on the Account setup step leads nowhere > From your account, this button and the one on its first sub-step take you back to the dashboard. To carry out this step, open **Settings** then the **Brand** tab. ## Setting up the brand before producing Open **Settings** then the **Brand** tab. Three blocks are there. The first is the choice of usage profile described above. The second is visual customization: your logo and your two colors. This block opens if your plan includes brand customization. Otherwise it displays a box indicating where that right begins. The third contains two switches, one for product returns, one for buyback. ## Creating a product model A model describes a product once, and then serves to manufacture items. Go to **Catalog** then **Product models**. The creation form asks for a name, an internal reference, a category, a description and an image. It also accepts, in the same record, the regulatory information: GTIN, customs code and customs description, CE marking, number and address of the declaration of conformity, EU type-examination certificate, weight in grams, volume in cubic centimeters, and the addresses of the repair, maintenance and safety documents, of the user manual, of the spare parts and of the disassembly instructions. > [!ATTENTION] The category is not optional > A model with no category cannot produce a batch. The mint button stays inactive as long as the category is not filled in. ## Minting a batch from a model SealTrust operates the physical minting and the encoding of the chips for the Basic anti-counterfeiting and Anti-counterfeiting + EU DPP profiles. With those two profiles, you follow progress read-only and the mint button does not appear. This section describes what the Full traceability suite and Custom profiles see. From a model's record, the **Mint a batch** button opens a panel that asks for five things. | Field | What it expects | | --- | --- | | Quantity | Between 1 and 10,000 items. | | Production date | Pre-filled with the current day. | | Batch code | Pre-filled in the form reference, date, time. You can replace it. | | Manufacturing site | Free text, optional. | | Authentication method | NFC, QR, or NFC + QR. | The authentication method decides what follows, and it changes the label of the confirmation button. - With QR only, the button becomes "Create + Generate QR codes". You land on the batch record, where the console produces the codes. - With NFC only, the button becomes "Create + Encode tags". - With NFC + QR, the button becomes "Create + Encode tags and QR codes". As soon as NFC is included, the console adds the batch to the encoder queue, because a chip comes out of manufacturing empty. The console numbers the items. A batch of ten items named from the model gives items numbered 001 through 010, each one carrying an external reference formed from the batch code and its number. > [!DANGER] The "Sealed batch" option cannot be undone > It puts the seal into service on every chip in the series. That is permanent on the chip. The labels must be NTAG 424 DNA TT tags with an intact tamper loop. This option has no effect on a QR-only batch. ## Tracking production batches **Catalog** then **Production batches** lists your series. A batch carries one of these four states: Draft, In progress, Minted, Anchored. The screen's state filter offers two of these values, Draft and Anchored. Anchoring on the Base chain, chain ID 8453, is an operation that SealTrust triggers batch by batch. Most batches are never anchored. The Anchored state means that the batch's hash has been recorded on that chain. A batch's record shows the progress of the minting, the state of the encoding jobs when there are any, and offers to retry the failed items. The link to the production wizard, which writes the chips of a series, appears on that same record for the Full traceability suite and Custom profiles, when the batch carries a chip and an encoding job exists. ## Creating products one at a time or from a file **Catalog** then **Create a product** offers three tabs: Single product, Batch (multiple products) and From CSV. **Single product** creates one item at a time. You choose the brand, the category, the model and the authentication method. **Batch (multiple products)** opens a table where you enter several rows by hand. Each row asks for a name, a brand, a category, a model and an authentication method. A button adds a row, a cross removes one. **From CSV** imports a file. Three columns are mandatory: `product_name`, `brand_id`, `category_id`. The screen displays the list of the optional columns it knows how to read, and it reports three things before the import: the missing mandatory columns, the columns present twice once spaces are stripped, and the columns it does not know and will ignore. The import rejects rows whose number of cells does not match the header, giving the row number. > [!ATTENTION] The partner API requires one more column > The batch mint endpoint of the partner API requires a fourth mandatory column, `metadata_uri`, which the console import does not expect and fills in itself when it is missing. A file accepted by the console is therefore refused by the API until you have added that column. This path creates only items identified by QR: the server sets the authentication method and the identifier of each item itself. For NFC items, go through the console. ## Issuing certificates The **Certificates** screen issues and manages certificates of authenticity. Two buttons at the top: "Issue a certificate" for one item, "Batch issuance" for several. Batch issuance offers three ways to designate the items: from an issuance batch, from a filtered search, or by pasting a list of identifiers. The limit is 100 items per grouped issuance, and the confirmation button stays inactive beyond that. An optional note applies to all the certificates issued, and the result indicates how many were requested, succeeded and errored. Four counters summarize the state: total, active, revoked, expired. The list is filtered by free-text search and by state. ## Preparing for DPP compliance The **DPP compliance** entry brings together seven tabs: Compliance, DPP templates, Substances, Vocabulary, Access rules, EPCIS, DPP passports. There you note your level of readiness, you define the passport templates, you declare the regulated substances, you align your vocabulary, you decide who sees what in the passport, and you consult the passports produced. For the Basic anti-counterfeiting profile, this section stays visible in the menu but grayed out, and opening it by its address takes you back to the dashboard. Change profile in **Settings** then **Brand** to reach it. ## Tracking the life of products **Product events** keeps the lifecycle history: repairs, warranties, resales. You can also create an event there by hand. **Returns** and **Buyback** list the requests in all cases. As long as the corresponding switch stays off in **Settings** then **Brand**, the screen displays an activation banner and the actions stay inactive. Requests already recorded remain visible. **Claim rules** defines who can claim a product of your brand, and until when. You set one rule per sales channel. ## Opening up distribution and accrediting partners These two screens are in the **Analysis & Audit** section of the menu. **Distribution** shows activations, the coverage of your sales network and gray market monitoring, with a map and breakdowns. **Partners** serves to accredit the repairers and recyclers who will work on your products. The list gives, for each one, the name, the email address, the type, the state, active or revoked, and the date added. Two actions on active rows: resend the invitation, revoke the accreditation. A revoked row carries no action any more. An accredited partner works from a separate partner portal, with its own account. ## Reading what comes back The **Analysis & Audit** section contains six screens: Analytics, Distribution, Partners, Scan map, Activity log, Alert center. Distribution and Partners are described just above. **Analytics** gives scan trends, geographic distribution and the conversion funnel. **Scan map** places authentications on a map. **Activity log** lists the actions carried out within your perimeter. **Alert center** brings together in a single view the security, system and integration alerts. Each alert carries a type among Security, System, Webhook and Scan, and a severity level, from critical to information. Clones and products reported stolen both appear under Security. The screen's type filter offers Security, System and Webhook, plus the option that displays all types. Scan alerts cannot be filtered. The **Dashboard** gathers the essentials: active products, total scans, conversion rate, clone alerts, stolen products. A period selector at the top, and two outputs, a CSV export and a PDF print. ## The rest of the settings The **Team** tab invites the members of your brand. The invitation asks for the email address, the first name, the last name and an initial password that the console can generate for you and that you pass on to the person. The number of accounts is capped by your plan, and the screen displays the counter. You remove a member from the same list. The **My account** tab enables two-factor authentication. You scan a QR code with your authenticator app, you enter the six-digit code, then the console displays backup codes. You can regenerate them later. The **Developers** tab contains two blocks: your API keys, and your notification subscriptions with their delivery log. A key's secret is displayed only once, when it is created, in a window with a copy button. After that, only a short prefix lets you recognize it in the list. The two blocks depend on distinct rights in your plan: API access for the keys, outbound notifications for the subscriptions. When a right is missing, its block stays displayed, grayed out and inactive, under a padlock indicating that you have to change plans. The **Integrations** tab plugs in your existing tools. Eleven connectors are offered: Shopify, WooCommerce, PrestaShop, Salesforce, SAP, NetSuite, Dynamics 365, HubSpot, Odoo, Akeneo PIM, Salsify. Without the right to ERP connectors in your plan, this block stays displayed, grayed out and inactive, under a padlock. The second block of the same tab records your Slack and Teams notification addresses, and stays usable whatever your plan. This tab disappears from the bar for the Basic anti-counterfeiting profile. The **Billing** tab manages your subscription and your invoices. It displays the current plan, the billing rhythm, monthly or annual, four counters for the period, and the list of your invoices. Two of those four labels are confusing. The counter titled "NFC tags" actually counts all the products created over the period, whatever their identification method, QR included. The "Scans" counter counts the recorded authentication reads, those of the QR code as well as those of the NFC chip. The two other counters, "Mints" and "API calls", do cover the mints and the calls to the partner API. The **Domain** tab displays your brand's consumer address, its verification state and the DNS records to set up. You relaunch the verification from this screen once the records are published. To set up this domain, or to change it, write to `contact@sealtrust.io` with the domain name you want. Choose it once and for all: the address goes out engraved in every chip manufactured, and a chip already fitted cannot be rewritten remotely. This tab requires the white-label plan. When the right is missing, the tab stays visible and indicates where that right begins. The **Multisig** tab lists the signing wallets attached to your brand and the transactions awaiting approval, which you approve and then execute from this screen. It appears in the tab bar only for the Full traceability suite and Custom profiles. The **Reversibility** tab lets you leave with your data. One button, "Request a full export", starts the build in the background. The export contains everything, media included. Below it, a table keeps the history. Each row indicates its number, its state, the number of units, of passports and of media files, and its size. A download button appears on the row when the export is ready. ## Where to go next - [Creating products](/en/creer-des-produits/): creating one at a time, in batches and from a file, in detail. - [Partner API, overview](/en/api-vue-ensemble/): the endpoints available and what each one does.