Skip to main content

Build a profile from a folder

A new client usually arrives as a folder: the style guide, a glossary, a checklist, a few rules in an email, some bilingual files, perhaps LQA scorecards and old QA reports. Build from a folder on the Profiles page reads all of it and proposes the profile.

Build a profile from a folder, 39 seconds, narrated, with captions.
Read the transcript
  1. Build a profile from a folder. From the client’s own files.
  2. 1. Press Build from a folder.
  3. 2. Name the account and drop the folder. Style guide, glossary, past jobs. A zip works too.
  4. 3. Press Read the folder. It names what each file is and its languages.
  5. 4. Press Continue and check what it will write. Only ticked lines are written.
  6. 5. Press Approve and build. Nothing is written before that.
  7. Next: Learn from your reviewers’ decisions.

How it goes​

  1. On Profiles, press Build from a folder and give it the client's folder: drop the folder on the dialog or press Choose a folder. Your browser packs the files and sends them, up to 100 MB in all; nothing in the folder is changed and hidden files such as .DS_Store are left out. A zip of the folder works the same way, dropped or chosen with Choose a zip, whatever your computer calls its type. With a Dropbox account connected under Settings, Connections (Team and up) you can pick From a Dropbox folder instead: the folder and its subfolders one level down are read once and nothing is written to it.
  2. It reads every file, names what each one is (a glossary, a style guide, a checklist, a bilingual file, a scorecard, a QA report) and which languages it holds, and proposes one profile per language pair. A folder with files in two pairs gets two profiles. A style guide, checklist or rules file that names no language goes to both. You can choose to build only one of them. Divisions are not split: pass a division (Storefront, Support) or split the folder and build each division on its own.
  3. When a file reads Not sure, pick what it is in the list next to it and press Re-read with my answers. A draft may also ask a question or two, for example which of two languages is the source.
  4. Read what it will add: every glossary row, term, rule and guidance line, per profile. The draft shows the name, the base, the languages, the asset counts and the checks it turns on.
  5. Press Approve and build. Before that, nothing is written.

Brands, glossary rows and register​

Under each profile the review step lists three sections: Brands and terms to keep, Glossary rows and Register. Every line shows the words of the guide it came from and the file. Only ticked lines are written; Tick all and Untick all work per section.

  • Lines read from a list or a table are ticked for you: a term list or DNT list, a glossary row whose target is the source, a table in a guide, the list items under a heading such as Trademarks, Brands, Do not translate, DNT, Glossary or Terminology (also in Turkish, German, French and Spanish), and the notes column of a game lockit ("Keep in EN: Wolf Pack").
  • Lines the AI read in a guide's prose wait for your tick: a brand named in a sentence, a whole class such as "all native platform names", "X is Y, not Z" and the form of address, per content type when the guide gives one. The AI reads the whole guide; a name that only appears in an example sentence is left out, and a guide with no instructions about language (a logo guide) is marked and nothing is taken from it.
  • A term kept with a condition is handled for the profile's language: "DNT except in Japanese" is kept in a Turkish profile, "only kept in German" is listed but not written, "always lowercase" also becomes a guidance line.
  • A ticked glossary row is merged with the imported glossary, one row per source term with its forbidden words. A ticked Turkish register turns on Turkish: informal and formal you in one segment at major and adds a guidance line that quotes the guide.

With the AI off, brands and terms come only from lists, tables and those sections. The review then says Brands and terms in this guide need the AI pass. A localisation kit (LocKit), a Client instructions file and other instruction files are read as guides. A file copied into several job folders is read once.

What is built​

The profile, its glossary, its brands and terms to keep, the checklist as rules, the custom rules and the guidance lines from the style guide. LQA scorecards and QA reports go to the new profile's Learn queue as suggestions you approve; Learn comes with Business.

From an assistant​

The same steps are available over the MCP server with the Build permission: the assistant scans the folder, proposes the draft, takes your answers and builds only once you have said yes to the summary. A new proposal replaces your own open draft for the same account, and the assistant can discard a draft when you ask it to.

Drafts​

A draft waits under Drafts on the Profiles page until someone approves it, whether it was made here or by an assistant. Each row shows the profile names and languages, where the draft came from, who made it and when. Open takes you to the review step, where you can answer its questions and approve it. Delete discards the draft after you confirm; nothing in a profile changes. A workspace holds up to 20 open drafts.

Who can do it​

A PM or above. The built profile belongs to the account you named and behaves like any other profile.