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 sent you a one-time link to set your password. Sign in with that account; if you belong to one organisation you land on its projects page, otherwise on a list of your organisations.
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 you forget your password, use the forgot password link on the sign-in screen; if your account was never set up, ask your organisation admin or AmberLogic.

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.

Sign out is in the header. Sessions end by themselves after a period 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 and units, 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.

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;
its units, with the newest at the top; Find a unit on the projects page covers the rest.

Project admins can appoint project groups and, where the template allows, adjust the template for their project alone.

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/slug/K7M-3PA, that never changes and always leads to that unit's record. Scanning it as a signed-in member opens the unit page; pasting it into Find a unit does the same.

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.

Passports

The unit page shows the passport record: the fields the project's template defines, as far as your role may see them. 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 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.

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 (the EU battery passport is one) or publish a new version of your own; every project names one.
Units and allocations: the organisation's pool, per-project reserves and low-water marks, requests from project admins, and the notifications that were sent.
Organisation settings: require two-step sign-in for every member; the organisation's notification list.

Each project also has an admin page (Project admins, groups and access) for appointing project admins and deciding which groups apply to it.