Mayetik Tutorial

How to use this guide

Pick the path that matches your role: Path A if you're setting up and running interviews, Path B if you've been invited to complete one, or Path C if you're configuring Mayetik for your team. Each path is self-contained — you don't need to read the others. Every section ends with a hands-on exercise; the "You know it worked when" line tells you exactly what success looks like. For a complete reference to every field and action, see the Mayetik User Guide.

---

Path A — Project Admin

You're a project manager or team lead running a structured exit interview for a departing engineer. You have Project Admin access to an existing project.

A1. What is an interview?

A Mayetik interview is a structured set of questions completed one-to-one by each participant. Unlike a survey sent to a large group, it's designed for in-depth knowledge capture from individuals. Each participant gets their own session, and Mayetik generates a personalised brief summarising what they said.

Every interview moves through three statuses:

Status	Meaning
Draft	Being built. No participant can see or start it yet.
Published	Live. Invited participants can start and complete it.
Closed	No longer accepting new sessions. Existing answers are still accessible.

The lifecycle exists so you can build and edit an interview privately before anyone sees it. Finalise your questions before publishing — once participants have started, edits to question text can affect how their answers are interpreted.

Try it

Setup: You have Project Admin access to a project. No published interviews exist yet.

Steps:

1. Open the project dashboard at /projects/[projectId].
2. Click Interviews in the navigation.
3. Click New Interview.
4. Enter a title (e.g., "Engineering Exit Interview") and an optional description.
5. (Optional) Select a Language from the dropdown. Leave it as English for now — you can change it later on the Details tab.
6. Click Create Interview.

You know it worked when: The new interview appears in the interview list with a Draft status badge and your chosen title.

---

A1b. Alternative: import an interview from a JSON file

If you already have a questionnaire defined in a spreadsheet, document, or another tool, you can import it as a JSON file instead of building questions one by one. The Import from JSON section is on the same interview list page, directly below the New Interview form.

Step 1 — Get a template. Click Download template in the Import section to download interview-template.json. Open it in any text editor. The file shows all 16 question types with realistic example values.

Step 2 — Edit the template. Replace the example values with your own interview title, questions, and options. The minimum viable file is:

{
  "title": "My Interview",
  "questions": [
    { "order": 1, "text": "Your first question", "type": "text" }
  ]
}

For the full field reference — question types, options shapes, branch rule syntax, and condition type aliases — expand the Format reference panel on the import page, or see the Interview Import Format reference.

Step 3 — Upload and import. Select your file with the file picker and click Import. If validation passes you are redirected to the new interview's detail page. If validation fails an error is shown inline — fix the issue in your file and try again. No interview is created on failure.

What's supported on import:

• All 16 question types
• Branch rules (use targetOrder to reference another question's order value; only forward jumps are allowed)
• Stakeholder group and language fields
• SurveyJS format (auto-detected; visibleIf expressions are not converted)

Known limitation: import always creates a new draft — it cannot update an existing interview. Duplicate titles within the same project are rejected with a clear error.

Try it

Setup: You have Project Admin access to a project.

Steps:

1. Go to the Interviews list page.
2. In the Import from JSON section, click Download template to save interview-template.json.
3. Open the file in a text editor. Change "title" to "Imported Exit Interview" and delete all but the first two questions.
4. Save the file. Back in Mayetik, click Choose file, select your edited file, and click Import.

You know it worked when: You are redirected to the new interview's detail page showing "Imported Exit Interview" in draft status with two questions listed.

---

A2. Building your first interview

From the interview detail page, use the Questions section to add questions. Mayetik supports 16 question types. The most commonly used are:

• Text — a multi-line free-form text box. Use it for open questions where you want the participant's own words. Supports voice input.
• Short Text — a single-line input with optional format validation (pattern preset) and character limit. Ideal for identifiers, codes, or constrained short answers. Supports voice input.
• Multiple Choice — the participant picks one option from a list you define. Use it when the answer space is bounded (e.g., "Which team did you primarily work with?").
• Yes / No — a two-option toggle. A simplified alternative to a two-option Multiple Choice question.
• Multi-Select — checkboxes for selecting multiple options. Use when multiple answers can apply simultaneously.
• Rating Scale — the participant picks a number on a range you configure. Use it to capture confidence, satisfaction, or effort levels.
• Number — a numeric input field. Use for counts, quantities, or any free-form number.
• Slider — a drag-style range selector. Useful when you want participants to see the full scale visually.
• Date / Time — date or time picker inputs.
• Email — a text input that validates the format of an email address.
• Address — a five-field US postal address form (Street, Apt/Suite, City, State, ZIP). Optionally validates the address against the USPS API. Use for intake forms, shipping addresses, or location capture.
• Signature — a typed electronic signature with a handwriting-style font picker and a timestamp. Use for consent forms or acknowledgement steps.
• File Upload — lets participants attach a file.
• Location — a location input.
• Ranking — a drag-to-rank list. Use when you want participants to prioritise options relative to each other.

Tick Required on any question where a blank answer isn't acceptable. Required questions must be answered before the participant can advance to the next one.

Use the ↑ and ↓ buttons to reorder questions after adding them. To remove a question, click Delete — this is a soft delete, so existing answers from past sessions are preserved.

Try it

Setup: The draft interview you created in A1 is open.

Steps:

1. In the Questions section, enter "Describe your most significant project in the last year" in the question text field.
2. Leave the type as Text. Tick Required. Click Add Question.
3. Add a second question: "How would you rate your overall experience on the team?" — type Rating scale, Required. Click Add Question.
4. Add a third question: "What was your primary area of work?" — type Multiple choice. Add three options (e.g., "Backend", "Frontend", "Infrastructure"). Click Add Question.

You know it worked when: All three questions appear in the questions list in the order you added them. The text and rating questions show a red asterisk (*) indicating they are required.

Bonus: try Address and Signature types

5. Add a fourth question: "What is your mailing address?" — type Address. Enable Show Street 2 and leave USPS verification enabled. Click Add Question.
6. Add a fifth question: "Please sign below to confirm your participation" — type Signature. Tick Required. Click Add Question.

You know it worked when: Both questions appear in the list with their respective types. When a participant reaches the address question they will see five labelled fields. When they reach the signature question they will see a name input followed by a font picker once they start typing.

---

A3. Publishing and inviting participants

An interview must have at least one active question before you can publish it. Click Publish in the Status section of the interview detail page. The status badge changes to Published immediately.

To invite a participant, go to the Invitations page (/projects/[projectId]/invitations). Use the Invite Participant form: select the published interview from the dropdown, enter the participant's email address, and click Send Invitation. They receive an email with a time-limited link. If the interview's language is set to Spanish, this email will be in Spanish. When they accept it, they are added to the project as a participant and can start their session.

Try it

Setup: Your draft interview has at least one active question.

Steps:

1. Open the interview detail page.
2. Click Publish in the Status section.
3. Navigate to the project's Invitations page.
4. In the Invite Participant form, select your newly published interview.
5. Enter a valid email address and click Send Invitation.

You know it worked when: The interview status badge changes to Published. The Sent Invitations table shows a new row with the email address, the interview name, and status Pending.

---

A4. Adding branch rules

A branch rule is an if-then instruction attached to a question: if the participant's answer meets a condition, then route them to a specific follow-up question instead of continuing in the default sequence.

Think of a doctor's intake form: "If you circled Yes on 'Do you have a pre-existing condition?', please go to Page 4." Page 4 only appears when the condition is true. Everyone else skips it and continues normally.

The three parts of a branch rule:

1. Source question — the question the rule is attached to (e.g., "Rate your experience: 1–5").
2. Condition — the check evaluated against the participant's answer. Supported conditions: equals, not equals, less than, less than or equal, greater than, greater than or equal, contains, is empty, not empty.
3. Target question — where to route the participant when the condition is true.

When a participant answers the source question, Mayetik checks all rules attached to it in priority order (lowest number first). The first rule whose condition matches determines the next question. If no rule matches, the participant moves to the next question in the default sequence.

Terminal questions: Mark a question as terminal using the "Mark as terminal question" checkbox in the question editor. When a participant reaches a terminal question and answers it, the interview ends immediately — regardless of how many questions remain. This is useful for early-exit paths, such as a screening question that determines the rest of the interview does not apply.

Try it

Setup: Your interview has at least two questions. Question 1 is a Rating scale (range 1–5). You have a third question of any type that will serve as an alternative follow-up.

Steps:

1. Open the interview detail page and click Edit next to Question 1.
2. In the branch rules section, click Add Rule.
3. Set the condition to less than with value 3.
4. Set the target question to your third question.
5. Click Save Changes.
6. Accept the test participant invitation yourself (or use a second account) and complete the interview twice: once with a rating of 2, once with a rating of 4.

You know it worked when: A rating of 2 routes directly to the third question, skipping Question 2. A rating of 4 proceeds to Question 2 as normal. On the responses page, the session where the rule fired shows a Branch rule matched indicator between the relevant answers.

---

A5. Viewing responses and briefs

The responses page (/projects/[projectId]/interviews/[interviewId]/responses) shows every participant session. The summary row at the top shows total sessions, completed count, and completion rate.

Click View on any session row to open the session detail. You'll see:

• The participant's answers in the order they were actually presented (following their path through any branch rules)
• A Branch rule matched label wherever routing fired
• A metadata sidebar: session status, questions presented, answers recorded, questions skipped, branch rules fired, and brief status

The knowledge brief is an AI-written synthesis of the participant's answers — not a transcript. It organises the key themes from their answers into readable prose. The brief link in the sidebar opens it in the participant's interview view.

Try it

Setup: At least one participant has completed a session in one of your interviews.

Steps:

1. Open the responses page for that interview.
2. Click View on a Completed session.
3. Read through the answer detail.
4. Check the metadata sidebar: note the "Questions presented" and "Questions skipped" values.
5. Click View brief in the Brief row of the sidebar.

You know it worked when: The session detail shows answers in the order the participant received them. The metadata sidebar shows non-zero values for "Questions presented" and "Answers recorded." The brief link opens and shows AI-generated prose (not a raw list of answers).

---

A6. Project Synthesis

When you have run interviews with multiple stakeholder groups and each interview has a completed interview synthesis, Project Synthesis pulls them together into a single strategic document.

The synthesis is generated from the prose content of each interview's synthesis — not from raw answers. This means the AI is working from curated summaries, not a dump of everything participants said.

How to set a stakeholder group

Before generating a project synthesis, assign a stakeholder group to each interview:

1. Open the interview detail page.
2. In the Details section, fill in the Stakeholder Group field (e.g., Engineering, Product, Design).
3. Click Save.

Interviews without a stakeholder group are labelled "General" in the synthesis.

Triggering a synthesis

1. Open the project dashboard and click Synthesis in the navigation.
2. The Generate new synthesis button becomes active once at least 2 interview syntheses are in the Completed state.
3. Click Generate new synthesis.
4. The page enters a "Generating…" state. The synthesis runs in the background — refresh or wait for the poller to update automatically.

Reading the output

The synthesis document has five sections:

Section	What it covers
Per-Group Summaries	One paragraph per stakeholder group drawn from each interview's synthesis
Convergent Themes	What multiple groups agree on — shared concerns or priorities
Divergent Findings	Where groups have conflicting needs or different views
Gaps and Blind Spots	Topics raised by some groups but absent from others
Action Plan	Prioritised recommendations with What / Why / Who / Impact for each item

The Action Plan section is the most actionable output — it translates the analysis into concrete next steps with clear accountability.

History

Every synthesis run is stored. The History list at the bottom of the page lets you view older runs by clicking View. This is useful for tracking how your organization's priorities have evolved across successive synthesis runs.

Try it

Setup: Your project has at least two interviews, each with a completed interview synthesis (visible on the responses page for each interview). Set a stakeholder group on each interview.

Steps:

1. Open /projects/[projectId]/synthesis.
2. Confirm the Generate new synthesis button is enabled (it will be greyed out with an explanation if not enough syntheses exist).
3. Click Generate new synthesis.
4. Wait for the synthesis to complete (up to ~60 seconds with a live OPENAI_API_KEY).
5. Read through all five sections of the output.
6. Trigger a second synthesis by clicking Generate new synthesis again and verify a new History entry appears.

You know it worked when: The page shows a completed synthesis document with all five sections visible. The History list shows the run with a COMPLETED status. The project audit log (/projects/[projectId]/audit) shows a projectSynthesis.triggered entry.

---

A7. Collecting responses without requiring sign-in (Public Questionnaire)

By default, Mayetik requires every participant to have an account and accept an invitation. That's the right choice for sensitive knowledge-capture interviews. But for lighter-touch data collection — open surveys, event feedback, intake forms — that friction causes abandonment.

Public questionnaire mode generates a shareable link. Anyone with the link can respond directly in their browser with no account, no invitation, and no login prompt.

How to enable it

1. Open the interview detail page → Details tab.
2. Tick the Public questionnaire checkbox.
3. Click Save.

A unique share URL appears in a read-only field. Click Copy link to copy it to the clipboard. The interview list now shows a Public badge next to the interview title.

How to share it

Paste the /q/[token] URL anywhere — email, Slack, a QR code, an event page. Anyone who opens it sees the questionnaire immediately. Their session is tracked by a browser cookie so they can close the tab and resume later from the same browser.

Turning it off

Untick the Public questionnaire checkbox and click Save. The existing share link stops working immediately. Any sessions already in progress can still be submitted from the respondent's open tab, but new sessions cannot start.

What you see in responses

Anonymous sessions appear in the responses dashboard exactly like authenticated sessions, except the Name column shows Anonymous and the Email column shows —. Session detail, answers, and the knowledge brief work the same way. Anonymous responses are included in thematic analysis and project synthesis automatically.

Try it

Setup: You have a published interview with at least one question.

Steps:

1. Open the interview detail page → Details tab.
2. Tick Public questionnaire and click Save.
3. Copy the share URL from the form.
4. Open the URL in an incognito window (no cookies, no account).
5. Answer all questions and submit.
6. Back in your admin view, open the responses page for this interview.

You know it worked when: The questionnaire loaded in the incognito window without any login prompt. The responses page shows the completed session with "Anonymous" in the Name column.

---

A8. Asking questions across your interview corpus

Once participants have completed interviews and briefs exist, Ask Mayetik lets you query the project's accumulated knowledge in plain language. Instead of reading through individual briefs one by one, you type a question and receive an AI-synthesised answer drawn from the most relevant briefs, with citations back to the original sessions.

How it works

Ask Mayetik embeds each completed brief as a vector and stores it in a project-scoped index. When you submit a query, your question is embedded the same way and compared to the brief index using semantic similarity. The top-matching briefs are retrieved, and an AI model generates a grounded prose answer citing specific briefs by number. Each citation links directly to the session detail in the responses dashboard.

Accessing Ask Mayetik

Project Owners and Project Admins can always access /projects/[projectId]/ask. Participants can access it only if a Project Admin/Owner has granted them Insights access from the Members page (see section A8b below).

Submitting a query

1. Open the project dashboard and click Ask Mayetik in the navigation.
2. Type your question in the text box.
3. Click Ask.

The answer appears below the form. Source links under the answer open the relevant sessions.

Cold-start behaviour

If fewer than 3 briefs are indexed, a yellow banner warns that accuracy is limited. The query form remains usable — you may still get useful results, but they will be more reliable once more sessions have been completed.

Try it

Setup: At least one interview session has been completed in your project and the brief is in the COMPLETED state.

Steps:

1. Navigate to /projects/[projectId]/ask.
2. Type a question relevant to your interview content (e.g., "What challenges did participants mention most often?").
3. Click Ask and wait for the answer to appear (up to ~10 seconds).
4. Click one of the source citation links below the answer.

You know it worked when: An answer in prose appears, referencing "Brief 1", "Brief 2", etc. Clicking a source link navigates to the correct session in the responses dashboard.

---

A8b. Granting participants access to Ask Mayetik

By default, participants cannot access Ask Mayetik — they can only see their own brief. If a participant should be able to query the full project corpus (for example, a team lead who completed an interview and also needs to review findings), you can grant them Insights access.

To grant Insights access:

1. Go to the project's Members page at /projects/[projectId]/members.
2. Find the participant's row.
3. In the Insights access column, click Grant access.

The button changes to Revoke access. To remove the permission, click Revoke access. The change takes effect immediately — no reload required on the participant's side on their next navigation.

Try it

Setup: A participant (not you) has an active project membership with the participant role.

Steps:

1. Go to /projects/[projectId]/members.
2. Locate the participant's row and click Grant access in the Insights access column.
3. Log in (or use a second account) as the participant.
4. Navigate to /projects/[projectId]/ask.

You know it worked when: The Members page button changes to Revoke access immediately after clicking. The participant account can reach /projects/[projectId]/ask without being redirected.

---

A9. Collecting structured data with Intake Forms

Intake Forms are a different collection mode from structured interviews. Instead of one question at a time, the AI conducts a free-flowing conversation to collect a predefined set of named data fields. Respondents don't need a Mayetik account — they access the form via a shareable link.

Use Intake Forms for: patient intake, client onboarding questionnaires, vendor assessments, event registrations, or any scenario where you want a structured record but don't need the respondent to be invited individually.

Building your first intake form

1. Open the project dashboard and click Intake Forms in the navigation.
2. Click New Form and enter a title.
3. In the Fields tab, click Add Field and add at least one field:
   • Label: "Reason for visit"
   • Key: reason (auto-derived from the label if left empty)
   • Field type: text
4. Switch to the Settings tab, tick Active, and click Save.
5. A share URL at /f/[shareToken] appears. Copy it.

Testing the respondent experience

Open the share URL in an incognito window. The AI will greet the respondent and guide them through collecting all required fields. When done, the conversation ends with a summary of what was collected.

Reviewing records

In the form builder, click the Records tab. Each completed session appears as a row. Click View to read the conversation transcript and see the extracted field values.

Exporting data

Click Export CSV to download a spreadsheet with one row per record and one column per field key. Click Export JSON for a full structured export.

Try it

Setup: You have Project Admin access to a project.

Steps:

1. Navigate to /projects/[projectId]/intake and click New Form.
2. Enter a title (e.g., "Patient Intake") and click Create.
3. Add a field with label "Full name" and key full_name.
4. Add a second field with label "Reason for visit" and key reason.
5. Go to the Settings tab, tick Active, and click Save.
6. Copy the share URL and open it in an incognito window.
7. Complete the conversation until the summary screen appears.
8. Return to the Records tab and verify the new record appears.

You know it worked when: The Records tab shows a completed record with the values you entered for "Full name" and "Reason for visit" extracted from the conversation.

---

Path B — Participant

You've received an invitation email. Your team lead is using Mayetik to capture your expertise before you move to a new role. You've never used Mayetik before.

B1. Accepting your invitation

Click the link in your invitation email. What happens next depends on your situation:

• Already signed in with the correct email: The invitation is accepted immediately and you go straight to your dashboard.
• Not signed in: You see a sign-in page. Sign in using the same email address the invitation was sent to — either via magic link (email) or Google. If you don't have a Mayetik account yet, one is created automatically when you sign in for the first time. After signing in, the invitation is accepted automatically.

The most common problem is signing in with a different email (for example, a personal Google account instead of your work email). If you see an "email mismatch" error, sign out and sign back in with the correct address.

Try it

Setup: You have received a Mayetik invitation email at the address you plan to use.

Steps:

1. Open the invitation email and click the invitation link.
2. If prompted to sign in, use the same email the invitation was sent to.
3. Wait for the redirect after signing in.

You know it worked when: You land on the interviews dashboard at /interviews and can see the interview you were invited to listed with a Not started badge.

---

B2. The interviews dashboard

Your dashboard at /interviews shows all published interviews you've been invited to. Each card shows the interview title, the project it belongs to, the number of questions, and your current status.

Button	When it appears
Start	You haven't begun the interview yet
Continue	You've started but not finished; picks up from where you left off
View	The interview is complete; opens your answers and brief

Answers save as you go. If you close the browser mid-way through, click Continue on your next visit — your previous answers are preserved and you resume from the next unanswered question.

Try it

Setup: You have accepted an invitation to at least one interview.

Steps:

1. Navigate to /interviews.
2. Find the interview card and note the status badge and question count.
3. Click Start (or Continue if you've already started).
4. Answer the first question and click Next.
5. Close the browser tab.
6. Return to /interviews.

You know it worked when: After re-opening the dashboard, the interview card shows In progress and the button has changed from Start to Continue.

---

B3. Completing an interview

Before your first question, you will be asked how you would like to receive them:

• Read to me — each question is spoken aloud as it appears. A Stop reading button lets you silence it; a Read again button replays it. Your browser's built-in text-to-speech is used — no microphone needed for this.
• I'll read myself — questions appear on screen only. This is the same experience as before the feature was introduced.

Your choice is saved in your browser. If you return to the same interview later, the preference is applied automatically and the choice screen does not appear again.

The interview shows one question at a time. Answer the current question using the input provided:

• Text questions — type your answer in the box, or use voice input (see below)
• Multiple choice — click one option from the list
• Rating scale — click the number that represents your answer

Questions marked with an asterisk (*) are required — you must answer them before you can move on. Click Next to save your answer and go to the next question. On the final question, Next completes the interview.

Voice input

On text questions, a microphone button appears beside the text box. Here is what it does:

1. Click the microphone to start recording in your browser.
2. Speak your answer. When you stop recording, the audio is sent to OpenAI Whisper, which converts it to text.
3. The transcription appears in the text box. You can edit it freely before clicking Next.
4. The audio itself is never stored — only the transcribed text is saved with your answer.

If the transcription isn't quite right, just correct the text — there is no penalty for editing. Voice input only appears on text questions; it is not available on multiple choice or rating scale questions. Recordings must be under 25 MB, and you can transcribe up to 10 clips per minute.

Try it

Setup: You have a Not started interview on your dashboard that includes at least one text question.

Steps:

1. Click Start on the interview card.
2. On the "Before you begin" screen, click Read to me.
3. Wait for the question to be spoken, then click Stop reading.
4. On a text question, click the microphone button.
5. Speak two or three sentences, then stop the recording.
6. Wait a few seconds for the transcription to appear in the text box.
7. Make a small edit to the transcribed text.
8. Click Next and complete the remaining questions.

You know it worked when: The "Before you begin" screen appears on first visit and disappears after your choice. After stopping the voice recording, transcribed text appears in the text box within a few seconds. You can edit it before clicking Next. After answering all questions, you see the completion screen — not the question form. The interview card on your dashboard changes to Completed.

---

B4. Your knowledge brief

After you complete an interview, Mayetik automatically generates a knowledge brief — a short AI-written document that synthesises what you said, organised by theme. This is not a copy of your answers; it is prose that draws out the key points from your responses.

The brief takes up to about 30 seconds to appear. On the completion screen you'll see one of four states:

State	What to do
Generating	Wait — the spinner disappears when the brief is ready
Complete	Your brief is displayed below
Timeout	Click Retry brief — generation is still processing in the background
Failed	Click Retry brief to attempt regeneration

You can revisit your brief at any time: return to /interviews, click View on a completed interview, and scroll down.

Try it

Setup: You have just completed an interview (reached the completion screen).

Steps:

1. Stay on the completion screen.
2. If you see a spinning indicator, wait up to 30 seconds.
3. Once the brief appears, read the first section heading.
4. Scroll down past the brief to see your original answers listed below.

You know it worked when: The brief appears as formatted text with section headings that reflect your specific answers (not generic labels like "Summary"). Your individual answers are visible below the brief text.

---

Path C — Org and System Admin

You're setting up Mayetik for a new team. You need to create the organization, add a project, bring in a project admin, and confirm everything is in order.

C1. Setting up an organization

An organization is the top-level container in Mayetik. Projects, interviews, and members all live within an org. Think of it as your company, department, or team division.

System Admins create organizations at /admin/organizations/new. You provide a name (unique across the platform), an optional description, and assign an initial owner from the list of registered users. The owner has full administrative control of the org.

Try it

Setup: You have System Admin access. The target team does not have an org yet.

Steps:

1. Navigate to /admin/organizations/new.
2. Enter a name and optional description for the organization.
3. Select the org owner from the Owner dropdown.
4. Click Create Organization.

You know it worked when: You are redirected to the org detail page. The new org appears in the Active tab of /admin/organizations.

---

C2. Creating a project

A project is where interviews and participants live. You can have multiple projects per org — one per team, initiative, or research programme.

From the org dashboard at /orgs/[orgId], click New Project. Give it a name (unique within the org) and an optional description. The person who creates the project is automatically assigned as the project owner.

Try it

Setup: An org exists and you are signed in as the org owner or admin.

Steps:

1. Navigate to /orgs/[orgId] for your org.
2. Click New Project.
3. Enter a project name and description.
4. Click Create Project.

You know it worked when: The project appears in the projects table on the org dashboard. Clicking Manage on that row opens the project dashboard at /projects/[projectId].

---

C3. Adding team members

Two kinds of invitations exist at the project level:

• Project admin invitation (via the Invite Project Member form on the Invitations page) — gives someone the ability to build interviews, send invitations, and view responses. Use this for team leads and coordinators.
• Participant invitation (via the Invite Participant form on the same page) — gives someone access to a specific published interview. Use this for the people you want to interview.

These are different invitation types. A participant cannot see any admin page; they can only access the interviews they have been personally invited to. A project admin cannot complete interviews as a participant unless they also receive a separate participant invitation.

If you need to bring in a coordinator who will manage multiple projects, send them an org-level invitation (/orgs/[orgId]/members) with the Admin role.

Try it

Setup: A project exists. You have Project Owner or Admin access.

Steps:

1. Go to the project's Invitations page at /projects/[projectId]/invitations.
2. In the Invite Project Member form, enter an email and select role Admin.
3. Click Send Invite.
4. Check the Sent Invitations table at the bottom of the page.

You know it worked when: A new row appears in the Sent Invitations table showing the email address, role Admin, and status Pending. After the person accepts and you open /projects/[projectId]/members, they appear with the Admin role.

---

C4. The audit log

Every significant action in Mayetik is recorded in an append-only audit log. It cannot be edited or cleared. Use it to verify that a setup step happened, or to investigate unexpected changes.

Three scoped views exist:

• System-wide (/admin/audit) — every event on the platform
• Org-scoped (/orgs/[orgId]/audit) — all events within the org and its projects
• Project-scoped (/projects/[projectId]/audit) — events for one project

All views support filters for action type, target type, and date range. Results are paginated 20 per page. Events include: who performed the action, when, what entity was affected, and any relevant metadata (such as the previous role before a change).

Try it

Setup: You have completed C1, C2, and C3 above.

Steps:

1. Navigate to /orgs/[orgId]/audit for the org you created.
2. Locate the org.created entry in the list.
3. Find the project.created entry for the project from C2.
4. Use the Action filter, type invitation.sent, and apply the filter.

You know it worked when: You can find all three event types — org.created, project.created, and invitation.sent — each with the correct user email and timestamp. The action filter narrows the results to only rows matching invitation.sent.

---

Quick reference

For full details on every field, action, and error state, see the Mayetik User Guide.

Role hierarchy

Role	What they can do
System Admin	Everything on the platform — all orgs, projects, users, and audit logs
Org Owner / Org Admin	Manage the org, create projects, invite org members, view org audit log
Project Owner / Project Admin	Build interviews, manage members and invitations, view responses and project audit log
Participant	Complete their assigned interviews and view their own briefs — no access to any admin page

A participant who should become a project admin must receive a separate project-type invitation with the Admin role.

Glossary

Term	Meaning
Interview	A structured set of questions within a project, completed one-to-one by each participant
Session	One participant's run of an interview — their answers, path taken, and generated brief
Branch rule	An if-then instruction on a question that routes the participant to a different next question when a condition is met
Terminal question	A question that ends the interview immediately when reached, regardless of remaining questions
Brief	An AI-generated prose summary of a participant's answers, produced automatically on completion
Draft	Interview status: not yet visible to participants
Published	Interview status: participants can start and complete it
Closed	Interview status: no longer accepting new sessions
Invitation	A time-limited email link granting access to an interview, project, or organization
Project membership	The link between a user and a project, with a role (owner, admin, or participant)
Audit log	An append-only record of all significant actions, filterable by action type and date range
Voice input	A microphone button on text questions that transcribes speech into the answer box via OpenAI Whisper
Ask Mayetik	A natural-language query interface at /projects/[id]/ask that retrieves answers synthesised from indexed interview briefs, with citations linking to individual sessions
Insights access	A per-member permission that allows a participant to access Ask Mayetik; granted and revoked from the Members page
Intake Form	An AI-chat collection form for external respondents — no account required; defined by named fields and shared via a public link at /f/[shareToken]
Intake Record	One respondent's run of an intake form — their conversation transcript and the field values extracted from it