Job search
Miro in a Design Interview: Check Visitor Editing, Board Navigation, and Export Permission
Current official documentation and two completed fictional records separate board entry, editing, object locks, navigation and authorized final-artifact delivery.
Before a design interview in Miro, confirm how the interviewer has shared the board, what you can edit and where the work should remain afterward. A visitor link, a guest invitation and an editing permission are different things. Buying your own subscription does not establish permission to change or export an employer’s board.
This guide reviews official Miro documentation checked October 21, 2026. No employer board, account or private interview material was accessed. The completed examples are fictional; their local record checks are not Miro runtime tests. LandOffer publishes this guide and offers job-search tools. You can browse recent roles on LandOffer.ai while keeping each interview’s instructions separate.

Identify the invitation type and the access level
Miro distinguishes visitors, guests and members. Visitors use public board links and need not have an account. Guests are registered external collaborators invited to particular private boards on paid plans. Members participate in a team. Check the Miro role separately from your status as an interview candidate.
Separately, board access rights distinguish viewing, commenting and editing. A board that opens successfully is not proof that you can create the objects the exercise requires. The documentation also says Request Access emails the owner. Treat it as an actual request, rather than a harmless button for inspecting permissions.
Use the interviewer’s existing instructions to establish the intended entry route. If an emailed invitation expects a particular identity, an unrelated account may not represent that invitation. If the employer provides visitor access, do not assume you must become a member or purchase a plan. Ask which route they expect before changing accounts or creating anything.
A public link is not a confidentiality guarantee. Miro’s visitor guidance warns that people possessing the link can access the board and may share it further. Do not forward the interview link, paste it into another service or invite a collaborator to diagnose it. The host should decide how its exercise is shared.
If access fails, describe the visible problem through the verified recruiting exchange: the link opens a permission screen, the board is view-only, or the expected editing tool is missing. Describe the missing access without proposing broader public sharing. Ask for the intended candidate access to the intended board, preserving the scope of the interview.
Check the tools without disturbing the exercise
Miro’s visitor documentation describes basic editing tools such as shapes, lines, text, sticky notes and the pen, subject to access level. It also lists visitor limitations, including locking and unlocking objects. A registered visitor can have more creation tools than an unregistered visitor; registration alone does not grant a different board access level.
Agree where a harmless readiness check belongs before adding anything. An interviewer may provide a practice area or prefer to verify your tools at the start. Do not alter the task prompt, other candidates’ frames or a prepared example to test dragging. A designated practice corner lets you check the requested interaction while leaving the prepared exercise intact.
Separate an object problem from a board-wide permission problem. If you can add a sticky note in the designated area but cannot move the prompt, the prompt may be intentionally locked. If nothing is editable, ask about access. A tool absent from a visitor toolbar is another distinct issue; explain which requested action needs it.
The locking documentation says visitors cannot lock or unlock objects. Protected locks add a further restriction: only the owner or co-owner who applied that lock can remove it. Another collaborator having edit rights is therefore not evidence they can unlock every object. Ask the host to identify the candidate’s working area instead of attempting broad unlock actions.
Navigate the canvas before moving objects
Miro’s mouse, trackpad and touchscreen guide separates panning from selection. It describes hand/select modes, V and H shortcuts, Space-drag for panning, and bottom-right controls for zoom, fit and the minimap. Input behavior varies with the device and selected navigation mode; do not assume every wheel or two-finger gesture behaves identically.
Before the timed discussion, identify the start frame, the working area and a way back to the overall board. Zooming into one part of the canvas can put adjacent instructions outside the viewport; that is different from deleting an object. If you lose your place, recover the view rather than dragging visible content toward yourself. Ask the interviewer to point out the intended frame if the structure is unclear.
During the exercise, distinguish changing your viewport from changing shared objects. Narrate the design reasoning the interviewer needs, not every navigation gesture. If an object moves unintentionally, acknowledge it and ask how to restore the expected state within the interview’s rules. Do not claim a browser undo or another action is safe for every shared-board situation.
If the input setup is uncomfortable or inaccessible, raise that before substantive work where possible. Ask the host to agree an alternative before moving the exercise to another tool. This review did not test a device, keyboard workflow or assistive technology, so it cannot promise that these documented controls resolve every candidate’s needs.
Worked example: turn a blocked action into a specific request
The following board, candidate and observations are invented. Priyan is invited to discuss a fictional returns-status flow. The stipulated interview instructions allow work only in a frame named Candidate Draft and prohibit copying the exercise elsewhere. This is not a real Miro board or an employer’s question.
His filled readiness record separates what the fictional observations support:
| Observation in the example | Supported interpretation | Completed decision |
|---|---|---|
| The link opens without a signed-in account | Visitor route in this stipulated case | Keep that route; do not assume a paid seat is required |
| A sticky note can be added in the designated practice corner | That basic editing action is available there | Mark sticky-note readiness confirmed for this example, not every tool |
| The prompt object cannot be moved | A locked object is consistent with the observation | Leave it unchanged and ask whether it is intentionally protected |
| A specialized component tool is absent | Requested tool availability remains unresolved | Ask whether ordinary shapes and text satisfy the exercise |
| Candidate Draft is initially offscreen | Location needs clarification, not necessarily new permissions | Find the named frame with the host before starting |
| No export action is available | Editing does not establish export capability | Retain the work on the host board; request the required handoff route |
Priyan’s complete, unsent note is narrow:
I can open the supplied link as a visitor and, in the designated practice corner, add a sticky note. The prompt object does not move, so I have left it unchanged. Could you confirm the Candidate Draft frame, whether ordinary shapes and text are sufficient, and whether the prompt is intended to stay locked? I will keep the exercise on your board. Please also confirm whether you want only the board handoff or a separately authorized export at the end.
Given the stipulated observations, Priyan’s next step is clarification rather than a subscription purchase or a request to expand public sharing. Priyan can already perform one permitted interaction, while the host can answer the specific tool and location questions. If the host later requires a feature unavailable through that route, the host can decide the appropriate access or alternative.
Notice what remains untested. Adding a note in the fictional practice corner does not prove that every frame is editable, that the board will remain accessible after the interview, or that the absent tool is essential. Each readiness claim is tied to one observation rather than a broad declaration that “Miro works.”

Treat exporting as a separate permission and purpose
Miro’s copying and exporting documentation describes team/admin restrictions and board-level controls. Even where copying is allowed, its table does not permit unregistered visitors to export or duplicate boards. Registered visitors and guests still depend on applicable content settings. Editing access alone does not establish export rights.
There is also an employer decision beyond the software capability: what may leave the interview environment, for what purpose and for whom? An enabled export option does not make an interview prompt available for a public portfolio. Likewise, permission to provide a final frame to the interviewer need not permit downloading every frame, attachment or comment.
Ask for the required submission route and scope before the session ends. The host might review the board directly or request a specific artifact. Do not substitute screenshots, a duplicate board or an external recording when exporting is restricted. Those actions still copy information; they are not permission-free workarounds.
If the host expects an export but your role cannot produce one, explain that mismatch. The owner can decide whether to provide the artifact, adjust the intended access or accept the board itself. Upgrading your personal workspace is not evidence that the employer’s administrative policy or content permissions have changed.
Worked example: close the interview without taking the board
This independent fictional case uses Livia and a different task: an invented appointment-rescheduling flow. Her stipulated instructions allow editing the Candidate Flow frame and require the result to stay in the employer’s board. A separate Sandbox frame contains discarded alternatives; a Prompt frame contains the interviewer’s material.
At the end, Livia’s completed artifact decision is:
| Item | Recorded state | Final action |
|---|---|---|
| Candidate Flow | Final proposed flow plus unresolved edge-case note | Identify this frame for the interviewer’s review |
| Sandbox | Abandoned branch retained for discussion | Label it as discarded, not part of the final proposal |
| Prompt | Host-supplied material | Leave it unchanged and exclude it from any requested personal copy |
| Export | No employer authorization recorded | Do not export, duplicate or capture a substitute image |
| Personal portfolio | No reuse permission recorded | Keep this exercise out of the portfolio |
| Submission | Frame location ready to communicate | Ask the interviewer whether this completes the required handoff |
Her final unsent handoff reads:
My proposed flow is in Candidate Flow. The edge-case note there identifies the remaining question; Sandbox contains the alternative I discarded. I have left the prompt unchanged and have not exported or copied the board. Is the indicated frame the complete handoff you require, or is another authorized delivery step needed?
We executed an original finite offline record check for these examples. It preserves six readiness decisions and six handoff decisions, then rejects three deliberately false changes: interpreting successful editing as export permission, interpreting a locked prompt as permission to unlock it, and marking a prepared handoff as confirmed submission. No Miro board was created, edited, exported or tested by that script.
Livia’s result is a defined delivery state, not an interview score. The work remains where the stipulated instructions require, the intended final frame is identifiable, and confirmation is still pending. She has not invented an employer receipt, approval or permission to publish the exercise.
Leave with a clear next step
Before joining, retain the verified invitation, intended role and access level, permitted working area, needed tools and expected handoff. Resolve missing editing access with the host rather than changing its sharing model yourself. During the session, keep navigation, object modification and content copying as separate actions.
Before leaving, name the final frame and unresolved design questions, then ask whether the host requires another delivery step. Keep confirmation pending until it is actually received. Record export or portfolio permission only if it was actually given for that purpose. For your broader search, explore LandOffer.ai and prepare each employer’s workspace within that employer’s rules.


