AssetCraft QA Test user guide
AssetCraft QA Test helps a marketing team turn an approved email, landing page or social post into a new one: adapted for another audience, market or language, checked against the brand's rules, approved, and handed to the marketing platform as a draft.
- Workspace
- Adapt
- Canvas
- Checks
- Submit
- Review
- Push or export
- Evidence
What AssetCraft QA Test is
This guide walks through the screens in the order a piece of work moves through them.
Two ideas explain most of what you will see. First, you always start from something already approved, and the assistant fills in approved building blocks; it never designs a layout or writes code. Second, every change is recorded: who or what made it, and why. That record is what reviewers look at, and what the evidence pack prints.
Who does what
What you can see and do depends on your roles. One person can hold several. Nobody can approve something they submitted themselves, so a full round trip needs at least two people.
- Creator
- Adapts approved assets, edits drafts on the canvas, runs checks and submits work for review.
- Brand admin
- Reviews and approves work at the brand stage. Looks after the brand pack in Studio.
- Approver
- Decides at the review stages the approval rules assign to them.
- Rule owner
- Owns the rules behind the checks. The only role that may override a check result that blocks pushing, and only with a written reason.
- Translation reviewer
- Reviews one language version, for example Japanese.
- Organisation admin
- Manages people, packs and instance settings, and is the only role that can push an approved asset to the marketing platform.
Sign in
Which ways to sign in you see depends on how your organisation set up AssetCraft QA Test. There may be one or several.
- Sign in with Microsoft: use your organisation's Microsoft account.
- Sign in with Google: use your Google account.
- Sign in with a code sent by email: type your email address, then the six-digit code that arrives.
- Open the address your administrator gave you.
- Choose a sign-in method. You land on the Workspace.
- You can switch the page between English and 日本語 before signing in.
Signing in with an emailed code
Type the email address you were invited with and choose Email me a code. A six-digit code is sent to that address. It works once and for ten minutes. Type it and choose Sign in.
Codes go only to addresses an administrator has invited, and the page answers the same for every address. If no code arrives, check your junk mail and the spelling of the address, then ask your administrator.
Send a new code replaces the old one. Use a different email address starts again. After five wrong tries a code stops working, so ask for a new one.
Confirm it is me
Some changes, such as inviting people or changing roles, need a sign-in from the last few minutes. If yours is older, the page says so and offers Confirm it is me. Choose it and sign in again; you may be asked for your password or a new code. You then come back to where you were. If you signed in with Google, the message tells you what to do instead.
No access yet
If you sign in with Microsoft or Google but have not been invited, you see No access yet. It names the account you are signed in with. Choose Sign out to leave, then:
- Ask your administrator for an invitation to the email address where you really receive mail.
- If you use Microsoft and your directory account has no email address filled in, ask your IT team to add one, so Microsoft can send it when you sign in.
- If the emailed code is offered, choose Email me a code on the sign-in page with the address you were invited at.
Workspace
Everyone starts here. Assets in the top bar brings you back.
The top half lists approved source assets: the emails, landing pages and posts you are allowed to start from. Each card shows the brand, channel, audience, languages and when it was approved. Below them, My drafts lists work you have started and not yet submitted.
- Narrow the list with Search by name, Channel, Language and Audience.
- Tick Show expired and superseded sources to see sources you can no longer adapt; each says why.
- Choose Adapt this asset on a card to start new work from it.
Adapt: the request and the brief sheet
Creators. Opens from Adapt this asset.
Nothing is drafted until you have checked a short form called the brief sheet: what to make, for which languages and audience, and any facts your request must state. For an event these are the event name, date, venue and registration link.
- Paste or type the request in Your request, as you would receive it in an email. Use an example request fills in a sample.
- Choose Prefill the brief. The assistant fills in only what your request states. Each field it filled is highlighted.
- Check every highlighted field. Changing a field counts as checking it.
- Choose Confirm the brief. If something required is missing, a warning names it. A fact the assistant cannot read in your request is never guessed: you always type it, such as the registration link of an event.
- Choose Start. The draft is built from the source's approved blocks and opens on the canvas.
Canvas: edit the draft
Creators. Opens after Start, or from My drafts.
An asset is a stack of blocks: header, hero, text, table, call to action and so on. The preview shows the result as it will be sent. You edit text in the Inspector, never inside the preview. Blocks are on the left, the preview in the middle, and the inspector and the assistant on the right.
- Select a block in Blocks or in the preview. Its fields appear in the Inspector.
- Edit the text. The page saves on its own a moment after you stop typing; the top bar shows Saving… and then All changes saved once the server has them. If it shows Not saved, check your connection and press Retry; your edits stay in your browser.
- Use Move up, Move down, Add after and Remove where the block allows it. Locked blocks, such as the header, show a lock and cannot be changed.
- Switch between language versions in the top bar. A version marked Needs review has changed since its source.
- Tick Show where text came from to see which text is from the approved source, which the assistant wrote and which a person wrote.
Working with the assistant
The Assistant panel works on the selected block, field or whole asset. Type an instruction such as "Make it friendlier", "Shorten the headline" or "Mention that seats are limited", then ask it to rewrite.
The assistant never changes the asset directly. Each change is a suggestion with a reason, marked AI suggestion, awaiting your decision: removed text is crossed out and new text is underlined. Choose Accept or Reject on each one.
When the assistant offers several options for one field, press Compare under them. Each option is shown in the asset side by side, with the changed field outlined; for a subject line you see it as it will appear in the inbox. Nothing is changed until you press Use this under the option you want.
Checks
Creators run them; rule owners can override. Checks in the canvas top bar.
Checks compare the draft with the brand's rules: approved claims, forbidden words, required legal text, character limits, contrast and more. A summary bar on the canvas shows what needs attention, and the Checks page lists every result, grouped by what happens next. Each result has one of three severities:
- Blocks push: must be fixed, or overridden with a reason by a rule owner, before the asset can go out.
- Needs a human: a reviewer must look at it.
- Advisory: worth reading; does not stop anything.
- Use the "Go to" link on a result to jump to the text on the canvas.
- Apply a suggested fix where one is offered. It arrives as a tracked change.
- Choose Run checks again after editing. Results go stale as soon as you change the draft.
Submit for review
Creators. Submit for review in the canvas top bar.
- Read Who reviews it: the stages and the role that decides each one. Stages in the same step run at the same time.
- Confirm the languages included, and add an optional Note to approvers.
- Choose Submit for review. The checks run again, and the asset moves to In review.
- You can Withdraw from review until the first reviewer decides.
Review
Brand admins, approvers, rule owners and translation reviewers. Review in the top bar.
- The queue is grouped by stage, oldest first. Open an item marked Awaiting you.
- Read What changed from the approved source: counts first, then each changed block, per language.
- Look at the checks, the claims the text cites, and comments. Reply to a comment or Mark as resolved.
- Decide: Approve, Request changes or Reject. Request changes and Reject need a reason. Approving moves the asset to the next stage, or to Approved after the last one.
Push or export
Organisation admins. Opens for an approved asset.
Pushing creates a draft in the marketing platform. AssetCraft QA Test never sends anything to customers; a person publishes from the platform.
- Read Before it goes: the asset is approved, nothing blocks push, the legal footer and unsubscribe link are present, and every language version is reviewed.
- Check the draft name, the campaign tracking parameters and how each block maps to the platform's template.
- Choose the push button, or Export as a zip file for the HTML and plain text of each language.
- For a landing page, Publish the page puts it on the web address shown.
Evidence pack
Anyone who can see the asset. Open the evidence pack from the review detail.
The evidence pack answers "who approved what, when, and on what basis": every version and why it was made, each approver and how they decided, check results with any overrides and their reasons, cited claims, automatic fixes, and every assistant run with the model used. It is assembled from the records, and nobody edits it by hand. Print gives a clean printable layout.
Studio
Brand admins edit and publish; others can look. Studio in the top bar.
Studio holds the brand as data rather than design files. Its sections are: Overview (the brand pack, its version and whether it is a draft or published), Start from approved assets, Components, Tokens (colours and fonts, with a contrast check), Patterns (approved arrangements of blocks), Voice and terms, Claims and rules and Knowledge (documents the assistant may draw on). The checks and the assistant read from here, so a change in Studio changes what they do.
To build a brand pack without writing it by hand, open Start from approved assets, choose emails or landing pages your company already approved and press Read these files. The Studio proposes the colours, type, logo and layouts it found, how sure it is, and which values it could not find. Nothing is approved by reading them.
Read the proposal, give the brand pack a name and press Accept as a draft. The draft opens in the other sections. Nobody creates from a draft: creators keep using the published pack until you publish.
On a draft, change colours and the base text size in Tokens, and the lock level and order of blocks in Patterns; the preview redraws as you go. Press Save as a draft to keep the changes. If the pack cannot be saved, the fields that need fixing are listed. Editing a published pack never changes it: saving makes a new draft with the next version.
When the draft is ready, save it and press Publish on the Overview. From then on every new asset uses that version. Assets that were already made keep the version they were made with. A published version cannot be changed.
Voice and terms and Claims and rules are editable too. In Voice and terms, change the do and do-not rules of each language, one rule per line, then press Save as a draft. In Claims and rules, add a claim or edit one: give its wording, choose the document in Knowledge that backs it (the source) and set the day it expires, if it does. An expired or withdrawn claim no longer counts as a source. Edit the wording of each disclaimer per language there as well. Save, then press Publish on that tab; the rule pack and the brand pack are saved and published separately.
Settings
Organisation admins only. Settings in the top bar.
- Instance: the product name and logo, languages, AI providers and which model does which job, connectors and security.
- People: invite someone, cancel an invitation or remove access, and Edit roles for anyone. A role can apply to the whole organisation or be narrowed to one brand, workspace or language.
- Packs: the brand, rule and approval packs in use.
- Usage: what each AI provider has cost this month against its budget, how many assistant runs completed or failed, how much AI text people kept, and the pilot metrics.
Changing people or security settings asks you to sign in again if your last sign-in was a while ago.
Managing people and usage
Organisation admins only. Settings in the top bar, then the People or Usage tab.
People
The list shows everyone with a status: Active, Invited (not signed in yet) or Removed. Filter it by role or status.
- In Invite someone, type the person's name and the email address they will sign in with.
- Choose the roles to give. For each role, Applies to sets the whole organisation or one workspace, brand or language, and Can see sets whether the person sees all content, partner and public content, or public content only. Choosing a role sets its usual choice.
- Choose Invite. The person is listed as Invited, and the roles apply from their first sign-in with that address. If the address already belongs to someone in the list, the roles are added to that person.
- If the page says you need a recent sign-in, choose Confirm it is me, sign in again and send the invitation again. What you typed is kept.
Edit roles shows the complete set of roles a person will have. Remove one or add one, then choose Save the roles. A person needs at least one role.
Cancel an invitation or remove access
- Cancel invitation is for someone who has never signed in, for example a wrong address. The invitation and its roles are deleted, and the address can be invited again later.
- Remove access is for someone who has signed in. Their roles are removed, every way in is refused, links to approve by email stop working, and an open session ends at their next request. They stay in the list as Removed, so history still names them.
- Re-invite someone who was removed: choose the roles to give and send the invitation. Their access returns with those roles.
Both ask you to confirm first. You cannot remove your own access, and the last organisation admin cannot be removed.
Usage
Budgets this month shows what each AI provider has cost against its monthly budget, and warns when one is close to it or has used it up. Assistant runs counts the runs by status, with tokens and cost for each provider and task, and the cost today and this month. Where a cost is not known, it says so.
AI text kept shows, for each language, how much of the text the assistant wrote stayed as written, how much people edited and how much they rejected, with the number of changes accepted and rejected.
Pilot metrics
Pilot metrics is a baseline of how review is going. It is worked out from records the app already keeps. It shows four figures:
- Cycle time
- Hours from the request that started the asset to its first hand-off: the first push to the marketing platform, page publication or export after approval. Shown as the median, with the number of assets counted.
- First-time pass
- The share of assets whose first finished review ended in approval, with no change request or rejection at any stage, for example 8 of 10. A submission withdrawn before anyone decided is not counted. Tables below show the same rate for each stage, and for each channel and language, when there is data.
- Review rounds
- How many times an approved asset went through review: 1 means approved the first time. Shown as the median and the mean. Withdrawn submissions are not counted.
- Open in review
- How many assets are in review now, and how many hours the oldest has been waiting.
Until something has finished, a figure says so, for example Not enough data. An asset still being worked on counts only towards Open in review.
Language and theme
The switches at the top right change the interface language and the theme (Light, Dark or System). They change the app around your work, not the content: an asset's own languages are chosen in its brief and switched on the canvas. Brand colours appear only inside previews, never in the app itself.
Asset states
Every asset shows its state as a badge. It moves forward through these. Changes requested sends it back to the creator to edit and submit again; withdrawing a submission returns it to Draft.
- Draft
- Checks running
- Ready for review
- In review
- Changes requested
- Approved
- Pushed or exported
- Archived
When you report something
Send your administrator:
- the page address and the time it happened, with your time zone;
- your role, and the asset's name;
- what you did, step by step, what you expected and what happened;
- a screenshot, with the interface language and theme visible.
Say whether you can make it happen again.
Glossary
- Source asset
- An approved email, landing page or post that new work starts from.
- Brief sheet
- The short form of facts and choices you confirm before anything is drafted.
- Block
- One approved building block of an asset, such as a hero, agenda or call to action.
- Pattern
- An approved arrangement of blocks for a kind of asset, such as an event invitation.
- Tracked change
- A recorded change with who or what made it and why. Assistant changes wait for Accept or Reject.
- Claims register
- The list of approved statements and figures, with their source, expiry and where they may be used.
- Override
- Letting a check result through with a written reason. Recorded in the evidence pack.
- Brand pack
- The brand as data: components, colours, voice, terms, claims and disclaimers.
- Evidence pack
- The printable record of versions, approvals, checks and assistant runs for one asset.
- Push
- Creates a draft in the marketing platform. It never sends anything to customers.