New to Mayetik? Start with the tutorial guide before using this reference. The tutorial covers all three roles with step-by-step exercises.
Mayetik is a structured knowledge capture system. Admins build sessions, invite participants, and collect answers. Participants complete sessions and receive AI-generated knowledge briefs summarizing their responses.
Mayetik uses a layered role system. Each layer is independent — a person can be an Org Admin and a participant in a specific project at the same time.
| Role | Scope | What they can do |
|---|---|---|
| System Admin | Whole platform | Create and manage organizations, projects, and users. Access all audit logs. |
| Org Owner | One organization | Everything an Org Admin can do, plus manage other org owners/admins. |
| Org Admin | One organization | View the org dashboard and member list, invite org members, create projects, view the org audit log. |
| Project Owner | One project | Everything a Project Admin can do. The "owner" role is assigned when the project is created. |
| Project Admin | One project | Build and publish sessions, manage questions, send invitations, manage project members, view responses and audit log. |
| Participant | One or more sessions | Complete assigned sessions and view their own knowledge briefs. Can also access Ask Mayetik if a Project Admin/Owner grants them Insights access. |
Dashboard redirect: When you sign in, Mayetik sends you directly to the right place:
/admin/projects/interviewsNavigate to /auth/signin.
Two sign-in methods are available:
Click Sign in with Google and complete the OAuth flow. You will be redirected to /dashboard on success.
Enter your email address and click Sign in with Email. A sign-in link will be sent to your inbox. Click the link to authenticate — no password required.
Self-serve sign-up: New accounts are created automatically on your first sign-in — no invitation required. You receive a 30-day trial with up to 100 session responses and full access to every feature. If you were invited to a specific project or organization, accept the invitation link before signing in so the membership is linked to your account.
Plans: After the trial, paid packages are available for Project Intelligence, Organizational Intelligence, and larger Enterprise Intelligence rollouts. Pricing is based on intelligence scope plus response volume; viewers/readers are included so teams can share knowledge without seat math. To upgrade, email hello@mayetik.com or visit /upgrade. A trial status banner at the top of every page shows how many days and responses remain on your current trial.
Language accessibility: A Translate button in the bottom-left corner of every page opens a language picker (Spanish, Portuguese, French, German, Italian, Punjabi) and displays the current page via Google Translate in a new tab.
System Admins access the admin area at /admin. Only users with the admin system role can reach these pages.
List page (/admin/organizations)
Shows all organizations in two tabs: Active and Archived. Each row shows the org name, description, and creation date. Actions available:
Create an organization (/admin/organizations/new)
Fill in:
owner role in the new orgOrg detail page (/admin/organizations/[orgId])
From here you can:
Owner or Admin roleList page (/admin/projects)
Shows all projects in Active and Archived tabs. Actions:
/projects/[projectId]Create a project (/admin/projects/new)
Fill in:
owner role in the new projectProject detail page (/admin/projects/[projectId])
Allows editing the project name and description, and changing the project owner. Changing the owner demotes the current owner to admin and promotes the selected user to owner (upserting their project membership if needed).
List page (/admin/users)
Shows all registered users with their system role. You can change any user's system role using the dropdown in each row. You cannot demote your own account — attempting to do so redirects to the users page with an error.
Available system roles:
user — standard role (no admin access)admin — full system admin accessAvailable at /admin/audit. Shows every auditable event across all organizations and projects, most recent first. See Section 8 — Audit Log Reference for full details.
Org Owners and Org Admins can access the org section at /orgs/[orgId]. System Admins also have access to all org routes.
The org dashboard (/orgs/[orgId]) shows:
Navigation buttons in the top right:
The members page (/orgs/[orgId]/members) shows the full list of org members with their name, email, role, and join date.
To invite a new member, fill in the Invite Member form at the top of the page:
Owner or AdminAn invitation email is sent with a link valid for 7 days. The invitee must accept the invitation to join the org. If they don't have a Mayetik account yet, they'll be prompted to sign in or create one via the invitation link.
Duplicate check: if a pending or accepted invitation already exists for that email, the form will show an error.
From the org dashboard, click New Project. You'll be taken to /orgs/[orgId]/projects/new.
Fill in:
You (the org member creating the project) are automatically assigned as the project owner.
The org audit log (/orgs/[orgId]/audit) shows all events scoped to this organization and its projects. This includes:
Use the filters at the top to narrow by action, target type, or date range. Results are paginated 20 per page.
See Section 8 — Audit Log Reference for the full list of action types.
The knowledge repository (/orgs/[orgId]/knowledge) gives org admins and owners a single searchable view of every completed knowledge brief across all projects in the organization.
Stats row — at the top of the page:
Search and filters:
Click Search to apply. Click Clear to reset all filters. Filter state is preserved in the URL so links can be shared.
Results table columns:
Results are paginated 25 per page. Pagination controls appear at the bottom when there are multiple pages.
Navigation buttons (top right):
Campaigns are the org-level scaling layer. Instead of creating a separate project and session for each department manually, you design one session and launch it across all departments at once. Mayetik creates a project and a session per department, clones your questions (including branch rules), and tracks completion across the campaign as a whole.
Access campaigns from /orgs/[orgId]/campaigns — the Campaigns button in the org dashboard header or the Campaigns nav link.
From the campaigns list, click New campaign. The creation wizard has three steps:
Step 1 — Details: Enter the campaign name, optional description, and optional deadline.
Step 2 — Base session: Select any published session in the org as the template. Its questions, hints, and branch rules will be cloned into each department's session.
Step 3 — Departments: Add one or more departments by name. You can optionally assign a group label to group related departments (e.g. "Leadership" vs. "Individual Contributors"). You can also define dependency edges — marks that one department's session should be completed before another's.
Click Launch to create the campaign. Mayetik creates a project and session per department in the background, then redirects to the campaign dashboard.
The campaign detail page (/orgs/[orgId]/campaigns/[campaignId]) shows:
Rather than inviting participants one by one per department, use Import participants on the campaign dashboard. Upload a CSV with three columns:
name,email,department
Alice Smith,alice@example.com,Engineering
Bob Jones,bob@example.com,Product
The department value must match the department name exactly (case-insensitive). Mayetik sends invitation emails to each address for the matching department's session. Duplicate invitations are skipped automatically.
Click Send reminders on the campaign dashboard to send a reminder email to all participants who have a pending invitation or an in-progress session older than 24 hours. Reminders are rate-limited to one per address per 24 hours.
Each department's session feeds into Mayetik's standard per-session synthesis (see Section 5.12 — Project Synthesis). Run a synthesis from the department row on the campaign dashboard or directly from the session responses page.
Once a department has a completed session synthesis, click Generate action plan in the department row. Mayetik generates a structured markdown document containing:
The action plan is stored against the department and can be downloaded as a Markdown file. If a campaign synthesis has also been run, the action plan incorporates cross-department context automatically.
A Download all plans button on the campaign dashboard exports every department's action plan as a single combined Markdown file.
Once at least one department has a completed session synthesis, click Run campaign synthesis on the campaign dashboard. The synthesis reads all completed department syntheses and produces a cross-department report covering:
Multiple syntheses can be run over time. The latest completed synthesis is shown by default; previous runs are listed in the history section.
A campaign synthesis can also be scoped to a group (e.g. "Leadership" only) by selecting the group from the synthesis trigger button.
When creating a campaign, select one of eight types. The type determines what the campaign is designed to learn:
| Type | Use when |
|---|---|
| Retrospective | Looking back at a completed quarter, sprint, or project — what happened, what was learned |
| Futurespective | Looking forward — what the team is committing to and what could cause those commitments to slip |
| After-Action Review (AAR) | Debriefing a specific completed initiative or launch: what was planned vs. what happened, why gaps occurred, and what to preserve |
| Pre-mortem | Before a major initiative begins: imagining failure, surfacing weakest assumptions, and naming early warning signals |
| Lessons Learned | Capturing transferable knowledge at the end of a long-running project: what to repeat, what to change, what advice to pass forward |
| Health Check | Assessing morale, clarity, friction, and capacity across teams — useful at end of quarter or after a stressful period |
| Alignment Check | Testing whether teams share the same understanding of strategic priorities — and where interpretations diverge |
| Win/Loss | Analyzing a completed sales evaluation or competitive situation: what was decisive, where were we strong, what gaps cost us |
Retrospective and futurespective campaigns can be paired together into a cycle, enabling cycle comparisons — see below.
On the campaigns list, active and closed campaigns show a New cycle button. This opens the clone wizard, where you:
The cloned campaign starts as a Draft and is activated when you complete the wizard.
A cycle comparison is available on retrospective campaigns that have:
Click Compare cycles to generate a comparison report. The report surfaces:
Like campaign synthesis, cycle comparisons can be scoped to a department group.
Click Close campaign on the campaign dashboard. Closed campaigns are read-only — no new participant imports or synthesis runs are possible. Campaigns can be cloned whether active or closed.
The Organizational Intelligence Dashboard (/orgs/[orgId]/intelligence) gives org admins and owners a live snapshot of knowledge capture activity across the entire organization — without navigating into individual projects.
Access: Click Intelligence in the org dashboard header, or navigate directly to /orgs/[orgId]/intelligence.
Headline stats
Four stat cards appear at the top of the page:
| Stat | What it counts |
|---|---|
| Total briefs | All-time completed knowledge briefs across all org projects |
| Briefs | Completed briefs in the last 30 days |
| Sessions completed | Completed sessions in the last 30 days |
| Contributors | Distinct participants with at least one completed session in the last 30 days |
Brief volume chart
A 12-week bar chart shows brief generation activity over time. Each bar represents one calendar week. Hover over a bar to see the exact count. Missing weeks (no briefs generated) render with no bar height.
Theme Pulse ✦
Click Generate in the Theme Pulse panel to run an AI analysis of the 15 most recent completed briefs across the organization. The AI extracts 5–8 recurring themes — topics, concerns, or insights that appear in multiple briefs. Each theme card shows:
An overall observation above the cards captures the most striking meta-pattern. Once generated, click Re-run to refresh the analysis as new briefs accumulate.
Note: Theme Pulse requires at least 2 completed briefs. The button is disabled until this threshold is met.
Most active projects and contributors
Two side-by-side tables show the top 5 most active projects (by brief count, last 30 days) and the top 5 contributors (by completed sessions, last 30 days). Project names link directly to the project dashboard.
Recent knowledge
The bottom of the page shows the 6 most recently generated knowledge briefs across the org as linked cards — displaying the project name, session title, respondent, and date. Click any card to open the session detail in the responses dashboard.
Org Ask Mayetik (/orgs/[orgId]/ask) lets org admins and owners ask natural-language questions across the entire organisation's indexed knowledge base and receive AI-synthesised answers with citations.
Access: Click Ask ✦ in the org dashboard header, the Knowledge Repository header, or navigate directly to /orgs/[orgId]/ask.
Knowledge base status
A status panel at the top shows the total number of indexed briefs and the number of projects they span. Indexing happens automatically when a knowledge brief is completed — no admin action required. For reliable answers, at least 3 indexed briefs are recommended.
Completed intake form records are also indexed alongside session briefs. They appear as sources with a blue badge and the form title as the source label; there is no "View session →" link for intake sources (records are not individual session pages).
pgvector note: Indexing is only available in the Railway production environment. In local development the page loads but queries return a "no briefs indexed" message.
Submitting a query
Six suggested prompts are shown when the query box is empty — covering themes, risks, lessons, contradictions, opportunities, and leadership-relevant patterns.
Reading the answer
The answer appears as prose below the form. Each claim references one or more source briefs by number ("Brief 1", "Brief 2", etc.). A Sources section below the answer lists each cited brief with:
Project scope filter
When a project is selected from the Scope selector, a pill appears below the form confirming the active filter. Click Search all projects × to clear the filter and search the full org again.
Org Synthesis (/orgs/[orgId]/knowledge/synthesis) generates an AI analysis that synthesizes findings across all projects in the organization — using completed project syntheses as its input.
Access: Click Synthesize ✦ in the Knowledge Repository header, or navigate directly to /orgs/[orgId]/knowledge/synthesis.
Requirements
At least 2 completed project syntheses must exist across the org's projects. An amber warning appears if fewer are available.
Source projects
The page lists all projects that have at least one completed synthesis, showing the synthesis title and date for each. These are the sources the AI will draw from.
Selecting a focus
Choose one of 6 focus types before generating:
| Focus | What it emphasises |
|---|---|
| Top Themes | The most prominent patterns across all projects |
| Client Pain Points | Problems, unmet needs, friction, and root causes |
| Operational Risks | Constraints, dependencies, blockers, and failure modes |
| Lessons Learned | Transferable knowledge for future work |
| Divergent Views | Where groups disagree, prioritize differently, or see different realities |
| Market Signals | External trends, buying signals, competitive pressure, or demand shifts |
Generating a synthesis
Click Generate org synthesis. A confirmation dialog shows the selected focus and the source projects that will be included. Click Generate to confirm.
The synthesis runs in the background (typically 30–60 seconds). The page polls automatically and displays the result when ready.
Reading and using the output
Completed org syntheses show the generated analysis first, followed by supporting controls:
Generate tailored next actions
Click Generate tailored next actions ✦ to produce on-page synthesis-specific suggestions without downloading the brief pack. Returns AI-tailored Ask Mayetik prompts (as clickable pills) and follow-up session cards (with title, audience, rationale, and Run in Studio → links). Falls back to curated defaults if AI is unavailable.
Synthesis history
All past org synthesis runs are preserved. The history list at the bottom of the page shows each run's focus, status, and timestamp. Click View on any completed entry to read that version.
The Settings page (/orgs/[orgId]/settings) lets Org Owners and Org Admins connect third-party workflow tools. Access it via the Settings nav link on the org dashboard.
Connect a Slack incoming webhook to receive real-time notifications in a Slack channel of your choice.
To connect:
https://hooks.slack.com/).Once connected, click Test connection to send a test ping. Use Update credentials to change the webhook URL. Click Disconnect to remove the integration (existing data is not affected).
Connect your Atlassian Jira instance to push synthesis action plans directly to Jira as stories.
To connect:
id.atlassian.com → Security → API tokens.https://yourorg.atlassian.netENG)Once connected, click Test connection to verify the credentials and project key. Use Update credentials to change any field. Click Disconnect to remove the integration (existing Jira issue links remain visible in the UI).
Creating Jira issues from synthesis:
Once Jira is configured, a → Jira button appears on any completed project or org synthesis next to the Download DOCX button. Clicking it opens a confirmation dialog and then creates a Jira story with:
mayetikAfter creation, the button is replaced with the Jira issue key as a link (e.g. ENG-42 ↗). Creating the same synthesis's issue again returns the existing key — creation is idempotent.
Publish completed syntheses to an Atlassian Confluence space as a formatted page.
To connect:
id.atlassian.com → Security → API tokens (the same credentials work for Jira if you connect both).https://yourorg.atlassian.netTEAM, ENG)Click Test connection to verify the space is reachable. Click Disconnect to remove the integration (pages already published are not deleted).
Once connected, a Push to Confluence button appears on any completed project or org synthesis. Confirming creates a page in the configured space with the synthesis content converted from Markdown to Confluence's storage format. Re-pushing the same synthesis creates a new page rather than updating the existing one.
Upload completed synthesis content as a Markdown file into a Microsoft 365 document library.
To connect:
https://yourorg.sharepoint.com/sites/KnowledgeClick Test connection to confirm the site is reachable. Once connected, a → SharePoint button appears on completed syntheses; confirming uploads a Markdown file to the configured folder.
Upload completed synthesis content as a Markdown file into a shared Google Drive folder.
To connect:
Click Test connection to confirm the folder is accessible. Once connected, a → Google Drive button appears on completed syntheses; confirming uploads a Markdown file to the configured folder.
Create a structured Notion page from a completed synthesis.
To connect:
notion.so/profile/integrations and copy the token.Click Test connection to confirm the page is reachable. Once connected, a Create Notion page button appears on completed syntheses; confirming creates a new page as a child of the configured parent page, with the synthesis content converted to Notion blocks.
Attach a completed knowledge brief to a Salesforce record as a Note, so buyer or account context stays with the opportunity.
To connect:
https://yourorg.my.salesforce.comClick Test connection to verify. Once connected, a Link to Salesforce link appears on any completed brief (session responses page). Choose an object type (Opportunity, Account, or Contact), search by name, select a record, and click Link brief — a Note is created on that record containing the brief content and a link back to Mayetik. The brief detail then shows a "[Record name] in Salesforce →" link.
Attach a completed knowledge brief to a HubSpot deal, contact, or company as a Note.
To connect:
crm.objects.deals.read, crm.objects.contacts.read, crm.objects.companies.read, crm.objects.notes.write.Click Test connection to verify (this also confirms your HubSpot portal ID). Once connected, a Link to HubSpot link appears on any completed brief — search by object type, select a record, and link the brief the same way as Salesforce above.
Attach a completed knowledge brief to a Dynamics 365 account, contact, or opportunity as a Note.
To connect:
https://yourorg.crm.dynamics.comClick Test connection to verify. Once connected, a Link to Dynamics 365 link appears on any completed brief, with the same search-and-link flow as Salesforce and HubSpot.
Rather than a dedicated app for each automation tool, Mayetik sends a generic, signed outbound webhook that Zapier (Catch Hook trigger), Make (Webhooks module), n8n, or any other tool that accepts inbound webhooks can consume.
To connect:
X-Mayetik-Signature header so your automation can verify the payload; leave blank to auto-generate one.Click Send test event to fire a webhook.test payload immediately. The Settings page shows whether the connection is Active or Paused, and the delivery status of the most recent event. Click Remove to stop sending events.
The Knowledge Entities page (/orgs/[orgId]/knowledge/entities) surfaces structured entities automatically extracted from every completed knowledge brief across the organization. Access it via the Entities button in the Knowledge Repository header.
What gets extracted
Every brief is analyzed by AI after generation. Four entity types are extracted:
| Type | What it captures |
|---|---|
| People | Named individuals referenced in the brief — not generic titles like "the manager", only actual names |
| Decisions | Explicit choices, conclusions, or agreed outcomes recorded in the session |
| Risks | Specific blockers, concerns, or uncertainties named in the brief |
| Commitments | Stated future intentions with a named actor — e.g. "Sarah to deliver the roadmap by Q3" |
Extraction runs in the background after brief generation. Each entity carries a confidence score; only items at 0.5 or above are stored. Up to 20 entities are extracted per brief.
Browsing entities
The entity list groups entries by (type, label) across all briefs. Columns:
Filters:
Each expanded row shows the exact excerpt from the brief that evidences the entity, with a "View brief →" link.
Commitment Tracker
When the all-types or Commitments view is active, a Commitments with no follow-up panel appears below the entity table. It lists commitments captured in a brief that have not been referenced in any other brief for the same organization within 90 days. These are commitments with no observable follow-through — useful for identifying items that may have been dropped.
Each entry shows:
Entity badges in Ask Mayetik
When a query returns sourced answers in Ask Mayetik (org level), each source card shows up to three entity badges for the decisions, risks, and commitments extracted from that brief. Badges provide structural context about each source without opening the brief.
Entities tracked stat
The Organizational Intelligence dashboard includes an Entities tracked stat card showing the total count of knowledge entities extracted from all org briefs all time. Clicking it navigates to the Entities page.
The Analysis Workbench (/orgs/[orgId]/knowledge/analysis) generates source-backed themes from all completed knowledge briefs in the organization. Access it via Knowledge Repository → Analysis in the org navigation.
Running an analysis:
Click Generate themes. The AI reads up to 20 recent briefs across all projects (or a filtered subset) and returns 5–8 named themes. Each theme includes:
Analyst controls (per theme):
| Control | What it does |
|---|---|
| Pin | Moves the theme to the top of the list and marks it as a priority finding |
| Dismiss | Hides the theme from the current view (not permanently deleted) |
| Rename | Replaces the AI-generated name with your own label |
| Add note | Attaches a private annotation — context, caveats, or next steps |
Copy evidence pack: Copies the theme name, summary, and all evidence excerpts as formatted Markdown, ready to paste into a report or message.
Jump to Ask Mayetik: Each theme card includes an "Ask Mayetik →" link that prefills a query with the theme name so you can explore deeper evidence from the full indexed archive.
Run history: The last 5 runs are saved with timestamp and brief count. Click any historical run to review its results.
Minimum: at least 3 completed briefs are required before the Generate button is available.
The Governance & Data Portability Center (/orgs/[orgId]/governance) gives Org Owners and Admins one place to show that Mayetik intelligence is governed, inspectable, and portable — useful for procurement reviews, security questionnaires, or simply confirming nothing is trapped in a silo. Access it via Governance Center on the org dashboard (Govern section).
Readiness grid
Four checks, each shown as done or not-done with a supporting detail:
| Check | What it confirms |
|---|---|
| Access | The organization has at least one member |
| Portable data | At least one exportable record exists (completed briefs, project/org syntheses, or intake records) |
| Auditability | The org audit log is available to admins (always true) |
| Destinations | At least one integration (see §4.10) is connected |
Portable inventory
A list of every route for exporting or reviewing organizational intelligence, each linking directly to the relevant page:
/orgs/[orgId]/knowledge)/orgs/[orgId]/knowledge/synthesis)Controls
Shortcuts to review members, inspect the audit trail, review connected integrations, and configure settings — all from one page.
Download manifest
Click Download manifest to generate a Markdown portability manifest for the organization, built from live counts at the moment of download (not a cached snapshot). Requires Org Owner or Admin.
The Outcome Dashboard (/orgs/[orgId]/outcomes) tracks whether captured conversations are turning into structured evidence, syntheses, action plans, and operational workflows — a single view of what organizational intelligence actually turned into. Access it via Outcome Dashboard on the org dashboard.
Outcome loop
A 5-stage pipeline, each marked complete once its underlying data exists:
| Stage | Complete when |
|---|---|
| Capture | At least one completed brief exists |
| Structure | At least one decision, risk, or commitment has been extracted (§4.11) |
| Synthesize | At least one project or org synthesis is completed |
| Act | At least one action artifact exists (interview action plan, campaign action plan, or linked Jira issue) |
| Operationalize | At least one integration (§4.10) is connected |
An overall percentage reflects how many of the 5 stages are complete.
Metrics and shortcuts
Stat cards for decisions, risks, commitments, and action artifacts, plus a shortcut list linking to Evidence, Syntheses, Action plans, Integrated work (Jira issue count), and Structured entities.
Project-level breakdown
A table of up to 6 projects showing completed briefs, project syntheses, entities, and action plans per project — sorted by synthesis count.
Pilot Success Report
Click Pilot Success Report to open /orgs/[orgId]/outcomes/report — a sponsor-facing summary built from the same live data as the dashboard: an executive summary, the outcome loop as a checklist, evidence captured (briefs, decisions, risks, commitments), action signals (syntheses, action plans, integrated work items, connected integrations), a project-level breakdown, and recommended next steps tailored to how far along the pilot is.
Click Download Markdown or Download DOCX on the report page for a one-click file (pilot-success-report-[org]-[date].md or .docx) suitable for sharing with a sponsor or stakeholder outside Mayetik. Both formats are generated from the same live data at the moment of download.
Project Owners and Project Admins access the project section at /projects/[projectId]. System Admins also have full access to all project routes.
The project dashboard (/projects/[projectId]) shows:
Session list (/projects/[projectId]/interviews)
Shows all sessions for the project with their status badge. Click View to open a session's detail page. Click New Session to create one, or use Import from JSON to create a session from a file (see below).
Session statuses:
| Status | Meaning |
|---|---|
draft | Being built. Participants cannot see or start it. |
published | Live. Participants can start and complete the session. |
closed | No longer accepting new responses. Existing responses can still be viewed. |
Status transitions (on the session detail page):
draft → published — requires at least one active questionpublished → closedclosed → published — reopens the sessionSession detail page (/projects/[projectId]/interviews/[interviewId])
Sections on this page:
Stakeholder group: an optional label (e.g. Engineering, Product, Customers) that identifies which group of stakeholders this session targets. The stakeholder group is used by Project Synthesis to organize findings by group and surface convergent/divergent themes across groups.
Language: sets the language used throughout the participant's experience for this session. When a language other than English is selected, the following are localized to that language: the participant session UI (buttons, validation messages, headings), the read-aloud TTS voice, the AI-generated knowledge brief, and the invitation email sent to participants. Currently supported: English (en) and Spanish (es). The language can be changed at any time on the Details tab; existing responses and briefs are unaffected until regenerated.
Importing a session from JSON
Below the New Session form on the session list page is an Import from JSON section. Upload a .json file and click Import to create a complete session — title, description, questions, and branch rules — in one step. The session is always created as a draft; publish it manually when ready.
Two file formats are accepted:
/help/guide#import or expand the Format reference panel inline on the import page.pages array. Question types are mapped to Mayetik equivalents (text/comment → text, radiogroup/dropdown → multiple_choice, checkbox → multi_select, rating → rating_scale, boolean → yes_no). Unsupported types are skipped with a warning. visibleIf expressions are not converted — add branch rules manually after import.Three ready-made templates are available via the Download template button and the links in the Format reference panel:
| Template | Description |
|---|---|
session-template.json | Full 15-question annotated example covering all 16 question types |
simple-survey.json | Minimal 3-question survey — good starting point |
branching-survey.json | Example with multiple branch rules and condition types |
If validation fails, a specific error is shown inline — no session is created. Common causes: duplicate title within the project, missing order: 1, targetOrder referencing a non-existent question, or missing options for types that require them (multiple_choice, rating_scale, slider, multi_select, ranking).
Browsing and cloning community templates
Below the Import from JSON section on the session list page is a Browse Templates section. Click to expand it and browse two tabs:
Each template card shows the title, description (if any), estimated completion time, and category. Click Use this to clone the template into the current project as a new draft session, pre-populated with all the template's questions, types, hints, and options. You can then edit, extend, and publish it like any other session.
To submit one of your own sessions as a community template, open the session detail page → Details tab → Submit as template (available on published sessions only). System admins review and approve or reject submissions. Approved templates appear immediately in the Community tab.
Session Studio is an AI-assisted design tool for draft sessions. It generates a full session structure — questions, types, hints, and branching logic — from a plain-language description of your research goal. You can then refine the design through follow-up chat before applying it to the session.
How to access
Open any session that is in draft status and click the Studio ✦ tab. (The tab is hidden once a session is published or closed.)
Generating a design
Example prompt: "I want to understand why engineers are leaving. Participants are senior engineers who recently resigned. I want to learn about compensation, management, and career growth — keep it under 10 minutes."
Refining the design
Type a follow-up message to make changes:
Each response updates the full design in the right panel. The chat history is included in every request so Session Studio maintains context across turns.
Applying the design
Once you are satisfied with the design, click Apply to session. This:
If the session already has questions, a confirmation dialog shows how many will be replaced before proceeding.
After applying, you are redirected to the Questions tab with a "Changes saved" banner. From there you can make manual adjustments, add more questions, or publish the session immediately.
Supported question types
Session Studio supports 8 types: text, short_text, multiple_choice, multi_select, yes_no, rating_scale, slider, and number. You can edit questions manually to use any of the 16 full question types after applying.
Tips for better results
Before publishing, run an AI-powered readiness review on any session to get a scored quality assessment across 8 design criteria.
How to access
Open any session and click the Readiness tab (available on draft, published, and closed sessions).
Running a review
Click Run readiness review. Mayetik sends the session's questions, branch rules, and metadata to the AI and returns a report in a few seconds. Click Re-run review at any time to get a fresh assessment — each run generates a new report.
What the report shows
| Section | What it assesses |
|---|---|
| Overall score | A 0–100 score with a status badge: Ready (≥ 80), Needs edits (50–79), High risk (< 50) |
| 8 section scores | Detailed findings for each criterion (see below) |
| Issues | A prioritized list of problems (High / Medium / Low), each with a description and suggested fix |
| Suggested questions | New questions the AI recommends adding, with a copy-to-clipboard button |
The 8 criteria:
| Criterion | What it checks |
|---|---|
| Audience Fit | Does the session match its intended audience? |
| Goal Coverage | Does it capture pain, urgency, current process, alternatives, and blockers? |
| Branch Logic | Are conditional follow-ups correct for both answer paths? |
| Low-Fit Detection | Can the session distinguish target respondents from adjacent ones? |
| Summary Readiness | Will answers produce enough material for a useful AI brief? |
| Admin Usefulness | Will responses support segmentation, synthesis, and follow-up? |
| Tone & Privacy | Is the language appropriate for the audience's sensitivity? |
| Length & Friction | Is the session appropriately sized? Are there likely abandon points? |
Notes:
Adding a question
In the Questions section of the session detail page, fill in the question form:
Click Add Question to save.
Question types
| Type | What participants see | Admin options |
|---|---|---|
Text | Multi-line text box | — |
Short Text | Single-line text input | Pattern preset, max length, placeholder |
Multiple Choice | Radio buttons for one selection | List of options (Add / Remove) |
Yes / No | Two-option toggle (Yes / No) | — |
Multi-Select | Checkboxes for multiple selections | List of options |
Rating Scale | Number scale selector | Min value, max value, step |
Number | Numeric input field | — |
Slider | Drag slider | Min value, max value, step |
Date | Date picker | — |
Time | Time picker | — |
Email | Email-validated text input | — |
Address | Five-field US postal address form | Show/require Street 2, require City/State/ZIP, USPS verification |
Signature | Typed name with handwriting font | — |
File Upload | File chooser | — |
Location | Location input | — |
Ranking | Drag-to-rank list | List of items |
Short Text options
When creating or editing a Short Text question:
Address options
When creating or editing an Address question:
verified: false). When USPS credentials are not configured, verification is silently skipped.Signature options
The Signature type captures a typed electronic signature with a timestamp. No additional options are required. Participants:
The submitted answer stores the name, the internal font key, and an ISO 8601 timestamp captured at the moment the participant clicked Next. Signatures have the same legal standing as typed names; they do not produce a cryptographic signature.
Editing a question
Click the Edit button next to any question. The form pre-fills with the existing values. Click Save Changes to update.
Reordering questions
Use the ↑ and ↓ buttons beside each question to move it up or down in the sequence.
Deleting a question
Click Delete beside a question. This is a soft delete — the question is hidden from participants but its existing answers are preserved in the database.
The invitations page (/projects/[projectId]/invitations) has two invitation forms and a sent invitations log.
Use the Invite Project Member form:
Owner or AdminThe invitee receives an email. When they accept, they are added to the project with the specified role. If they already have a lower role (e.g. participant), the upsert will promote them to the invited role.
Use the Invite Participant form:
The invitee receives an email with a link to the specific session. When they accept, they receive:
ProjectMembership (participant role) for the projectParticipants can only be added via session invitations. The project member form only creates owner/admin roles.
The Sent Invitations table shows all invitations (session-type and project-type) with their status.
The members page (/projects/[projectId]/members) lists all people who have a project membership, with their role and join date.
Changing a member's role
Only non-owner, non-self rows have the role change control. To change a role:
Admin or Participant)The project owner's role cannot be changed from this page. To transfer project ownership, a System Admin can use /admin/projects/[projectId].
Removing a member
Click Remove on any non-owner, non-self row. A confirmation dialog warns that the action is permanent and cannot be undone. Click Remove member to confirm.
Note: Removing a member does not revoke their pending invitations. Revoke any open invitations on the Invitations page separately if needed.
Mayetik has two response views: a cross-session overview for the whole project, and a per-session detail page.
/projects/[projectId]/responses)Shows every response across all sessions in the project. Four summary stats are shown at the top: total completed, in-progress, active sessions, and last activity date.
Filters: narrow by session, status (completed / in progress), respondent name/email, and date range.
Columns: Session (links to the response detail and to "all responses" for that session), Respondent, Status (with inline brief status), Answers, Date/duration, and a test-session toggle button. Use the Columns button (gear icon) to show, hide, and reorder columns — preferences are saved per browser.
Test sessions: sessions marked as test are shown at reduced opacity. Toggle "Show test sessions" to include or hide them.
/projects/[projectId]/interviews/[interviewId]/responses)Shows all responses for a single session.
Summary stats: total, completed, completion rate, and last response date.
Tag filter: filter sessions by their signal label (High signal, Low fit, Needs follow-up, etc.) to quickly focus on a subset.
Sessions table: lists every participant session. Use the Columns button to customise which columns are visible and their order (Respondent, Email, Status, Label, Answers, Duration, Date). Click Open → on any row to open the full session detail on a separate page.
Tagging sessions
Each session can be manually tagged with a signal label from the session detail page. Tags help you triage responses before running analysis — filter to "High signal" sessions, then trigger synthesis on that subset.
| Tag | When to use |
|---|---|
| High signal | Strong match: the participant fits the target audience and their answers are detailed and specific |
| Low fit | The participant doesn't match the target audience |
| Audience mismatch | The participant came from the wrong channel or cohort |
| Test/mock | Internal test session — exclude from synthesis and analytics |
| Strong objection | The participant expressed a significant challenge or resistance |
| Strong buying signal | The participant showed clear interest or intent |
| Needs follow-up | The answers warrant a follow-up conversation with this participant |
CSV export: when at least one session is completed, an Export CSV button appears in the page header. The download includes one row per session with columns for respondent, email, date, duration, and every question.
Marking test sessions: each row has a Mark as test / Unmark test action that toggles the session's test flag without deleting it. Test sessions are excluded from analytics and synthesis by default.
Below the sessions table, three collapsible AI analysis cards appear once enough sessions exist. Each card can be expanded or collapsed independently; the state persists across page reloads.
| Card | Minimum requirement | What it produces |
|---|---|---|
| Thematic Analysis | 2 completed sessions | A numbered list of common themes drawn from all session briefs |
| Session Synthesis | 2 completed sessions | Structured prose synthesis: overview, key findings, patterns, outliers, recommendations |
| Action Plan | 1 completed thematic analysis | 5–7 prioritised actions with Why / What to do per action |
Click Analyse (or Generate) to trigger a card. Click Retry if a previous run failed. Each card shows when it was last generated and the number of sessions it was based on.
When at least one brief is indexed for the session, an Ask Mayetik card appears above the analysis panel. It works identically to the project-level Ask Mayetik, but queries are scoped to this session's briefs only.
Click Suggest questions → to generate AI-suggested starting points specific to this session's content. Clicking a suggestion pill immediately submits it — no extra click needed. Source citation links in the answer navigate directly to the relevant response detail.
/projects/[projectId]/interviews/[interviewId]/responses/[sessionId])Click Open → on any session row to view its full detail:
Admin completion notifications
When a participant completes a session, every Project Owner and Project Admin for that project receives an email notification containing:
No configuration is required — notifications fire automatically for all completed sessions. They cannot currently be toggled per user.
Participant brief-ready email
After a participant completes a session and their knowledge brief is generated, they receive a separate email ("Your knowledge brief is ready") with a link to view it. This email is sent only to authenticated (logged-in) participants — anonymous public questionnaire respondents do not receive a brief email. Brief generation typically completes within 30 seconds of session completion.
The project audit log (/projects/[projectId]/audit) shows all events scoped to this project — sessions, questions, members, invitations, and briefs. System Admins and Project Owners/Admins can access it.
Filterable by action, target type, and date range. Paginated 20 per page.
Adaptive questioning allows a session to take different paths depending on a participant's answers. It is configured via branch rules on individual questions.
Branch rules
A branch rule specifies that when a participant answers a given question and their answer satisfies a condition, they are routed to a target question instead of proceeding to the next question in the default sequence. Rules are evaluated in priority order (ascending integer — lower number runs first). If no rule matches, the participant advances to the next question in the default sequence.
Each branch rule has the following fields:
| Field | Description |
|---|---|
| Source question | The question this rule is attached to |
| Condition type | The comparison to apply (see supported values below) |
| Condition value | The value to compare the participant's answer against |
| Target question | The question to route to when the condition is true |
| Priority | Integer determining evaluation order; lower runs first |
Supported condition types (ConditionType enum):
| Value | Meaning |
|---|---|
equals | Answer exactly matches the condition value |
not_equals | Answer does not match the condition value |
less_than | Answer is numerically less than the condition value |
less_than_or_equal | Answer is numerically less than or equal to the condition value |
greater_than | Answer is numerically greater than the condition value |
greater_than_or_equal | Answer is numerically greater than or equal to the condition value |
contains | Answer text contains the condition value as a substring |
not_empty | Answer is present and non-blank |
is_empty | Answer is absent or blank |
Terminal questions (isTerminal field on Question)
When a question has isTerminal = true, the session ends immediately after the participant answers it — regardless of how many questions remain in the default sequence. This is useful for early-exit paths, such as a screening question that determines the remainder of the session is not applicable.
The isTerminal flag is set in the question editor using the "Mark as terminal question" checkbox.
The Project Synthesis page (/projects/[projectId]/synthesis) generates a cross-session analysis that brings together findings from all stakeholder groups into a single strategic document.
Triggering a synthesis
Click Generate new synthesis. A confirmation dialog opens. Before confirming, select a Focus type:
| Focus | What it emphasises |
|---|---|
| Top Themes | The most prominent patterns across all sessions |
| Client Pain Points | Problems, unmet needs, friction, and root causes |
| Operational Risks | Constraints, dependencies, blockers, and failure modes |
| Lessons Learned | Transferable knowledge for future work |
| Divergent Views | Where groups disagree, prioritize differently, or see different realities |
| Market Signals | External trends, buying signals, competitive pressure, or demand shifts |
The button is enabled only when at least 2 completed session syntheses exist for the project. If fewer exist, a readiness panel replaces the button — showing a progress bar ("N of 2 syntheses ready"), a per-session checklist with the synthesis status for each session in the project, and a direct Run synthesis → link for any session that doesn't yet have one. Once the threshold is met the Generate button becomes active.
Once triggered, the page shows a "Generating…" state. The AI runs in the background. Refresh the page (or wait for the automatic poller) to see the result.
Reading and using the output
Completed project syntheses show the generated analysis first, followed by supporting controls:
Generate tailored next actions
Click Generate tailored next actions ✦ to produce on-page context-specific suggestions without downloading the brief pack. This calls the AI with the synthesis content and returns:
If AI is unavailable, the panel falls back to curated default prompts and session ideas. The panel can be re-generated at any time — each run uses the current synthesis content.
What the synthesis contains
The generated document has five sections:
| Section | What it covers |
|---|---|
| Per-Group Summaries | A brief summary of each stakeholder group's session synthesis |
| Convergent Themes | Ideas, concerns, or needs that appear across multiple groups |
| Divergent Findings | Points where groups have conflicting or incompatible views |
| Gaps and Blind Spots | Topics mentioned in some groups but absent in others |
| Action Plan | Prioritised recommendations with What / Why / Who / Impact for each item |
Synthesis history
Every synthesis run is preserved. The History section at the bottom of the page lists all past runs with their date and status. Click View on any completed entry to read that specific version.
Failure and retry
If synthesis generation fails, an error message is shown with a Retry button. Clicking Retry creates a new synthesis run — the failed record is preserved in the history.
The Public questionnaire mode lets a session collect responses from anyone with a shareable link — no account, no invitation, no login required. It is designed for low-friction data collection such as open surveys, event feedback forms, and intake forms where requiring registration would cause abandonment.
Enabling public mode
A unique share link (/q/[token]) is generated and displayed in a read-only field. Click Copy link to copy it to the clipboard. The session list shows a Public badge next to the session title.
Disabling public mode
Untick the Public questionnaire checkbox and click Save. The existing share link is immediately invalidated — anyone visiting the old URL sees a "Link no longer active" page. In-progress anonymous responses that have already started can still be submitted by those who have the session open, but new responses cannot be started.
How respondents use the link
Respondents open the share link in any browser — no sign-in required. On first visit, an anonymous session identifier is set in a browser cookie (mayetik-anon-id). This cookie is used to:
InterviewSession linked to the cookie value (not to a user account)A respondent who clears their cookies or switches to a different browser starts a new independent session.
Completion and knowledge brief
On completing the questionnaire, respondents see a completion screen. A knowledge brief is automatically generated in the background. Anonymous respondents cannot manually regenerate the brief (the Regenerate button is not shown) — they see the auto-generated content only.
Viewing anonymous responses
Anonymous responses appear in the responses dashboard (/projects/[projectId]/interviews/[interviewId]/responses) with Anonymous in the Name column and — in the Email column. The response detail panel shows "Anonymous respondent's answers." All other features (answer detail, metadata sidebar, brief link) work identically to authenticated responses.
Limitations (v1)
| Limitation | Notes |
|---|---|
| No spam protection | Anyone with the link can start unlimited sessions (a new cookie = a new session). |
| Brief visible on completion only | Anonymous respondents cannot return to view their brief after closing the tab. |
| No respondent identity | Responses are attributed to "Anonymous" unless the session contains an email/name question. |
| Synthesis includes anonymous responses | Session and project synthesis both include anonymous responses automatically. |
Ask Mayetik (/projects/[projectId]/ask) is a natural-language query interface that lets you ask questions across all completed session briefs in the project and receive a cited answer synthesized by AI. It turns the project's accumulated knowledge into a searchable resource.
Who can access Ask Mayetik
| Role | Access |
|---|---|
| Project Owner | Always — no extra steps |
| Project Admin | Always — no extra steps |
| Participant | Only if a Project Admin/Owner has explicitly granted Insights access from the Members page |
Participants without Insights access who visit /projects/[projectId]/ask are redirected to their dashboard.
Granting and revoking Insights access
/projects/[projectId]/members.Submitting a query
/projects/[projectId]/ask.Mayetik keeps the question and answer in the current page state rather than placing the question in the URL. It searches indexed briefs using semantic similarity, then generates an answer grounded in what the briefs actually contain. Refreshing or leaving the page clears the result.
Suggested questions
When at least 3 briefs are indexed, click Generate suggestions to have the AI produce 5 suggested questions and 5 suggested actions tailored to the project's sessions. Clicking a question pill pre-fills the query box; you still click Ask to submit. Actions are informational — they won't auto-submit.
Per-session Ask Mayetik
An Ask Mayetik card also appears directly on the per-session responses page (/projects/[projectId]/interviews/[interviewId]/responses) once briefs are indexed for that session. It works the same way but scopes all queries to this session's briefs only. Click Suggest questions → to load session-specific suggestions; clicking a pill immediately submits the query without an extra click.
Reading the answer
The answer is displayed below the query form as prose. Each claim is labelled with a source citation ("Brief 1", "Brief 2", etc.). Source links below the answer open the corresponding session in the responses dashboard, so you can read the full session detail behind any cited brief.
Cold-start nudge
If fewer than 3 briefs have been indexed for this project, a yellow banner explains that accuracy improves as more sessions are completed. The query form is still available — you may get a useful answer even with limited data, but results will be more reliable with more indexed briefs.
What gets indexed
Briefs are indexed automatically when a session is completed and reaches the COMPLETED state. Only briefs generated after Ask Mayetik was introduced are indexed; earlier briefs are not backfilled. Regenerating a brief via Retry brief will embed the new version.
Completed intake form records for the project are also indexed and appear as sources in query results — shown with a blue badge and the form title. There is no "View session →" link for intake sources.
Limitations (v1)
| Limitation | Notes |
|---|---|
| No backfill | Briefs generated before Ask Mayetik are not indexed. Regenerate a brief to index it. |
| Top-5 briefs | Each project-level query retrieves the 5 most relevant briefs (8 at org level). Very large projects may miss relevant material. |
| pgvector required | Ask Mayetik requires the pgvector PostgreSQL extension. In local development without pgvector, the page loads but queries return a "no briefs indexed" message. |
For org-wide queries across all projects, use Ask Mayetik (Org Level) — see Section 4.8.
Intake Forms (/projects/[projectId]/intake) let you collect structured information from external respondents through a conversational AI chat interface — without requiring them to create a Mayetik account.
Unlike structured sessions (which require invitation-based sign-in), intake forms are designed for open-access data collection: a patient intake, client onboarding questionnaire, vendor assessment, or any scenario where you want to collect responses from anyone via a shareable link.
Intake forms and the knowledge base
When a respondent completes an intake form, Mayetik generates a prose summary of their responses and indexes it alongside session briefs. This means completed intake records appear as sources in Ask Mayetik queries — respondents are attributed as "Form respondent" with the form name as the source label. Intake sources are shown with a blue badge to distinguish them from session briefs. This makes intake data part of the organization's queryable knowledge base without any additional configuration.
Key concepts
| Concept | Description |
|---|---|
| Form | A set of named fields defining what information to collect |
| Field | A single data point: label, snake_case key, type, optional hints |
| Record | One respondent's session — conversation transcript and collected field values |
| Share link | The public /f/[shareToken] URL respondents visit |
Form modes
| Mode | Description |
|---|---|
| Standard | Conversational AI collects all required fields in a natural dialogue |
| Short | More direct, concise prompts — better for quick-turnaround forms |
Creating an intake form
/projects/[projectId]/intake and click New Form.Adding fields
On the Fields tab, fill in the Label (displayed to the AI and on summaries), the Key (snake_case identifier used in exports), and optionally select a Field type.
Supported types: text, number, date, email, phone, select, boolean.
For select fields, add options one per line in the Options textarea.
Advanced options (collapsed by default):
Use the ▲ / ▼ arrows to reorder fields.
Activating and sharing
On the Settings tab, check Active and click Save. A share URL appears at /f/[shareToken]. Copy the URL or use the Embed snippet to add the form to any page.
Collecting respondent identity
Check Collect respondent name and email. When enabled, respondents are shown a name/email form before the chat begins. Their details are stored on the record and appear in the Records tab.
Response cap
Set a Response cap to stop accepting new records after a fixed number of completions. The cap counts completed records only — abandoned records do not count.
Viewing and exporting records
The Records tab shows all records with status (started, incomplete, completed), respondent info (if collected), and the conversation transcript. Two export formats are available via the Export links:
Webhook integration
Enter a Webhook URL and optional Secret in the Settings tab. Mayetik POSTs a signed JSON payload to your endpoint on each completed record. The signature header is X-Mayetik-Signature: sha256=<hmac>. Click Send test ping to verify the endpoint before activating. Failed webhooks can be resent from the Records tab.
Every session can be assigned a category that classifies the type of intelligence it captures. Categories enable structural filtering across the knowledge base — you can ask "show me all health checks" without relying on search terms to find them.
Available categories:
| Category | When to use |
|---|---|
| Health Check | Recurring team or customer health assessments |
| Win / Loss | Post-deal or post-cycle win/loss debriefs |
| Discovery | Customer or market discovery interviews |
| Alignment | Vision, strategy, or cross-team alignment sessions |
| Retrospective | Project, sprint, or quarter retrospectives |
| Pre-Mortem | Pre-launch risk and assumption checks |
| Stakeholder Feedback | Structured stakeholder or partner feedback |
| Other | Any session that doesn't fit the above |
Setting a category:
Open a session's Details tab and select a category from the dropdown. Save. The category appears as a badge in the session list and is used when filtering responses and querying the knowledge base.
A Series groups sessions that ask the same questions on a recurring schedule — monthly health checks, quarterly win-loss reviews, bi-annual alignment sessions. The series structure lets you track how the answers change over time and generate a trend analysis that compares synthesis content across instances.
Creating a series:
Navigate to Project → Series → New series. Give it a name, an optional description, and select a cadence (Monthly, Quarterly, Yearly, or Custom).
Assigning sessions to a series:
Open any session's Details tab. In the Series dropdown, select the series this session belongs to. Save. The session now appears in the series view with its synthesis status and response count.
Trend analysis:
Once at least two sessions in the series have completed syntheses, the Series detail page shows a Generate trend analysis button. This calls an AI model that compares the synthesis content across all instances and returns:
Trend analysis can be re-run at any time. Results are generated fresh on each run.
Voice Call Intake provides a phone-style response experience for intake forms. Where the standard intake UI is a chat interface, the call UI mimics an incoming phone call — a ring screen, a spoken greeting, and fields collected one at a time by voice.
Access: The call link is separate from the chat link. In the intake form settings, the Call link (/call/[shareToken]) can be copied and shared independently. Both links collect responses into the same intake record system.
Respondent experience:
Notes:
When you receive an invitation email, click the link. The invitation page shows what you're being invited to.
If you're already signed in with the correct email: the invitation is accepted automatically and you are redirected to /dashboard.
If you're not signed in: you'll see a sign-in prompt. Sign in with the same email address the invitation was sent to. After signing in, the invitation is accepted automatically.
Error states:
After signing in as a participant, you land on /interviews. This page shows all sessions you've been invited to that are currently published.
Each card shows:
Buttons:
Read-aloud preference: the first time you open a new session you are asked how you would like to receive questions:
Your choice is saved in your browser and applied automatically on any future visit to the same session. To change it, clear your browser's local storage for this site.
The session page shows one question at a time.
Saving your answers: answers are saved individually as you advance. If you close the browser and return later, your answers are preserved and you resume from where you left off. On your first question, Mayetik shows a brief note confirming this and reminding you that only the project team can see your completed response.
Voice input: on text and short-text questions, a microphone button appears. Click it to record a voice answer. Your speech is transcribed using OpenAI Whisper and placed in the text box. You can edit the transcription before moving on. Recording is limited to 25 MB per clip with a rate limit of 10 transcriptions per minute. Voice input is not available for address or signature questions.
Address questions: you will see a US postal address form with fields for Street Address, Apt/Suite (if enabled), City, State, and ZIP Code. Fill in the fields and click Next. If the administrator has enabled address verification, Mayetik will check your address against the USPS database. If a standardised form of your address is found, the fields are updated automatically and a green "Verified" badge appears. If verification fails, a warning is shown and you can click "Submit anyway" to save the address as entered.
Signature questions: type your full name in the input field. Once you have entered at least one character, a font picker appears — choose the handwriting style you prefer (Classic, Elegant, Casual, or Bold). A preview of your signature is shown with an underline. Click Next to confirm. Your name, chosen font, and the current date and time are recorded as your electronic signature.
After you complete a session, Mayetik automatically generates a personalized knowledge brief summarizing your answers using AI (GPT-4o-mini).
The brief goes through four states:
| State | What you see |
|---|---|
| Generating | A spinner — brief is being generated in the background (up to ~30 seconds) |
| Complete | The full brief text |
| Timeout | The poller waited 30 seconds with no result — click Retry brief to try again |
| Failed | Generation encountered an error — click Retry brief to attempt regeneration |
The brief is shown on the completion screen and is also visible when you click View on a completed session card.
Once the brief is complete, Mayetik sends you an email ("Your knowledge brief is ready") with a direct link back to the session. The email is only sent to signed-in participants — anonymous respondents who completed a public questionnaire do not receive a brief email.
Your individual answers are shown below the brief on the completion screen for reference.
Continue to your next session: if you have other sessions assigned that are not yet completed, an "Up next" card appears on the completion screen showing the session title, project name, and a "Start session" or "Continue session" button. Click it to go directly to your next session without returning to the dashboard first.
There are three invitation types in Mayetik:
| Type | Who sends it | What it does when accepted |
|---|---|---|
| Session | Project Admin/Owner | Creates a session membership (participant) for the specific session and a ProjectMembership (participant) for the project |
| Project | Project Admin/Owner | Creates or updates a ProjectMembership with the invited role (owner or admin) |
| Org | Org Admin/Owner or System Admin | Creates or updates an OrgMembership with the invited role (owner or admin) |
Important notes:
admin invitation, their role is updated to adminAll significant actions are recorded in the audit log. The audit log is append-only and cannot be edited or deleted.
Views:
/admin/audit) — all events, System Admin only/orgs/[orgId]/audit) — all events within the org and its projects, Org Admin/Owner only/projects/[projectId]/audit) — all events within the project, Project Admin/Owner onlyFilters available on all views:
interview.created)Interview, Project)Columns:
| Column | Description |
|---|---|
| Timestamp | Date and time the event was recorded |
| User | Email or name of the user who performed the action (blank = System) |
| Action | Dot-notation action string |
| Target type | The type of entity affected |
| Target ID | First 8 characters of the entity ID |
| Metadata | Additional context (e.g. previous role, email address) |
Full action list:
| Action | Target type | When it fires |
|---|---|---|
brief.generated | Brief | AI brief generation completes |
brief.embeddingIndexed | Brief | Brief indexed for Ask Mayetik |
brief.embeddingFailed | Brief | Brief indexing failed (retried automatically) |
interview.created | Interview | New session created |
interview.statusChanged | Interview | Session published, closed, or reopened |
interview.updated | Interview | Session title, description, or language edited |
invitation.accepted | Invitation | Invitee accepts an invitation |
invitation.resent | Invitation | Project admin resends a pending invitation |
invitation.revoked | Invitation | Project admin revokes a pending invitation |
invitation.sent | Invitation | New invitation created and emailed |
member.removed | ProjectMembership | Project member removed |
member.roleChanged | ProjectMembership | Project member role changed |
org.archived | Organization | Organization archived by System Admin |
org.created | Organization | New organization created |
org.unarchived | Organization | Organization unarchived by System Admin |
org.updated | Organization | Organization name or description edited |
project.archived | Project | Project archived |
project.created | Project | New project created |
project.ownerChanged | Project | Project owner changed by System Admin |
project.unarchived | Project | Project unarchived |
project.updated | Project | Project name or description edited |
projectSynthesis.triggered | ProjectSynthesis | Project synthesis run triggered |
question.created | Question | New question added to a session |
question.deleted | Question | Question soft-deleted |
question.updated | Question | Question text, hint, type, or options edited |
user.created | User | New user account created |
user.systemRoleChanged | User | User's system role changed |
intakeForm.created | IntakeForm | New intake form created |
intakeForm.updated | IntakeForm | Intake form settings updated |
series.created | InterviewSeries | New recurring series created |