Mayetik

This guide is for the person who opens a new Mayetik environment: you received the admin address for it, and nothing else is set up yet. It takes you from signing in to an invited person completing a session. Allow about 30 minutes. If you are a participant who was invited to answer a session, you want Taking part in a session instead.

Go to the sign-in page and enter the email address you were given as the admin address. Choose Sign in with Email.
Open the email and click the link. The link works for 10 minutes and only in a browser that asks for it once; if it expires, request a new one.
Prefer Google? Choose Sign in with Google, using the Google account for the same address. A different Google account counts as a different person and is refused.

"This workspace is invite-only." If you see this, the address you used is not the admin address and has no invitation. It is the environment working as intended: only the admin and people who have been invited can sign in. Use the right address, or ask the person who set up the environment.

2. What an empty environment looks like

A new environment contains one person (you, a system admin), no organization, no project and no sample sessions. That is why there is nobody to invite yet: every invitation belongs to an organization or a project. You will create those first.

3. Create your workspace

Open Admin from the top menu, then choose Create Workspace on the Admin Dashboard.
Enter the customer (organization) name, choose an owner, and name the starter project. Choose yourself as the owner for now; you can invite the customer's own people next.
Create it. You now have an organization and a project, and your account can see both.

Who can sign in is controlled by invitations. Anyone not invited is refused, so invite everyone who will manage the project.

Open Admin → Users. In the invite form, choose the organization, enter the person's email, and choose a role (Owner or Admin).
They receive an email. They open the link and sign in with the same address the invitation was sent to (magic link or Google). An invitation expires after 7 days; send a new one if it does.
Inside a project, Members and Invitations (from the project's menu) let a project owner or admin add more people to that project.

People who only answer sessions do not need accounts or invitations of this kind. You invite them to a specific session (section 7).

5. Build a session

Open your project, choose Sessions, and start a New session. The wizard has four steps: Start, Design, Launch, Share.
Start: name the session, or begin from a template (there are curated templates for common cases such as exit interviews, stakeholder discovery and usability feedback).
Design: add your questions. You can write them yourself, import them, or describe what you want to learn and let the assistant propose them. The question types are Text, Short text, Multiple choice, Multi-select, Rating scale, Slider, Yes / No, Number, Date, Time, Email and Ranking. Make a question Required only when you need an answer to continue.
Launch (publish) when the questions are ready. A draft cannot be answered; a published session can. You can close a session later to stop new answers, and reopen it.

The Design tab

While a session is a draft with no completed responses, one Design tab holds everything for building it. The questions are in the middle and each card edits in place. The assistant and the quality panel are beside them (on a phone they stack under the questions).

Ask the assistant for changes in plain words ("shorten this to ten minutes", "add a follow-up when the answer is No"). It returns a set of proposed changes, each with a reason and a before-and-after view. Tick the ones you want and choose Apply selected. Nothing changes until you apply, and a version is saved first.
Versions: save a version at any time, compare two, and restore one. Restoring saves a version first, so you can undo it.
Locks: lock a question to keep the assistant away from it. You can still edit it yourself.
Objectives: write what the session should learn, and mark which questions serve each. The quality review tells you when an objective has no question.
Question library: search questions from this project's other sessions and from the curated templates.
Order and section suggestions: on request, the assistant suggests a better order or section titles.
Sections: group a run of questions into a section with a title and a short introduction. Respondents see that introduction on a short screen before the section begins. A section can be skipped for people whose earlier answers say it does not apply.

Is it ready?

The quality panel scores the session out of 100 and lists what to fix: blockers first, then warnings and suggestions. You may see a range such as "likely 76 to 88", because a fresh review of the same session can differ by a few points. Once a session has 20 completed responses, findings that start "From responses:" appear too, for example a question many people skip or a point where people stop. They are suggestions, and they use only counts, never anyone's words.

Changing a session that has responses

Once a session has completed responses, its structure is fixed, because past answers refer to those questions. You can still reword a question or its hint, change whether it is required, and add choices at the end. Adding, removing, moving or retyping questions, sections and branching rules are refused, with a message pointing here.

To make those changes, choose Revise. It creates a new draft copy, titled "<title> (revision 2)", with all of the original's settings. The original keeps its responses, its public link and its invitations, and keeps running for anyone partway through it. After you publish the revision:

A banner offers to close the original. It never happens automatically.
The invitation box can add people who have not answered the original.
Move the public link here gives the revision the original's public address, once.
See what changed compares the two designs. It shows counts, never answer text.

6. Check it as a participant would

Once the session is launched, answer it once yourself before you invite anyone else: invite an address you control (section 7), or open the public link. The Launch checklist at the top of the session page has a preview step that takes you there. Then open Review and look at your own response and brief, so you know exactly what your participants will experience.

There are two ways, and you can use either or both.

Invite by email. In the session's Launch area, choose the Invitations tab, enter email addresses (one, or a pasted list), and send. Each person gets a personal link that opens the session directly. They do not need an account. The link is theirs alone, so it should not be forwarded. On the session's Details tab you can add your own short message (and, if you like, a subject line) to every invitation and reminder; it cannot contain links.
Public link. In the Sharing tab, turn on Public questionnaire and copy the link. Anyone who has it can answer without an account. You can set a response cap so it stops after a number of responses.

Use invitations when you need to know who answered and to remind people who have not. Use a public link for a broad audience where names do not matter.

8. Review the responses

Open the session and choose Review. There you will find:

Summary: how many people started and finished.
Responses: every response, one by one, with each person's knowledge brief (a short summary the system writes after someone finishes, usually within a minute).
Analysis: themes across all responses, once enough people have finished.
Ask: type a question in plain language and get an answer drawn from the completed briefs. It needs a few completed briefs before it is useful.

You can also use Ask Mayetik from the project menu to search across all the project's sessions.

Once a session has 10 completed responses, the Share view in Review can prepare a read-only page for the people who took part. It is built from your stored results, with no new AI call: key numbers, the themes, the summary, and an introduction and closing note that you write. The action plan is never included.

Edit or hide anything, check the Preview, then publish with two ticks: you reviewed everything, and participants were told results may be shared. The page has its own address that search engines do not index. Turn off or Give it a new link ends the old address at once. New sessions tell participants that results may be shared (the Details tab has a switch for that line); it only reaches people who answer after it is on.

Keeping the analysis up to date

On the Details tab, Keep analysis up to date lets a session refresh its themes and summary on its own, once enough new responses have arrived (you choose how many, and how often). It is off by default. If a refresh fails, the previous version stays. You can also let it update the results page draft; it never publishes a page you did not already publish unless you choose that option.

Reviewers and the daily digest

Both are on the Details tab and need no account for the people you add.

Reviewers (up to 20 per session) can read one session's completed responses, knowledge briefs and analysis, read-only. They sign in with the invited address and see nothing else in your workspace. They are never counted as invited respondents. On an anonymous session they see "Respondent 1, 2, …" and no names; the standard analysis is hidden there, so you can generate a separate no-names Analysis for reviewers and approve it before it is shown.
Notify others of new responses (up to 10 addresses) sends each person one email a day when the session has new completed responses. It shows the session, a count and a link, never names or answers, and every email has an unsubscribe link.

9. Trial limits

An organization has a trial window and a response allowance, shown in the banner at the top of the page: days remaining and responses remaining. By default a trial lasts 30 days and includes 100 completed responses; your pilot's terms may differ, and your Mayetik contact can tell you what applies to you. A session can also have its own response cap (set in its details).

What a participant sees when a limit is reached:

Response cap reached: "This session has reached its response limit and is no longer accepting new submissions."
Session closed: "This session is no longer accepting responses."
Trial or plan ended: the session is temporarily unavailable and asks them to contact the team that sent the link.

People who already finished can still open their completed response with their link.

10. The audit log

Every important action is recorded: who did it, what, and when. Answer text is not part of the log. You can read it in three places:

Project → Audit for one project.
Organization → Audit for everything in an organization.
Admin → Audit for the whole environment (system admins only).

11. Things that look like problems but are not

What you see	What it means
"This workspace is invite-only"	The address has not been invited. Invite it, or sign in with the invited address.
A magic link says it has expired	Sign-in links last 10 minutes. Request a new one.
Google sign-in is refused	The Google account's address must match the invited address.
A participant's brief is not there the instant they finish	It is written after they finish and usually appears within a minute.
A question cannot be moved or deleted, and the message mentions Revise	The session already has completed responses. Choose Revise to work on a copy.
The Design tab is missing	It is only for a draft with no completed responses. A published or answered session keeps the Questions tab.
An invitation link says it is invalid or expired	Invitations last 7 days, and a revoked one stops working. Send a new one.

12. Getting help

Use the Feedback button at the bottom right of any page to report a problem or ask a question; you can attach a screenshot. Or contact the person at Mayetik who set up your environment.

Getting started: from first sign-in to your first completed session

1. Sign in for the first time