> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/personas/working-with-personas/batch-and-bulk-operations/persona-details-reference.md). # Persona Details reference The `Persona details` spreadsheet is the bulk create/edit format for the Conducttr persona library (`Personas > Bulk changes`). Export an empty or populated library, edit, reimport. 71 columns in a single sheet, row 1 headers, one persona per row. Layout: | Block | Columns | Covers | | -------- | ------- | ---------------------------------------------------------------------------------------- | | Identity | 1–12 | Name, handle, faction, disposition, empathy, tags, beliefs, RP, email, bio, goals, image | | `Tw*` | 13–30 | MicroBlog profile, history and engagement | | `Fb*` | 31–48 | GoSocial profile, history and engagement | | `Ig*` | 49–60 | InstaMedia profile and history | | `Tg*` | 61–67 | Telegraph profile and history | | Trailing | 68–71 | GPS, Permissions, Show, WebsiteViews | The four social blocks repeat the same shape, so a persona can carry a different display name, handle, avatar and follower count per channel. They are **not** auto-filled from the identity block - a blank `TwName` means a blank name on MicroBlog, not a fallback to `Name`. *** ## Identity block | Column | Format | Notes | | ------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Name` | Text | Required. | | `Handle` | Text, no spaces | Required and unique. Used for persona replacement matching between libraries, and as the key in persona smartwords: `{persona._handle_.name}`. Not seen by players. | | `Faction` | Text | Free text - creates the faction if it doesn't exist. Affects AI content generation and Pattern of Life voice. A leading underscore (`_Digital Youth`) appears in production files as a naming convention for grouping, not a syntax requirement. | | `Disposition` | Number, −5 to +5 | Stance toward the training audience, hostile to supportive. Range is -5 to +5. Default 0 if unset. | | `Empathy` | Number, −3 to +3 | Confrontational to conciliatory tone. Range is -3 to +3. Default is 0. | | `Tags` | Comma-separated, unquoted | Freeform, 30 chars per entry. Searchable and filterable in the library. Not consumed by the simulation, so safe for classification schemes (`DEM_MALE,EW_K5`). | | `Beliefs` | Comma-separated (assumed) | Unused at this time | | `RP` | `0` / `1` | Role-player flag. | | `Email` | Email address | Required for the Email channel. Also the login address when the persona matches a player. | | `Bio` | Text | Designer-facing description. | | `Goals` | Comma-separated quoted strings | Unused at present | | `Image` | URL | Master profile image. Per-channel `*ProfileImg` overrides it for that channel. | *** ## Social blocks — `Tw` (MicroBlog), `Fb` (GoSocial), `Ig` (InstaMedia), `Tg` (Telegraph) | Column | Present on | Format | Notes | | ----------------------- | -------------- | ------------ | -------------------------------------------------------------------------------------------------------- | | `*Name` | Tw, Fb, Ig, Tg | Text | Display name on that channel. | | `*Handle` | Tw, Fb, Ig, Tg | Text | Channel handle -independent of the master `Handle` and of each other. | | `*Verified` | Tw, Fb, Ig | `0` / `1` | Verified badge. | | `*Created` | Tw, Fb, Ig | `YYYY-MM-DD` | Account creation date shown on profile. | | `*Bio` | Tw, Fb, Ig, Tg | Text | Channel bio. | | `*ProfileImg` | Tw, Fb, Ig, Tg | URL | Avatar for that channel. | | `*BgImg` | Tw, Fb, Ig, Tg | URL | Header/banner image. | | `*Followers` | Tw, Fb, Ig | Integer | | | `*Following` | Tw, Fb, Ig | Integer | | | `*Posts` | Tw, Fb, Ig | Integer | Displayed post count - cosmetic, independent of `*History`. | | `*Subscribers` | Tg only | Integer | Telegraph's equivalent of followers. | | `*History` | Tw, Fb, Ig, Tg | See below | Back-catalogue of posts shown on the profile before the exercise starts. | | `*Website` | Tw, Fb, Ig | Domain | `www.islanddaily.com.gl`. Intended for use by organisations to link from social media profile to website | | `*CmtLo` / `*CmtHi` | Tw, Fb | Integer | Comment count range per post. | | `*LikeLo` / `*LikeHi` | Tw, Fb | Integer | Like count range per post. | | `*ShareLo` / `*ShareHi` | Tw, Fb | Integer | Share count range per post. | **Engagement ranges exist on Tw and Fb only.** Ig and Tg have no Lo/Hi columns, so InstaMedia and Telegraph engagement can't be set from this sheet. Engagement defaults by influence category, for reference when filling the ranges by hand: | Category | Followers | Comments | Likes | Shares | | ----------- | --------- | --------- | ------------- | ----------- | | Influencer | 400k+ | 200–2,000 | 8,000–40,000 | 500–5,000 | | Entertainer | 400k+ | 300–3,000 | 10,000–50,000 | 1,000–6,000 | | Commentator | 100k–400k | 100–800 | 2,000–15,000 | 200–2,000 | | Geek | 5k–10k | 5–50 | 150–800 | 10–80 | | Regular | up to 1k | 0–10 | 5–50 | 0–5 | ### `*History` format One post per line, lines separated by a newline **inside the cell** (stored as `_x000d_\n` in the XLSX XML). Each line is a three-field CSV record: ``` "post text","image URL","age" ``` * **text** — always quoted * **image URL** — quoted URL, or empty with the commas retained: `"text",,"2days"` * **age** — how long before exercise start the post appeared, as a relative offset: `6hours`, `394hours`, `2days` Example, two posts, one with an image: ``` "Some people say the harshest punishment is spending time alone.","https://…/photo.png","6hours" "Redland keeps testing our spine because they think we'll blink.",,"2days" ``` *** ## Trailing columns | Column | Format | Notes | | -------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `GPS` | `lat, lng` | `21.261549679644897, -157.80192864443518`. Geolocates the persona's posts and articles - required for InfoMap. | | `Permissions` | Comma-separated positions | Which positions may impersonate this persona — `red, blue, facilitator`. On import, **positions named here are created if they don't already exist**, so a typo silently adds a stray position to the exercise. | | `Show` | `0` / `1` | Social graph visibility. `0` hides the persona from all social graphs. | | `WebsiteViews` | Integer | Displayed view count on the persona's website. Organisations only in practice. | *** ## Known gaps Fields available in the Editor's persona form that have **no column in this sheet** (they must be set in the UI). **Import is non-destructive for these fields.** A field with no column is left untouched on reimport, so it's safe to create a persona in the Editor, set the UI-only fields there, and manage everything else by spreadsheet from then on. * **Is Organisation** — the flag that activates the Website channel. Can't be set from the sheet, but an existing organisation **stays** an organisation through a reimport; it won't be flipped back to an individual. * **Matches Player** * **Classification** (Open / Restricted / Confidential / Internal) * Identity detail: gender, age, job title, character pitch, nationality, ethnicity, accent * Cultural/narrative: affiliation, A3E, archetype, role, established * Location as text (only `GPS` is present) * Communication style: style, tone, register, delivery, writes in, uses emojis, avoids, examples * The COM-B expert attributes: capability, opportunity, motivation, mindset, standards, behaviour, memory ## Practical notes * **Handle is the join key.** Reimporting a sheet with an existing handle updates that persona rather than creating a duplicate. * **Blank overwrites - but only within the sheet.** A blank cell in a column that exists here is a value, not "leave alone", so populate defensively when editing a subset. Fields with no column are a different matter: they survive the reimport untouched. * **Two-pass creation for organisations.** Create them in the Editor with Is Organisation set, export, then bulk-edit. The flag persists. * **Per-channel identity is independent.** Setting `Handle` does not set `TwHandle`. * **Avatar fallback testing** needs `Image` *and* every `*ProfileImg` blank, or only one channel's fallback is exercised. * **Non-ASCII is fine** in names, tags and history — production files contain `Nānākuli` and curly apostrophes. Not true for Handles. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/personas/working-with-personas/batch-and-bulk-operations/persona-details-reference.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.