Help and user guide

buildrecord keeps a digital product passport for every unit an organisation builds: a permanent identity printed on the product, and the versioned record that identity points at, from line-off to end of life. This page is the guide; the short version is the .

Getting started

You were added by your organisation. AmberLogic or your organisation admin created your account and emailed you a one-time link to set your password. The link works once and for about a day; if it has been used or has expired, ask them for a new one. Sign in with that account; if you belong to one organisation you land on its projects page, otherwise on a list of your organisations.
Accept the software agreement. The first time you sign in you are shown the buildrecord software agreement and asked to accept it. You are asked again only if it changes.
Take the tour. It opens on your first visit and explains projects, units, passports and your role. Replay it any time from Getting started at the foot of a page.
Open a project. You see the projects you have been given access to. A project lists its units, newest first, and lets you mint more if your role allows.
Stuck? Ask a question; it reaches AmberLogic support with your name and the page you were on, and we reply by email.

Signing in

Your buildrecord account is an AmberLogic sign-in: the same username and password on every AmberLogic app. If your account was never set up, ask your organisation admin or AmberLogic.

Forgotten your password? Use Forgot password? on the sign-in screen and give your email address. If there is an account for it, you receive a message with a one-time link to set a new password; the link works once and for about a day. The page says the same thing whether or not an account exists, so if nothing arrives, check your spam folder and that the address is the one on your account.

Two-step sign-in. Under Sign-in security you can add a passkey, an authenticator app or backup codes. Some organisations require it: you then see a page saying so until you have added one and signed in again with it. Your other organisations are not affected. To remove a method, or if you have lost the device, tell AmberLogic.

Sign out is in the header. Sessions end by themselves after eight hours of no use and after a week at most.

No organisation yet? If you sign in and see "not in an organisation yet", the account you used is not the one that was invited, or your organisation has not added you. Request access on that page tells AmberLogic; say who invited you.

Organisations, members and roles

Everything belongs to an organisation: its projects, units, passport records and templates are visible only to its members. You can be a member of several organisations; the header shows which one you are working in, and the projects page lets you switch.

Each member has an organisation role. The two you start with:

Organisation admin: manages members, groups, roles, templates, units and the organisation's settings, and can do everything on every project.
Member: no rights by themselves. What a member may do on a project comes from the groups they are in (each group carries a project role such as editor or viewer) and from being appointed a project admin.

Organisation admins can rename these roles, change what they allow and add more. If a page or button you expect is missing, it is almost always a role or group question: ask your organisation admin.

An organisation on a Trial sees the badge next to its name. Trial organisations mint freely and can have a handful of projects; to move to a full plan, contact AmberLogic.

Projects

A project is one product line, model year or build: a battery pack design, say. It has:

a slug, a short lower-case name that is part of every printed link and cannot change once set;
a passport template chosen from the organisation's templates when the project is created, which decides which fields a passport has and who may see and edit each one;
an optional logo, shown with the organisation's above every unit's passport and on the page a scan reaches;
its units, with the newest at the top; Find a unit on the projects page covers the rest.

Project admins can appoint project groups, name the project's own states, set the project's logo, decide where a scan of its labels leads and, where the template allows, adjust the template for their project alone. All of that is on Project admins, groups and access, linked from the top of the project page.

Units and identifiers

Minting creates identifiers for new units, up to a batch at a time, and is done at line-off. Each identifier looks like K7M-3PA: six letters or digits with a check character, so a mistyped or misread id is refused rather than pointing at the wrong unit. Hyphen and case do not matter when you type one.

Every unit is printed with a permanent link, https://61406.co/code/K7M-3PA, that never changes and always leads to that unit's record. The code is the project's own five-character code, shown on the project page; a project may instead carry a chosen name there, arranged with AmberLogic. The line printed under the symbol is that link without https://. If you are signed in and may see the project, scanning it opens the unit page; pasting the link or the id into Find a unit does the same. Anyone else who scans it reaches the public page described under What a scan shows.

The unit page's Label panel shows that link as a QR code or a Data Matrix in the IEC 61406-1 frame with the id beneath, and, for roles allowed to download labels, offers each as PNG, SVG or PDF. The Label section of the passport sets the code's size in mm and in pixels, the printing resolution and the preferred format; until it is filled in, labels use 20 mm at 300 dpi.

Minting draws on the organisation's units: an allowance AmberLogic grants, which organisation admins can reserve for particular projects. If a mint is refused for want of units, the message says whom to ask. Organisations on a Trial mint freely during the trial. There is also a pace: at most one mint request every few minutes per organisation, shown on the mint form.

What a scan shows

A scanned label goes through https://61406.co to buildrecord. What appears depends on who is scanning:

A member who may see the project is taken straight to the unit page.
Anyone else, signed in or not, sees the unit's public page: the project's logo (or the organisation's), the organisation's name, the identifier, the status and, once the passport is published, the fields its template marks as public. Fields kept for the team or for particular groups never appear there. A draft reads "not yet published"; a withdrawn record says so; a record with nothing public says that too.

The public page has three ways on. View details leads to buildrecord's detailed view, which asks the person to sign in, or to a page of your organisation's own if it has set one. Request more info is a short form (name, email, message) that reaches AmberLogic, who reply by email and pass the question on. Sign in brings a member back to the same unit afterwards.

Organisation admins choose where View details goes under Where a scan leads on the organisation settings page, and can send a scan of a published unit straight to their own page with no buildrecord page in between; a project can override either. An identifier that buildrecord does not recognise shows a plain "not found" page, and ids cannot be guessed from one another.

Passports

The unit page shows the passport record: the fields the project's template defines, as far as your role may see them, under the organisation's and the project's logos where they have been set. Fill in the passport (or Edit) opens a form; saving creates a new version. Nothing is ever overwritten and every version stays, with who saved it and when. A unit's first form comes pre-filled where the template can guess (the previous unit's values, the unit id, the mint date); you can change anything before saving.

The template decides, field by field, who may see and edit it: the team, groups such as customers or authorities, or the public. What the public may see is exactly what a scan shows to someone outside the team.

A passport has a status. Draft is where a unit starts. Publish when it is ready to be shown outside the team; publishing locks the fields the template does not keep editable. Withdraw if it must no longer be shown; only an organisation admin can re-publish. Some projects define their own states (for example in service, returned); setting one sets the status to match.

Fields marked with * on the unit page come from somewhere other than the form, such as the template's defaults or another system. The History panel at the foot of the unit page lists every action on the unit and which fields each version changed.

For organisation admins

The Manage line at the top of the projects page links to everything below. A sensible first hour: adopt a passport template, create a project, add your team, mint one unit and fill in its passport.

Members: add a person by their sign-in email or username and give them an organisation role. Someone whose account does not exist yet is created and invited by AmberLogic; ask us.
Groups: the organisation's audience groups (customers, legitimate-interest parties, authorities) and any you add; a group can carry a project role, and templates can show fields to a group.
Roles: what each organisation and project role allows; reset to defaults at any time.
Passport templates: adopt a built-in template (a generic unit, the EU battery passport and a demo battery pack) or publish a new version of your own, in a grid or as JSON. A template can be renamed, copied as a new one (shared with the organisation or private to one project) and downloaded as JSON. Every project names one; a new organisation adopts a template before it can create a project.
Units and allocations: the organisation's pool, per-project reserves and low-water marks (a percentage of the units granted or reserved, 10% unless changed; the organisation is emailed when a balance falls to it), requests from project admins, and the notifications that were sent.
Organisation settings: the plan; the organisation's logo; where a scan leads; whether two-step sign-in is required for every member; and the organisation's notification list, the members and email addresses told when units run low or a project asks for more.

Each project also has an admin page (Project admins, groups and access) for appointing project admins, deciding which groups apply to it, its own states, its logo, its own where a scan leads and its own notification list. A project without a list falls back to the organisation's, and that to the organisation admins.