How to use OpinForge

Create a free account from the homepage, then sign in to open your workspace. Each account belongs to an organization — typically your team or company — so everyone on that team sees the same studies, surveys, and roll-up reports.

Two ways to get started: Create workspace (new team, you become owner) or Join with invite (use a link from a teammate — no separate org is created).

1. Create workspace: register with your real organization name, work email, and password (8+ characters).
2. Join with invite: open the /join/… link from your owner, or paste the token on Register → Join with invite.
3. Sign in from the header at any time.
4. Forgot password? Use the link on the sign-in page — we email a reset link that expires in one hour.
5. Return to this guide from the site header (How to) or the workspace sidebar (How to guide).

After sign-in you land on the overview. The left sidebar is your home base for day-to-day work.

• Overview — counts for studies and surveys; drag to set your personal list order (only you see it); shortcut to org-wide Insights.
• Surveys — open the builder, publish, and manage each questionnaire.
• Templates — start full surveys from pre-built question packs.
• Question Library — browse the platform standard catalog by category; manage questions your team saved for reuse.
• Responses — latest submissions across the org (with consent audit per row).
• Insights — cross-survey roll-ups, trends, and quality summary (/app/insights).
• Audience — recruitment links, tracked sources, and completes by channel (/app/audience).
• Import — upload contact CSVs and voter files into workspace lists (/app/import).
• Calling — call list templates, assignment to a teammate or hired caller, and an interviewer queue with click-to-call (/app/calling). This is a workspace add-on, not included with any plan until granted.
• Results — upload published Excel toplines and SPSS (.sav) microdata (/app/results).
• Shared Files — surveys another organization invited you to review (questionnaire access without full membership).
• Team — owners create invite links for full workspace members; teammates join via /join/… without creating a duplicate organization.
• Workspace switcher — if you have access to more than one organization (your team plus shared guest access), pick which workspace you are working in from the dropdown under the sidebar logo.
• The left sidebar stays visible while you scroll long pages so you can switch sections without scrolling back to the top.

1. Open Calling (/app/calling) and pick a template: Cold Calling Poll, From Address Book, or Import File.
2. Cold Calling Poll can create a phone survey from a cold-call module or a paid political QRE (Advanced Template Library). Address Book snapshots contacts that already have a phone number. Import File starts an empty list — upload a CSV or voter file next.
3. Grant the whole list to a teammate, or invite a hired caller by email or copy link (7 days). Hired callers get a limited login: Home and Calling only.
4. Prepare Interviews deploys the list to the attached survey so each row can Open Interview. Call uses the device dialer (tel:).

Platform Admin (/app/admin) is cross-organization: every client workspace, user, study, survey, response, template, trash recovery queue, master audit log, combined reports, and the respondent PII vault.

• Super-admin — full access, including permanent deletes (organizations, users, surveys, responses, templates) and PII vault maintenance (index / re-scan).
• Platform admin (read-only) — same browse, export, password resets, and survey restore from admin trash; cannot delete records or run destructive vault jobs.
• Grant roles under Platform Admin → Users → Edit (super-admins only can change roles).

Using the normal workspace as an operator:

• If your account also belongs to a team (organization membership), the sidebar shows Platform Admin plus the usual workspace links (Overview, Surveys, Reports, etc.).
• Inside Platform Admin, use the Workspace tab at the top to jump back to your team’s /app overview.
• Operators without a team membership only see Platform Admin until an owner adds them to a workspace (or a super-admin attaches them to one).
• After a role or membership change, sign out and sign back in so your session picks up the update.

• Trash (admin) — surveys that left a team’s trash appear here for a second recovery window before permanent purge; read-only admins can restore, super-admins can purge.
• Contact data (admin) — per-workspace view of email lists, invite batches, and per-survey invite counts; super-admins can purge lists or wipe invite data when clients need support (see Contact list import below).
• Reports (admin) — select one or more surveys for a combined cross-survey report and CSV export.
• PII vault — contact and census-style demographics (party, age, gender, ethnicity, education, income) mirrored from responses; searchable, charted, and CSV-exportable; super-admins only for bulk re-indexing.

A study groups related work: methodology text, consent settings, quotas, and pause/resume fielding. A survey is the questionnaire — pages, questions, theme, and logic.

• Create a study when several questionnaires share the same audience rules or disclosure.
• Add surveys from the study page or Surveys list.
• Study settings — edit methodology, disclosure, consent, and the quota grid (targets per segment). These fields control the respondent intro screen before questions (not the questionnaire pages).
• Skip the intro — clear methodology and disclosure and leave consent off; respondents go straight to the first question.
• Name surveys clearly; titles appear in Reports, Audience, and exports.

Open any survey to use the survey builder. All teams use the same Edit workspace: a block-based canvas, inline editing, and a sticky header with top tabs (Edit, Design, Distribute, Analytics, Settings). Changes auto-save as you work.

Terminology: a block (labeled G1, G2, …) is a group of questions on one respondent page. A question is one item in that block (multiple choice, rating, instruction text, or a pre-built panel such as Name). Each block is its own respondent step unless you merge blocks by removing an empty one.

Adding and removing blocks

• Add Block — on the last block only (footer or bottom toolbar). Creates a new empty block below and starts a new respondent page.
• Remove Block — on a block only when the block below it is still empty. Deletes that empty block and merges the pages back together.
• Blocks with questions — use the block menu (⋮) → Delete block if you need to remove a block that already has questions.
• Middle blocks — no Add/Remove footer controls; they only appear where the action applies.

Quick add questions

• Open Add Question → All Questions. The Quick add section is at the top of the drawer.
• Personal Information — first and last name, street address, city, state, ZIP, phone, and email in one panel.
• Address — street, apt, city, state, ZIP, and country.
• Name — first name, middle initial, and last name.
• Contact Information — first and last name, phone, and email.
• Individual fields — scroll to Personal Info, Contact, Address, or Work for single fields such as Street Address or Phone Number.
• Question labels — each item shows its type above the title (for example Street Address or Personal Information) while you build.

Top tabs

• Edit — build the questionnaire (Workspace sub-view by default).
• Design — theme presets, accent color, density, and survey-wide fonts & colors.
• Distribute — public link, QR, email/SMS compose (opens your mail or messages app), personal invite lists, and CSV contact list import.
• Analytics — live summary counts, response map, and links to Reports.
• Settings — report chart types per question, response quality checks, and respondent intro (study methodology/disclosure).
• Preview — open from the tools menu on Edit (desktop and phone layouts; optional validation/logic/page-break overlays).
• Publish — on the Edit tab header (next to Preview). Saves questionnaire, logic, and theme to the live public link. Fix blocking logic errors before publishing.

Edit sub-navigation

Under Edit, use the icon row below the main tabs:

• Workspace — block canvas, Add Block, Add Question, Choose template, Undo, Edit Footer, and Thank You Page.
• Design — same theme editor as the Design top tab.
• Finish Options — what happens after a successful complete (thank-you page, redirect URL, chain to another survey). Separate from End survey screen-out redirects on Edit → Logic.
• Logic — IF/THEN rules, nested And/Or groups, Test logic, and saved scenarios (including End survey screen-outs with optional redirect).
• Variables — invite-list fields, URL parameters, constants, and answer-copy tokens for logic.
• Settings — response quality policy (Security and Notifications are planned).
• Media Library, Languages, and Advance Quotas — coming soon (stub panels with roadmap links).

Workspace workflow

1. Survey names — Internal name is for your team lists; click the large survey title on the canvas to edit the respondent-facing title.
2. Add Block — creates a new question group (G1, G2, …) on the last block or from the bottom toolbar. Click the block badge to rename it.
3. Add Question — pick a type from the drawer (multiple choice, dropdown, matrix, rating, HTML instructions, image picker, and more). Use Quick add at the top of the drawer for Personal Information, Address, Name, and Contact Information blocks.
4. Edit in place — click question text, answer choices, scale labels, or block titles. A compact formatting bar appears (bold, italic, underline, font size, text color, link, image URL).
5. Per-question actions — Validation, Logic, and Settings on each question card; Bulk Edit for many choices at once.
6. Block menu (⋮) — reorder blocks, block flow & randomization, question randomization within a block, or delete the block.
7. Collapse blocks — click a collapsed block header to expand; useful on long questionnaires.
8. Choose template / Undo — in the sticky header on Workspace (Undo keeps the last 10 layout changes). Choose template opens the same searchable template library grid used on the Templates page.
9. Edit Footer — HTML footer on every respondent page except the thank-you screen.
10. Thank You Page — edit the successful-complete message from the bottom bar or Finish Options (not used for End survey screen-outs that set their own message).
11. Publish when ready (header Publish or Distribute). Drafts stay private until published. Live respondents go straight to Complete — there is no answer-preview page before submit.

Standard Question Library (Tier 2 Basic or higher when plan enforcement is on; full access for most teams today):

• 250+ ready-made questions — contact & demographics, political & civic batteries, HR, customer feedback, events, education, health, and reusable scales.
• Pre-built panels — name, address, contact, and work info with layout already set.
• Question Library page (/app/question-library) — preview any item before adding.
• In the builder — Add Question → Question Library; items append to the focused block.
• Your Organization tab — questions your team saved from the builder (single questions only, not whole panels).

• Templates — start blank or apply a template from Templates or Choose template on Workspace. The Advanced Template Library (political catalog first) can be previewed on any plan; using a library QRE is included with Enterprise or granted as an add-on. The paid political kit includes phone and Spanish twins, likely-voter models, rotating named ballots, quota presets, SPSS-ready names, a banner plan, Electoral Intel topic hints, and optional inserts (Hispanic origin, union, media, military, children).
• Answer choices — inline edit with formatting; Bulk Edit for long lists; Keep at end when randomizing pins options like Other or Undecided.
• Design tab — Design studio with Customize (themes, density, type) and Settings (layout modes, header logo, backgrounds, progress / previous).
• Logic — see Survey logic guide (/how-to/survey-logic): Edit → Logic for IF/THEN rules; per-question Logic on the card for skip paths; Edit → Variables for tokens; Test logic before publish.
• Distribute tab — public /s/… link, QR, mailto/SMS compose, personal invite lists, voter CSV import (map columns on Edit → Variables).
• Settings tab — report charts, response quality checks, respondent intro link to study metadata.

Before the questionnaire, respondents may see a separate intro screen with the survey title, study name, methodology, disclosure, and a Continue to survey button. That screen is not built in the questionnaire editor — it comes from the study linked to the survey.

1. Open the survey → Settings tab → Respondent intro screen → Edit study metadata (or open the study from Overview). Response quality checks are also under Settings, or Edit → Settings for a focused view.
2. Under Study metadata & respondent consent, edit Methodology and Disclosure with the copy you want respondents to read.
3. To remove the intro entirely: clear both text areas, leave Require consent unchecked, and save. Respondents then start on the first questionnaire page.
4. If consent is required, the intro screen always appears (with a checkbox), even when methodology and disclosure are empty.

• Study changes apply on the live public link without republishing the survey.
• New studies start with placeholder methodology/disclosure text — replace or clear it before fielding.
• Each response stores consent timing plus an audit snapshot when consent is used.
• Responses page — View audit on a row for the full consent record (timestamps, methodology, disclosure).

For platform-level transparency notes, see Methodology in the site header.

Team invites (/app/team) add full workspace members. For proofreader access without response data, use collaborator invites on Distribute → Email → Team access (enter an email to send automatically, or leave it blank to copy a link). Contact your workspace owner if you need reviewer access.

1. Open the survey → Distribute tab for the public link, QR code, email/SMS compose, invite lists, and Team access.
2. For collaborator review access: Distribute → Email → Team access, or ask your workspace owner — full members use Team → invite link.

• Cross-org reviewers use Shared Files or the workspace switcher.
• Guests cannot open Responses, Insights, Audience, or Team — only questionnaire work they were granted.
• Full members: use Team for org-wide access.

Publishing saves a snapshot of the questionnaire, logic, and theme. Respondents always receive that version until you publish again.

1. Finish building and use Preview from the Edit tools menu (desktop or phone). Preview is for your team — live respondents do not see an extra “review answers” step before submit.
2. Click Publish (or Publish changes) in the survey workspace when you have permission to publish.
3. Open the Distribute tab: copy the public respondent URL (/s/your-slug), download QR, or compose email/SMS (opens your mail or messages app with a tracked link).
4. Client-facing share and email template URLs stay as /s/your-slug (no version or release query parameters). Republishing does not change the slug — the same link always serves the latest publish.
5. The field dashboard shows the same public-link tools while you are fielding.

Open public link vs personal invites only

• Default — anyone with the open /s/… link can respond (while published and fielding is not paused).
• Require personal invite link — turn on under Distribute → Personal invite links (or Fielding settings). The open /s/… URL then shows “Personal invitation required”; only ?t=… tokens or short /r/… invite links accept responses.
• When invite-only is on, Compose and public-link panels warn you so you do not share the open URL by mistake. Use Lists to create and export personal links.
• Platform operators can open a verification URL with v and r parameters for admin checks; do not put those on client email or social posts.

Only distribute links to intended participants. Pause fielding from the field dashboard when you need to stop new completes without unpublishing.

Every published survey has a main BYO (bring-your-own) link. Add tracked sources when channels should have separate URLs — email vs. social vs. a partner list — so attribution is automatic.

1. Publish the survey first.
2. Open Audience in the sidebar and find your survey.
3. Use the main link (and QR on Distribute) for general distribution, or Email → Compose on Distribute (creates tracked Email/SMS sources automatically).
4. Click Add tracked source — name the channel and optionally set utm_source, utm_medium, utm_campaign, and panel_id.
5. If you republish after creating a tracked link, Audience warns when that source’s link was built for an older version — copy a fresh link or re-share via email/text.
6. Copy that source’s link only for that channel; do not mix channels on one URL if you want clean counts.

• Completes by source — chips on Audience summarize volume per tracked name.
• Personal invite list — on each survey card: search by name or API ID, filter status, export full CSV (all statuses), Export for email / ESP (active + email), or Export for texting company (active + phone). We do not send SMS from the app.
• Contact list import — open Import in the sidebar (or Distribute → Email → Lists → Open Import). Any CSV; auto-detects standard 44-column state voter files; up to 250,000 rows. Map list columns on Edit → Variables. See Contact list import for progress, resume, and reuse across surveys.
• Tracking is stored on each response (collector id and UTM fields).
• Remove a tracked source anytime; historical responses keep their attribution.
• Quotas and pause fielding are still managed under Study settings.

Where to import

1. Open Import from the sidebar, Address Book → Import contacts, or a survey’s Distribute → Email → Lists.
2. Choose Address Book (contacts only) or Survey invites (contacts + personal links). Survey mode requires a published survey.
3. Upload a CSV, map the unique ID and columns, then review rows (editable for files up to 2,000 rows).
4. Inactive registrations (STATUS = I) are excluded unless you check Include inactive registrations.
5. Choose New list or Existing list, then import.

Reusable workspace lists

• New imports create a workspace email list that any survey in the organization can use — you do not need to re-import the same CSV for every survey.
• Existing list — add or update contacts in a list you already started; duplicate IDs in the file are merged (last row wins for profile fields).
• Email lists table — Create links for this survey deploys personal invites from a saved list without uploading the CSV again.
• Compose (Distribute → Email) can target a saved list for mailto drafts.
• Delete list — soft-deletes the list from the workspace; platform admins can restore from Admin → Trash for five days.

Progress during import

After you select a file, the UI shows how many data rows were detected (for example ~65,000). During import you see a progress bar: contacts saved so far / ~total rows in the file, with a percentage.

• The total is based on rows in your CSV, counted when the file is read — not a separate server estimate.
• Progress may finish below 100% if voter-file filters skip rows (inactive registrations, missing email/phone) or if duplicate IDs in the file are collapsed.
• Large files (50,000+ rows) may take several minutes. Keep the browser tab open until the import completes or shows an error.
• The preview table shows the first few sample rows and all columns — scroll horizontally to verify the 44-column layout before importing.

If import fails or stops partway

1. A new list is created as soon as you start import, before all rows finish uploading — partial progress is kept in the database.
2. Refresh the page if needed; open Address Book → My lists (or Distribute → Email → Lists) and check the list’s contact count.
3. Choose Existing list on Import, select that list, and re-import the same CSV. Rows already saved are skipped or updated by ID; only missing contacts and new invite links are added.
4. If the error message includes a saved count, use that list name — do not start over with New list unless you intend a second copy.
5. Platform operators: Admin → Contact data → select the workspace to see list rows, batch counts, and per-survey invite totals; super-admins can wipe survey invites or purge a list when a client needs a clean reset.

Limits (current release)

• Up to 250,000 importable rows per file (rows above the cap are skipped).
• Imports run in the browser in small batches (100 rows per server request, up to three batches in parallel) to stay within hosting limits.
• Each chunk saves list members and creates personal invite links for the current survey.
• All organizations share one production database; data is isolated by workspace (organization_id), not separate databases per client.

Planned improvements

For many clients uploading large lists at the same time, a queued background import (one active import per workspace, email when complete) is documented for engineering in the repo under docs/engineering/CONTACT_LIST_IMPORT_SCALE_PHASE1.md. That is not live yet; until then, stagger very large imports when possible.

Logic and variables

Columns beyond the ID field are stored on each invite’s profile. Map them on Edit → Variables (source: Invite list / profile) and use them in Edit → Logic. See Survey logic guide → Contact list import and logic for step-by-step recipes.

• Audience (sidebar) — search personal invites, export short URLs, revoke or regenerate links.
• Fielding reference for the 44-column layout: docs/fielding/VOTER_FILE_FORMAT.md in the repository (engineering).

1. Open Results from the sidebar (/app/results).
2. Upload an Excel aggregate (.xlsx) — or attach a file to an existing study. Title, region, and field date are guessed from the filename when possible.
3. After parse, open the study to browse topline questions (searchable charts + CSV/PNG) and published crosstab sheets (full grid, CSV/PNG export).
4. Upload an SPSS (.sav) to the same study (or as a new study). Cases and variables power the microdata explorer and the crosstab builder (stub × up to two nested banners, weight/missing/filters, bases, significance letters, table CSV export).

Results are workspace-scoped: any member can upload. This is separate from live survey Responses — it is for published poll deliverables and historical microdata. Identifier fields such as email and IP stay stored but are omitted from CSV export.

While a survey is live, the field dashboard shows real-time progress and quota fill.

Split ballot (A/B): create separate surveys per arm in one study, publish each, then enable Split ballot under Study settings. Share only the entry survey’s public link — respondents are randomly assigned and tagged by ballot arm in Responses and CSV exports.

• Open Field from the survey workspace or study page.
• Live counts refresh automatically; use Refresh now for an immediate update.
• Quota grid — set targets on the study; the dashboard shows fills per cell.
• Pause study — temporarily block new public completes (fielding paused message).
• Public link, QR, email, and text share appear on the field dashboard — URLs stay /s/{slug} for client distribution.
• Personal invite links — same Require personal invite link setting as on Distribute; use Lists for /r/… links when invite-only is on.
• Screen-outs and completes — Responses and dashboards count terminated (screened out) separately from completes; optional screen-out redirect is configured on End survey rules (Edit → Logic), not Finish Options.
• For org-wide volume trends, use Insights; for question charts, use Reports.

Three layers help you move from raw submits to client-ready analysis.

• Responses — last 50 submissions org-wide; filter by survey; consent status and View audit per row.
• Reports (per survey) — distribution charts and tables for each reportable question; date and quality filters; methodology block for exports.
• Download CSV or SPSS (.sav) on Reports — same filters apply to both. SPSS uses numeric codes with value labels for single-choice questions, 0/1 columns per checkbox option, matrix rows, ratings, and outcomes (1=Complete, 2=Screened out, 3=Quota full). Open in SPSS or PSPP.

Report chart types (per question):

• Choose how each closed-ended question is visualized: table (default), vertical bar, horizontal bar, pie, or donut. Charts are optional — pick them per question on Reports or Settings.
• Open-ended text questions always show a response list (no chart picker).
• Matrix (Likert grid) questions — set the chart style once; each row in the report uses that style with its own table.
• Multi-select (checkbox) questions work best as horizontal or vertical bar charts; pie charts can be hard to read with many overlapping selections.

Where to set chart types (both update the same preferences):

1. Survey builder → Settings tab → Report charts — configure every question in one list; link opens the live Reports page. Analytics tab also links to Reports.
2. Survey Reports → dropdown on each question card — change while reviewing real data.

Chart choices apply immediately on the live Reports page — you do not need to republish the survey. Response counts and which questions appear still follow the published questionnaire when the survey is live; only the visualization style updates on the spot.

Use this for fielding health and executive summaries: total completes, daily trend, volume by survey, and flagged-response counts. Drill into Reports on a specific survey for question-level detail.

1. Open Insights in the sidebar (or Org insights on the overview).
2. Set optional date range and quality filter (all, flagged only, or clean only).
3. Review summary cards, completions-over-time chart, and responses-by-survey table.
4. Export summary CSV for the aggregates on screen.
5. Click Reports on a survey row for full charts and per-survey CSV.

Not the same as the public Insights page on the marketing site — that page is demo syndicated tracker data only. Your fielded surveys appear only in the signed-in workspace.

Open a survey → Settings tab (or Edit → Settings) → Response quality checks. Turn checks on or off and adjust thresholds (seconds, minimum matching answers, character counts). Click Save quality settings. Rules apply to new web submissions after you save; changing settings does not automatically re-score older responses (re-run on past data is planned).

Checks available today:

• Suspected straightlining — the same answer repeated on many questions (default: 3+ matching values).
• Completed very quickly — total time below your limit (default: under 5 seconds).
• Too fast per question — average time per question below your limit (off by default; useful on longer instruments).
• AI-like phrasing — common LLM phrases in text answers (heuristic, not a full AI classifier).
• Automated browser / bot — user-agent looks like a script, headless browser, or crawler.
• Very short open text — open-ended answers that are all extremely short (off by default).
• Duplicate long text answers — two or more long open answers with identical text.
• Very fast with long text — finished in under 30 seconds but left very long open-ended text (always on when fast-complete is enabled).

AI and bot detection are pattern-based (phrases and browser signatures). They catch obvious automation and copy-paste from chat tools but can miss subtle AI text or rarely flag formal human writing. A stronger optional LLM review of comment fields is on the product backlog.

Using flags in analysis:

• Responses — quality badges on recent submissions org-wide.
• Reports (per survey) — quality summary card, flag breakdown, and filter: all, flagged only, or exclude flagged from charts and CSV.
• Insights — org-wide flagged counts and the same quality filter on roll-ups.
• CSV export — quality summary and one column per flag type.

Coming soon: organization-wide default quality policy for new surveys, a control to re-run checks on existing responses after you change rules, and an optional LLM pass on open-ended comment fields.

Paper upload and AI-assisted extraction are planned but hidden in the current release so testers are not sent to half-finished flows. Web survey fielding, reports, and CSV export are fully supported today.

• Before fielding complex branching, walk through a live logic demo (/how-to/survey-logic#live-demos) or run Test logic under Edit → Logic.
• For panel / partner screen-outs, configure Screen-out redirect on the End survey rule — do not rely on Finish Options (those are for completes only).
• If the study is invite-only, turn on Require personal invite link before sharing; export /r/… links from Lists instead of the open /s/… URL.
• Share client-facing links as /s/your-slug only — skip admin verification query parameters.
• Finish and screen-out redirects both support `{variable_code}` tokens — define the variable under Edit → Variables (URL or invite source) so partner return URLs get the ID.
• On public links, answering the last single-choice question usually submits automatically; Complete remains for multi-select and open-ended last pages.
• Pilot with a small group; fix wording and logic before wide launch.
• Use the standard question library for contact blocks, Likert batteries, and industry-specific items.
• Use Bulk Edit on long choice lists; the floating format bar supports bold, size, and color on labels.
• Collapse blocks on long surveys to jump between sections quickly.
• Set fonts and colors on the Design tab before fielding.
• Edit Footer and Thank You Page for brand-consistent completion screens (successful completes).
• Keep one published version live during fielding unless you intentionally re-publish — the public slug stays the same.
• Use a separate tracked link per channel when source matters.
• Print QR codes from Distribute for in-person recruitment.
• Check Analytics and Insights during fielding; use Reports before stakeholder meetings.
• Set report chart types before decks — Settings → Report charts or on each question in Reports.
• Export CSV after major milestones; document quality exclusions in your analysis plan.
• Before fielding, clear placeholder methodology/disclosure on the study or replace with real copy (Settings → Respondent intro screen).

This guide covers self-service workflows. For full-service design, sampling, or analysis, use Contact us on the homepage.

Everyone: Survey Logic Guide with ten live demos (/how-to/survey-logic). Signed-in users: How-To Guide and Survey Logic Guide in the workspace sidebar · Contact list import (progress, resume, admin troubleshooting) · Shared Files · Question Library · Organization Insights · Audience · per-survey Reports · Edit → Logic and Edit → Variables · Distribute tab (public link, lists) · Methodology on the marketing site. Platform operators also use Platform Admin (Contact Data, Trash, PII Vault) and the Workspace tab there.