# Panova Application documentation > Panova builds interactive image-based learning experiences, and delivers them through your LMS or a shareable link. Every public help article for Panova Application, in one file. Contents page: https://support.panova.app/llms.txt --- ## What Panova is, in one page *Getting started. Experiences, scenes and pins — the three ideas everything else is built on.* Source: https://support.panova.app/what-is-panova Panova turns photographs of real places into things people can explore and be assessed in. There are only three ideas to learn. ## Experience An **experience** is the whole thing you publish and share — a kitchen induction, a heritage trail, a room-setup check. It has a title, a set of scenes, and one link. It also has a **theme**: the colours and lettering a learner sees it in. Every experience already has one, so this is never something you have to do — see [Themes and branding](/support/articles/themes-and-branding) if you want to change it. ## Where an experience lives Every experience lives in a **workspace**, and every workspace belongs to your **organisation**. Signing up made you one of each, so both already exist before you build anything. - Your **organisation** is your school or institution. Billing and people live here, and nothing crosses from one organisation to another. - A **workspace** is a team, a department or a course inside it. Work is shared with the people in that workspace — so Year 4 and Year 5 can be two workspaces, or one. See [Organisations, workspaces and roles](/support/articles/organisations-workspaces-and-roles). ## Scene A **scene** is one image inside an experience. It can be a **360° spherical** photo that learners look around, or a **flat** image they pan and zoom. Neither is second best: both hold pins and both publish the same way. Most experiences are a handful of scenes. Your plan sets a ceiling on how many scenes one experience may hold, alongside the storage it uses — see [Plans, limits and usage](/support/articles/plans-limits-and-usage). Scenes carry more than the picture: a title overlay, an optional narration recording, an ambient sound bed, and a backdrop colour for the space around a flat image. ## Pin A **pin** is a point of interest on a scene. Click it and a panel opens with whatever you put inside — text, images, a quote, a checklist, a callout, a link to another scene, an embed. Pins are the content; scenes are just where they live. Pins are grouped into **contexts**, which learners can switch between — "Safety", "Service", "Front of house". Contexts belong to a scene, so scene 1 and scene 4 can organise their pins completely differently. > Each thing lives inside the one above it. A pin belongs to a scene, and a scene belongs to one experience — so moving an experience takes its scenes and pins with it. ## What comes next Once the content is right, you can layer **activities** on top — ask learners to find things, place things, sequence things, record evidence, or add their own pins. Then you **publish**, and hand out a link or put the experience in a page. You can look at your work the way a learner will at any point, with **Preview**. Nothing a learner can open exists at all until you publish. > The shortest complete path. Nothing a learner can open exists until step five. Start with [Build your first experience](/support/articles/build-your-first-experience). If you cannot find a screen something is on, [Find your way around Panova](/support/articles/find-your-way-around-panova) is the map. --- ## Build your first experience *Getting started. From an empty dashboard to something you can share, in about ten minutes.* Source: https://support.panova.app/build-your-first-experience ## 1. Create it On **My Experiences**, choose **New experience**. Give it a title — you can change it later — and it opens straight into the editor. ## 2. Add your first scene The editor's left rail is your scene list. Add a scene and give it an image. The picker offers five places to get one: your organisation's **Library**, an **Upload** from your own machine, Panova's drawn patterns, a **Stock** search if you have connected a provider, or a **URL**. You are also asked to describe the picture before you can confirm it — see [Choosing a picture, describing it and pointing it](/support/articles/choosing-and-describing-a-picture). If the photo is a 360° panorama, Panova will usually detect it. If it doesn't, set the projection yourself in the scene's settings — a spherical image shown flat looks stretched and wrong. ## 3. Drop some pins Turn the pin tool on first: in the **Pin tools** cluster at the top of the canvas, press the map-pin button. Right-clicking the picture does the same thing. The cursor becomes a cross-hair. Click on the image where you want a pin, and a small card opens asking for its label. The tool stays on, so the next click is the next pin. Press **Escape**, or right-click, when you have finished. A **Pin** panel opens on the right with everything about the pin you just placed. To write what a learner reads, press **Content panel preview** in that panel and then click a block on the card that appears — see [Placing and styling pins](/support/articles/placing-and-styling-pins). Pins land in the scene's default context. Once you have more than a handful, split them into contexts so learners can filter. ## 4. Preview as a learner Use **Preview** in the header. This is what a learner sees — no editor chrome, no hidden contexts. Preview early and often; it is the fastest way to catch a pin that made sense while you were placing it and doesn't when you arrive at it cold. ## 5. Publish **Publish** takes a snapshot of the draft and makes it the live version. Nothing a learner can reach changes until you press it — so you can edit a published experience all week without anyone seeing half-finished work. If Publish refuses, a picture somewhere has no description. **Readiness** in the header lists them and takes you to each one. > Publishing takes a copy. Editing afterwards changes your draft and nothing a learner is holding, until you publish again. ## 6. Share it The header's **Share** dialog holds two different addresses, and the difference matters: - the **Link** is for people who already have an account in your organisation, and it is the only one that records anything; - the **Embed code** puts the experience inside another web page and opens for anyone at all, recording nothing. Neither of them is a public link you can send to a class of children who have no accounts. Read [Getting a class into your experience](/support/articles/getting-a-class-in) before you hand anything out — it is short, and it says which of the two is right for a school. If you are using an LMS, see [Connecting your LMS with LTI 1.3](/support/articles/connecting-your-lms-lti). --- ## Find your way around the editor *Getting started. What each part of the editor does, and where to look for the thing you want.* Source: https://support.panova.app/find-your-way-around-the-editor The editor has four regions. One word first, because it is used throughout: a **node** is one step in the experience — a scene, a cover, or a page. They are all nodes because learners walk through them the same way and the editor counts them together. Where this article says "node", read "scene" if scenes are all you have made. ## The header A block across the top of the screen: the section it belongs to, the title at a readable size, a line of counts, and the controls down the right — **Preview**, **Publish**, **Share**, **Theme**, **Readiness**, the two undo arrows, and an overflow menu for duplicate, version history and delete. **Readiness** is the one to know about. It lists what is unfinished, and publishing is refused while any picture has no description — see [Readiness: what has to be finished before you publish](/support/articles/readiness-before-you-publish). **Theme** picks the colours and lettering learners see this experience in — see [Themes and branding](/support/articles/themes-and-branding). The counts line says how many **nodes** the experience holds rather than how many scenes, because a cover and a page are nodes too. The **"?"** here opens help for whichever panel you are in. ## More room to work in The expand button, at the top right beside **Preview**, withdraws the app's own menu and topbar and gives the space to the editor. Nothing else moves, and the button stays where it was — press it again, or press **Escape**, to bring them back. It is not remembered between visits. Full screen is something you do for a stretch of work rather than a preference, and an editor that opened with the rest of Panova already hidden would be a worse trade. ## The node rail (left) **Experience nodes** in order — your scenes, and the covers and pages that sit among them. Drag to reorder; the order is what learners walk through, and what "Order the sequence" scrambles. Select one to edit it. See [Experience nodes: scenes, covers and pages](/support/articles/experience-nodes-scenes-and-covers). ## The canvas (middle) The scene itself. Above it sits **Pin tools**: an arrow for selecting, and a map-pin button that turns pin placing on. With the pin tool on, each click on the picture places a pin; with it off, clicking does nothing but clear your selection. Drag a pin to move it. For a 360° scene, drag to look around; the position you leave it in is not the learner's starting view unless you set it as such. Hold **Shift** to select several pins at once — then edit their context, style or visibility in one go. ## The right panel Changes with what you have selected: - **Nothing selected** — the experience's own tabs, described below. - **A scene selected** — backdrop, projection, title overlay, audio, contributions. - **A pin selected** — its label, blocks, display style and context. > Four working areas. The middle is the only one a learner ever sees. ## The experience tabs, one line each A row along the top of the editor, above everything else. The first five sit together on the left; **Link Manager** and **Experience Settings** are pushed over to the right-hand end, because they are tools *for* the experience rather than parts of it. - **Design** — the working view this article has been describing: the node rail, the canvas and the panel beside it. This is where you build. - **Properties** — the experience's name, its icon and colour, and the overlay a learner meets before the first scene. - **Interactivity** — the activities that run across the whole experience, and the rules for each. Activities that run on a single scene are set on that scene instead. - **Review** — where learner work lands: what has been handed in, and the versions learners built for themselves. - **Insights** — where learners get stuck, how far they get, and whether the experience is reachable for everyone. - **Link Manager** — every web address anywhere in the experience, and whether it still works. - **Experience Settings** — four sub-tabs of its own: - **General** — publishing state, the direct link, how learners move between scenes, and the default look of pins. - **About** — the short summary a learner reads before starting. - **Team** — the colleagues you have named on this one experience. - **Danger** — one control: delete this experience. It goes to the **Bin** first, so it can be restored. ## Saving There is no save button — edits are written as you make them, to the **draft**, and the header tells you when the draft has moved ahead of the published version. Because nothing is saved by hand, there is an **Undo**: two arrows in the header, and **Ctrl+Z**. See [Undo a change in the editor](/support/articles/undo-a-change-in-the-editor). --- ## 360° or flat: which to use *Scenes & images. How the two projections behave, and how to avoid the stretched-image problem.* Source: https://support.panova.app/choosing-360-or-flat ## Flat Use this for ordinary photographs, floor plans, diagrams and screenshots. Learners pan and zoom within the image. Pins are anchored to a point on the picture. **A good flat photograph is not second best.** It holds pins the same way, publishes the same way, and carries an activity the same way — a picture taken on your phone of the classroom, the playground or a page of a Victorian schoolbook works exactly as well as a panorama for most of what people build. Choose 360° when *being in the space* is the point, and flat the rest of the time. Flat images rarely fill the viewport, so the space around them is painted with the scene's **backdrop colour**. Set it to something that belongs with the image — a dark neutral behind a photograph, white behind a plan. ## 360° spherical Use this for **equirectangular** photos — the very wide 2:1 images a 360° camera produces. Learners drag to look around and can pan a full circle. Pins are anchored to a direction, so they stay put as the view moves. A spherical image must be a true equirectangular capture. A wide panorama stitched from a phone is usually *not*, and will look bowed. If you want one and have no camera, there are three places to look: borrow or hire one for a day, search the **Stock** tab (some providers carry equirectangular images, though far fewer than flat ones), or ask whether anyone else in your organisation has already put one in the asset library. If none of those works out, use a flat photograph. You lose nothing that matters. > Both hold pins and both publish the same way. The difference is only what the picture is. ## Getting it wrong is obvious A spherical image shown flat looks stretched at the top and bottom. A flat image shown spherical bows in the middle and can be spun past its own edge. If a scene looks odd, check the projection first. ## Image size Upload the best version you have. Panova re-encodes an image once, as it arrives, and keeps a scene backdrop at up to 4096px wide on the default quality setting — sharp across a 360° view without storing detail nobody will ever see. The original is not kept, so this is a one-way trip. Keep your masters somewhere else, and do not shrink a panorama before uploading it: see [What happens to an image when you upload it](/support/articles/what-happens-to-an-uploaded-image). --- ## Narration and ambient sound *Scenes & images. Two separate audio tracks per scene, and when each is worth adding.* Source: https://support.panova.app/scene-audio-narration-and-ambience A scene can carry two independent audio tracks. ## Narration A spoken introduction to the scene. Record it in the browser or upload a file. It plays once when the learner arrives and can be replayed from the scene's controls. Narration is the single most effective addition to a scene that is otherwise a wall of pins: thirty seconds of "here is what you are looking at, and what I want you to notice" orients someone far better than a paragraph they have to find first. ## Ambient sound A looping background bed — kitchen noise, a busy lobby, birdsong. It sets the scene's atmosphere and is deliberately quieter than narration. Use it sparingly. Ambient audio that plays under an assessment is a distraction, and learners on shared devices may not be able to turn it down. ## Accessibility Anything said only in audio is unavailable to some of your learners. Write the narration a **transcript**: a learner can then open it from the scene and turn the sound off, which is what makes it a real alternative rather than a note to yourself. See [Recording narration, and writing its transcript](/support/articles/recording-narration-and-transcripts). If the narration carries instructions, it is still worth repeating them in a pin, where they can be found without playing anything. --- ## Scene order and how learners move between scenes *Scenes & images. Reordering, jump links, and the difference between the two.* Source: https://support.panova.app/scene-order-and-navigation ## The rail order The order of scenes in the left rail is the order learners walk through with next/previous. Drag to change it. This order is load-bearing for one activity: **Order the sequence** hands learners your scenes shuffled and asks them to put them back, marking against the rail order. If you reorder scenes after learners have attempted it, earlier attempts were marked against the old answer — say so, or reset the activity. ## Jump links A pin can link to another scene. That is how you build spatial navigation: a pin on the doorway of the lobby scene that jumps to the corridor scene. Learners follow the space rather than a list. Jump links are what **Wayfinding challenge** uses. If you plan to use that activity, build the links as a real map of the building rather than a convenience shortcut, or the "shortest path" it measures against will not mean anything. ## The cover The cover is what a learner sees before they enter. Give it a title, a short description and an image that makes it obvious what this is. --- ## Placing and styling pins *Pins & contexts. Getting pins in the right place, and making them readable against the image.* Source: https://support.panova.app/placing-and-styling-pins ## Placing a pin Clicking the picture does not place a pin on its own. Turn the pin tool on first, then click. **Pin tools** sits at the top of the canvas: an arrow for selecting, and a map-pin button that turns pin placing on. Press the map-pin button, or **right-click anywhere on the picture**, and the cursor becomes a cross-hair. Now each click on the image drops a pin and opens a small card asking for its label. The tool is *sticky*: it stays on until you turn it off, so a run of pins is a run of clicks rather than a trip back to the toolbar between each one. **Escape**, or another right-click, turns it off again — first closing the label card if one is open, then the tool. Drag an existing pin to move it. On a 360° scene, look around first and place the pin while you are facing the thing it refers to — the pin is anchored to that direction. ## Opening a pin to write in it Selecting a pin opens the **Pin** panel on the right: its label, colour, size and context. That panel is about the marker. What a learner *reads* lives somewhere else, and it takes one more press. In the Pin panel, under **Content**, choose **Content panel preview**. The pin's card floats over the scene, exactly as a learner gets it, at the width they get it. Then, to write: - **click any block on that card** — a paragraph, a picture, a callout — and the block editor opens beside it, with that block selected; - on a pin with nothing in it yet there are no blocks to click, so the card offers **Add a block** instead. There is no separate Edit button, and that is deliberate: clicking the thing you want to change says which one, where a button could not. The two panels are separate on purpose. The preview answers *what does a learner see*; the editor answers *how do I change it*. Closing the preview closes both. The scene underneath never moves or narrows while they are open, so a pin you place after closing them lands where you clicked. ## Styling Each pin has a colour and a display style. Use colour with intent: if every pin in a scene is a different colour, the colour has stopped carrying information. A common pattern is one colour per context. Pins can also be numbered. Numbers are assigned in order and close up automatically if you delete one, so there is never a gap in the sequence a learner sees. ## Editing several at once Hold **Shift** and click to select multiple pins, or drag a selection box. With several selected you can change their context, colour or visibility together, or delete them in one action. This is much faster than fixing twenty pins one at a time after you decide the scheme was wrong. ## What goes inside a pin Pins hold blocks: text, headings, images, video, audio, galleries, compare, reveal, quotes, checklists, callouts, banners, buttons, stats, key facts, dividers, spacers, embeds, resource lists, accordions and scene links. Add what the point needs and stop — a pin the learner has to scroll through twice is usually two pins. The one block a pin cannot hold is a **menu**. A menu is a way around a page, and a pin is somewhere you have already arrived. It is the same block editor a page node and a scene use, so a block behaves the same wherever you built it. Two things about working in it are worth knowing. **Deleting a block asks first.** It names the kind of block and says the delete cannot be undone, because on a pin the blocks *are* the content and nothing puts one back — see [Undo a change in the editor](/support/articles/undo-a-change-in-the-editor). **Pasting into a text block keeps its formatting.** Bold, italics, bullet and numbered lists and links all survive a paste out of a document or a web page, so you no longer have to redo by hand what you had just brought in. Everything else is reduced to plain words on the way in. ## A link pin, and where it opens A pin can be a **link** to an address outside the experience. It opens in a new tab by default, which is usually right — but a link into another page of the same course, or a form the learner is meant to finish and come back from, reads better in the window they are already in, and the pin can now say which. ## If you built something before 27 August 2026 ⚠️ **Pins written before then have been repaired.** A pin used to have a plain **description** box and a single picture of its own, and neither was ever shown to a learner — a pin whose only content was that box did not open at all. Both have been moved into real blocks inside the pin, so that content now appears. **It is worth opening an experience you built before then and reading its pins**, because some of them are showing text a class never saw. If you signed up after that date, this cannot affect anything you have made. --- ## Organising pins into contexts *Pins & contexts. Contexts are per-scene layers learners can switch between — and some are yours alone.* Source: https://support.panova.app/organising-pins-into-contexts A **context** is a named group of pins within one scene. Learners can switch contexts to filter what they see — "Safety", "Service", "Equipment". ## Contexts belong to a scene Each scene has its own set. A kitchen scene can be organised by hazard type while the dining room scene is organised by service stage; they do not have to agree. Every scene starts with one default context, so you only think about this when you need to. > A context is a group of pins on one scene. Learners use it to show one group at a time — so contexts are how you say "now look at the wiring, not the plumbing". ## Making one while you are placing a pin You do not have to leave what you are doing. The popover that opens when you drop a new pin can create a context there and then, and the pin lands in it — so realising half-way through a scene that these five pins are really a group of their own costs you nothing. ## Hidden contexts A context can be marked **author-only**. Its pins are visible to you in the editor and invisible to learners — and they are *excluded when the experience is published*, not merely hidden afterwards. Nothing in a hidden context is reachable by a learner who knows where to look, which is what makes them safe for staging notes, answer keys and work-in-progress. Pin numbering closes the gap: if pins 3 and 4 are hidden, learners see an unbroken 1, 2, 3. ## Deleting a context Deleting a context asks what to do with its pins — move them to another context, or delete them with it. It will not silently orphan them. ## Contexts and activities **Sort into contexts** hands learners your pins and asks them to file each one correctly. If you plan to use it, make the contexts genuinely distinguishable — a sorting task where two categories overlap is a test of guessing. --- ## Choosing an activity *Activities & assessment. All ten activities, what each one asks of a learner, and what you get back.* Source: https://support.panova.app/choosing-an-activity Activities sit on top of content you have already built. They fall into four groups. ## Create & observe | Activity | Asks the learner to | You get back | | --- | --- | --- | | **Student versions** | Build a version of their own, with their pins over yours | Every version, side by side | | **Field notes** | Drop observation pins into your scenes | Each note, by learner and scene | | **Evidence at a pin** | Record audio or upload a photo at a location | Clips and photos, per pin | ## Place & recall | Activity | Asks the learner to | You get back | | --- | --- | --- | | **Pin the space** | Reproduce your pins from memory (three difficulties) | Placement accuracy | | **Scavenger hunt** | Pan the scene and click to find your answer | Hits and misses per prompt | | **Wayfinding challenge** | Navigate from A to B using jump links | Route taken vs shortest path | ## Sort & sequence | Activity | Asks the learner to | You get back | | --- | --- | --- | | **Sort into contexts** | File each pin into the context it belongs to | Correct and incorrect assignments | | **Order the sequence** | Put your scenes back into the right order | The order each learner submits | ## Judge & decide | Activity | Asks the learner to | You get back | | --- | --- | --- | | **Spot the issue** | Flag what is wrong in a staged scene | Issues found vs issues planted | | **Branching scenario** | Make decisions that lead to different outcomes | The path each learner chose | ## Letting learners add pins is not one of these Opening a scene for **contributions** is a setting on that scene rather than an activity you place. It is not scored and it produces no attempt, which is why it is not in the tables above. See [Letting learners add their own pins](/support/articles/letting-learners-add-pins). ## Say what you are asking for **Prompt to students**, at the top of the **Interactivity** tab, is one brief for the whole experience. Four of these activities put it in front of a learner before they start. See [The prompt you give a class](/support/articles/the-prompt-to-students). ## Picking one Match the activity to what you actually want to know. "Can they find it?" is a scavenger hunt. "Do they know where it goes?" is Pin the space. "Can they tell good from bad?" is Spot the issue. "Will they make the right call under pressure?" is a branching scenario. Adding three activities to one experience rarely triples what you learn, and it does triple the time it takes a learner to get through. --- ## Placements: where an activity runs *Activities & assessment. Why some activities attach to a scene and others to the whole experience — and why you cannot mix.* Source: https://support.panova.app/how-placements-work When you switch an activity on, Panova records a **placement**: the activity, where it runs, and the rules you set for it. ## Scene-level activities Field notes, Evidence at a pin, Scavenger hunt, Sort into contexts, Spot the issue and Pin the space run on **individual scenes**. The same activity on two scenes is **two independent placements**. Each has its own attempt limit, its own scoring rule, and its own attempts. A learner's work on scene 3 has nothing to do with their work on scene 7. That is deliberate — a scavenger hunt in the kitchen and one in the cellar are different tasks. ## Whole-experience activities Student versions, Order the sequence, Wayfinding challenge and Branching scenario bundle **every scene into one activity**. There is exactly one attempt per learner per experience, because the task only makes sense across the whole thing — you cannot sequence scenes "within scene 4". ## They do not mix An experience holds **either** one whole-experience activity **or** any number of scene-level ones. Never both. This is not an arbitrary restriction. A whole-experience activity already claims every scene; adding a scene-level one on top would give the same scene two different owners with two different sets of attempts, and no honest way to combine them into a grade. > An experience holds either one whole-experience activity or any number of scene ones — never both. Each placement keeps its own rules and its own attempts. ## Copying an experience Duplicating an experience copies its placements and their rules, not just the fact that an activity was on. The copy behaves the same way from the first learner. --- ## Attempts, scoring and grades *Activities & assessment. Attempt limits, the four scoring rules, and how a whole experience becomes one grade.* Source: https://support.panova.app/attempts-and-scoring ## Attempts Each placement has an attempt allowance. Leave it unlimited, or set a number. A learner who has attempts left can resume an unfinished one or start the next; a learner who has used them all sees their result and cannot start again. Nothing deletes an attempt except deleting the whole experience permanently. There is no "clear this learner's attempt" button, on purpose: an assessment record you can quietly erase is not a record. ## Scoring rules When a learner has several attempts at one placement, the rule decides which one counts: - **Highest** — their best. Rewards persistence. The usual choice for practice. - **Latest** — their most recent. Rewards improvement, and is honest about where they have got to. - **First** — one shot that counts. For a genuine check. - **Mean** — the average. Smooths out a fluke either way. ## Showing history You can let learners see their own previous attempts, or not. Showing history helps with practice; hiding it is usually right when the first attempt is the one that counts. > What happens to one learner on one placement. Nothing deletes an attempt, so a record of what they did stays put. ## One experience, one grade An experience produces a **single 0–1 result**, whatever is inside it. It is the average across every placement you made. An activity a learner never attempted scores **zero** — it is part of what you asked for, so ignoring it would flatter the result. Each placement is first reduced to one number by its own scoring rule, then those are averaged. Some activities record a score out of a maximum; some record only that the learner completed them. An activity with no score is judged on completion. Progress stays **Started** until every placement has been submitted, and the grade is posted once, at the end. If that grade is refused by your LMS, the workspace's leaders and the organisation's admins get a notification saying so — see [Connecting your LMS with LTI 1.3](/support/articles/connecting-your-lms-lti). --- ## Letting learners add their own pins *Learner contributions. Open a scene for contributions, and choose when peers see them and whose name is on them.* Source: https://support.panova.app/letting-learners-add-pins A **contributory scene** lets learners pin the image themselves and see each other's work. You set the rules per scene. ## Turning it on Select a scene, then **Let students add pins** in the right panel. Write a prompt while you are there — "Add a pin where you notice something worth sharing" is better than an empty canvas, and much better than no instruction at all. ## When the class sees a contribution - **I approve each one** — nothing appears to the class until you say so. Slower, and the right default for a group you do not know yet. - **Show it straight away** — appears for everyone the moment it is saved. Better for live sessions, where a queue kills the momentum. > You set this per scene. Whichever you pick, staff always see who wrote what. ## Whose name the class sees - **Their own name** — classmates see who added each pin. - **A nickname** — classmates see a consistent, generated nickname instead. Two things about nicknames matter: 1. **The nickname is stable.** "Amber Fox" is the same person on Monday and on Friday, so a conversation can refer back to what someone said. It is stored, not recalculated. 2. **It is peer-facing only.** You and your colleagues always see the real name. You cannot responsibly moderate work you cannot attribute, and the promise made to learners is only that their *classmates* will not know — which is exactly what the interface tells them. > Anonymous means anonymous to other learners, never to you. A learner keeps the same made-up name all the way through one experience. ## Reviewing **Review contributions** lists everything submitted, with the real author, ready to approve, hide or remove. The scene's panel shows a count when something is waiting. ## Contributions and publishing Contributions are live learner data, not part of the published snapshot. Publishing a new version does not disturb them, and they do not appear in an exported or embedded copy of the content. --- ## Drafts, publishing and versions *Publishing & sharing. Why editing is always safe, and what Publish actually does.* Source: https://support.panova.app/drafts-and-publishing ## Only Publish changes what a learner sees Everything you do in the editor writes to the **draft**. Learners never see the draft. You can restructure an experience over a week, mid-term, while a class is using it, and nothing they open changes until you press **Publish**. The header tells you when the draft has moved ahead of what is live. ## What Publish does Publishing takes a complete snapshot of the draft — scenes, pins, contexts, blocks, links, activity setup, theme — and stores it as a new **version**, numbered 1, 2, 3 and so on. A version is **immutable**. Publishing again does not modify version 2; it creates version 3. Nothing edits a version after the fact. Author-only contexts and their pins are left out at this point, rather than hidden later — so they are not in the published document at all. ## Version history The status chip in the editor header opens version history: every version, when it was published and by whom, with a link to each one and the controls to preview it, serve it, copy it to a new experience or restore it over your draft. See [Version history: preview, serve and restore](/support/articles/version-history-preview-serve-restore). ## Stay live, or Freeze In the **Share** dialog, under **When the experience changes**, there are two cards: - **Stay live** — everybody is served your newest published version. Publish a fix and every reader picks it up. This is how a new experience starts. - **Freeze** — everybody is held on one named version, for as long as you leave it there. ⚠️ **Freeze holds the whole experience, not only the embed.** It is the one setting people expect to apply to one thing and it applies to everything: the embed *and* the link you have already given your class. Publish a correction afterwards and none of them receives it. If what you want is one group held on one version while everyone else moves on, do not use Freeze — give that group the version's own link instead. See [Sending a class to one version](/support/articles/sending-a-class-to-one-version). A freeze names a version, not a file, so it survives everything — including deleting the experience and restoring it from the Bin. ## Anyone can open the embed, unless you turn it off Publishing also makes the experience available at a second address, the **embed** — and that one opens for anybody who has the address, with no account and no sign-in. It is switched on for every experience unless you go and switch it off, in the same **Share** dialog under **Allow embedding**. That is worth a moment's thought before you publish photographs taken inside a classroom. Turning **Allow embedding** off changes nothing for your own class, who use the link. See [Embedding an experience in a page](/support/articles/embedding-in-a-web-page). ## Attempts remember which version Every attempt records the version it was taken against, so a result from March can still be read against the content that existed in March. --- ## Sharing a link and embedding *Publishing & sharing. Public links, iframe embeds, and what each one exposes.* Source: https://support.panova.app/sharing-and-embedding ## The share link A published experience has a link of its own — the address the **Share** dialog copies. It always serves your latest published version. **It is not a public link.** Whoever opens it has to be signed in, have confirmed their email address, and belong to your organisation. Somebody outside your organisation who is handed the link gets "not found" rather than a sign-in prompt. That is the right behaviour for anything that records work, because an attempt has to belong to somebody. The token in the link is unguessable, but it is an address rather than a password — the gate is what keeps strangers out. ⚠️ **So this is not the link to send to a class who have no accounts.** Getting learners in is its own question, with three answers and no painless one: read [Getting a class into your experience](/support/articles/getting-a-class-in) before you hand anything out. If you need an address that works with no account at all, that is the embed, and it comes with a real trade: see [Embedding an experience in a page](/support/articles/embedding-in-a-web-page). ## Embedding **Embed** gives you an iframe snippet for a web page, intranet or course tool. ⚠️ **An embed is a different address from your share link, and nothing a learner does inside it is recorded** — no activities, no attempts, no contributions. Do not embed a task you intend to mark. Read [Embedding an experience in a page](/support/articles/embedding-in-a-web-page) first. An embed moves with every future publish. If one group has to stay on one version, give them that version's own link rather than freezing the experience for everybody — see [Sending a class to one version](/support/articles/sending-a-class-to-one-version). Embeds need a reasonable amount of height. A 360° scene in a 300px-tall frame is unusable; give it at least 500px, more if the page allows. ## Unpublishing Unpublishing takes the experience out of circulation. Existing links and embeds stop resolving. Attempts already recorded are untouched. --- ## The Bin: deleting and restoring *Publishing & sharing. Deleted experiences are recoverable — for a window your organisation sets.* Source: https://support.panova.app/the-bin-and-restoring Deleting an experience moves it to the **Bin** rather than destroying it. From there you can restore it whole — scenes, pins, contexts, versions and all. ## Files go there too Deleting a picture, a video or a sound from the asset library bins it the same way, and restoring puts it back in your library with its file. Deleting one used to take the file off the disk in the same action, and since an upload is re-encoded on the way in and the original is not kept, that was the only copy of it anywhere. The two halves of the Bin are scoped differently, and the page says so: **experiences belong to the workspace you are in**, so another workspace's deletions are in its own bin, while **files belong to your organisation's library** and are all in one place. A binned file does not count towards your storage while it waits. ## Nodes go there too Deleting a **scene**, a **cover** or a **page** bins it as well, and restoring puts it back with everything that was on it — its pins, the content on those pins, its own blocks, its pin groups and the links other nodes made to it. Nodes are listed under their own heading, each naming the experience it came from, because "North wall" on its own is not something anybody recognises. > Only whole experiences and library files reach the Bin. Everything smaller is deleted there and then, and version history is the only way back. ## ⚠️ Pins and blocks are a different way back A **pin**, a **block** or a **pin group** does not appear in the Bin, and that is not because it is gone. Press **Ctrl+Z** in the editor and it comes back — a pin with its content, a group with the pins that were in it. See [Undo a change in the editor](/support/articles/undo-a-change-in-the-editor). The difference is where you would look. A pin you deleted a moment ago is an editing mistake, so the answer is in the editor; a node or an experience is something you might notice tomorrow, so the answer is a page that is still there tomorrow. ⚠️ **Undo does not survive the tab.** Close the editor, or open a different node, and both arrows empty. If you deleted a pin yesterday, the way back is restoring a version you published before you deleted it — which replaces the whole draft, so it is a heavy answer to a small problem. **Publish early**, even a half-finished experience nobody has the link to, and you always have one. ## How long it stays Your organisation has a retention window. It can be a number of days, or "keep indefinitely". Once the window passes, a nightly job removes binned experiences permanently, along with their published files. The window is set for your organisation by Panova rather than on your own settings screen, so ask us if you need it changed — this is not a control you will find on your settings page, even as an organisation admin. Where nothing has been set for you, the platform default applies. ## What restore brings back Restoring returns exactly what deleting took, and nothing else. An experience comes back with everything that was inside it when it went in, and a node with everything that was on it. Anything you had already deleted separately, before you binned the thing above it, was gone at that point and does not return with it — a pin you removed and then a node you removed are two decisions, and restoring the node only undoes the second. ⚠️ **A node whose experience is also in the Bin is not listed.** Restore the experience first and its nodes come back on it; putting a node back into a deleted experience would give you something nothing can open. ## Permanent deletion Deleting from the Bin is final. There is no second bin, and for a file it is the point at which the bytes go. If you have emptied it by mistake, tell us the same day. --- ## Organisations, workspaces and roles *People & workspaces. How access is structured, and what each role can do.* Source: https://support.panova.app/organisations-workspaces-and-roles ## The shape An **organisation** is the account — the thing that is billed, and the boundary nothing crosses. Inside it are **workspaces**: teams, departments, campuses, properties. Experiences live in a workspace. ## The roles Each is cumulative — every role can do everything the one below it can. | Role | Can | | --- | --- | | **Free** | Build and publish their own experiences | | **Individual** | The above, plus the asset library and themes | | **Workspace Member** | Work on the shared experiences in their workspace | | **Workspace Leader** | Manage their workspace's members, learners and settings | | **Organisation Admin** | Manage every workspace, billing, integrations and org settings | Someone can be a leader in one workspace and a member in another. Their access is worked out per workspace, not once for the account. > Each rung can do everything the rungs below it can. Somebody can be a leader in one workspace and a member in another, so the rung is worked out per workspace rather than once for the account. ## Learners are not a role Learners are a different kind of membership, not a rung on this ladder. A learner does not get "less than a member" — they get a different surface entirely. Promoting a learner to a member is a deliberate change, not an increment. That is why a learner never appears on **Members**, and why nobody on **Students** has a role beside their name. See [The learner roster](/support/articles/the-learner-roster). ## What you cannot reach, you cannot see An experience in a workspace you have no access to does not appear as a locked row. It is not there at all. That is intentional: telling you something exists is itself information. --- ## Inviting colleagues and learners *People & workspaces. How invitations work, what happens if one is not accepted, and how to withdraw it.* Source: https://support.panova.app/inviting-people ## Sending an invitation From **Members**, invite by email address. They receive a link; accepting it creates their account or joins their existing one to your organisation. **An invitation no longer sets a role.** Everybody arrives as a member, and you set their role on **Members** once they have accepted. An email address is not yet a person, so a rung granted before anyone accepts is a rung a mistyped address could use. An invitation is not access. Nothing changes for them until they accept. Each accepted invitation takes one of your plan's **staff member** places, and an invitation is refused once they are used up — see [Plans, limits and usage](/support/articles/plans-limits-and-usage). > An invitation lets somebody in. It does not decide what they may do — you set that after they arrive. ## Pending invitations Pending invitations are listed with the option to **resend** or **withdraw**. Withdrawing invalidates the link immediately — do this rather than hoping an invitation sent to the wrong address is ignored. ## Learners are not invited ⚠️ **There is no invitation for a learner, and the Students screen has no button that adds one.** Invitations are for colleagues: somebody accepting one becomes a member of your organisation with a role, which is not what a learner is. A learner arrives one of two ways — by opening your experience and doing something in it, or by being on the class list of an LMS course you have placed an experience in. Both put them on **Students** on their own. See [The learner roster](/support/articles/the-learner-roster). Naming a learner in advance, without an LMS, is not something Panova can do yet. If what you are trying to do is get a class into an experience, read [Getting a class into your experience](/support/articles/getting-a-class-in) first — inviting thirty children one email address at a time is usually the wrong answer, and that page says what the alternatives cost. ## Removing someone Removing a person from a workspace takes their access with immediate effect. Their contributions and attempts stay: they are a record of what happened, not a possession. --- ## Connecting your LMS with LTI 1.3 *Connecting your LMS. Register Panova as a tool, place an experience in a course, and send grades back.* Source: https://support.panova.app/connecting-your-lms-lti Panova is an LTI 1.3 tool. Once registered, instructors place experiences directly into courses and results flow back automatically. ## Registering Two routes, from **Organisation → Integrations**: - **Dynamic registration** — paste Panova's registration URL into your LMS and it exchanges the details itself. Supported by Canvas, Moodle and Blackboard among others, and much less error-prone. - **Manual** — copy Panova's client id, keyset URL, login and launch URLs into your LMS, and paste six values back: its **issuer**, **client id** and **deployment id**, and its **authorisation**, **token** and **key set** addresses. Use this if your LMS does not support dynamic registration. Each registration is scoped to your organisation. Two organisations can connect the same LMS independently without seeing each other's content. > Connecting is done once per LMS. After that a teacher adds an experience to a course without coming back here. ## Placing an experience in a course In the course, add an external tool and choose Panova. The **content picker** opens with the experiences that workspace can reach; choose one and it is attached to that assignment. The course link then follows every future publish. Where a cohort must be assessed against identical content, give them a version's own link instead of the plain one — see [Sending a class to one version](/support/articles/sending-a-class-to-one-version). There is no live-or-frozen choice in the content picker itself; that setting lives in the **Share** dialog and applies to everybody at once. ## Grades If the assignment is graded, Panova posts a result back when the learner has completed everything you placed — one grade per experience, as a 0–1 ratio your LMS scales to its own points. Progress shows as **Started** until every activity has been submitted. ## If a grade is refused, somebody is told A gradebook column that never fills in used to be found by a student asking why they had no mark. Now, when the platform refuses a result — a revoked permission, a line item that has been removed, a deployment that has expired — the workspace's leaders and the organisation's admins get a notification naming the learner and the experience. The learner's work is safe either way; it is only the gradebook entry that is missing. Fix the connection and re-check the column. You get **one** line per failure, not one per learner: a broken connection fails for the whole class, and thirty copies of one fact make it unreadable. Once you have marked the line as read, the next failure tells you again — which is what you want, because it means the thing you went and fixed is still broken. ## If a launch fails A launch that cannot be verified shows an explicit error rather than a login page. The usual causes are a clock skew between the two systems, a stale keyset, or a registration pointing at a different environment. Two refusals are deliberate and are worth telling apart from a fault. **A disconnected LMS cannot launch**: pressing **Disconnect** on the Integrations screen ends every launch from that platform, and a course still pointing at Panova gets an error rather than a lesson. And **a plan that no longer includes LTI cannot launch either**, whatever was registered while it did. ## Availability LTI is included on Professional and Enterprise plans. --- ## Themes and branding *Account, themes & billing. Applying your own colours and type, and checking they stay readable.* Source: https://support.panova.app/themes-and-branding A **theme** controls how a published experience looks to learners — colours, type and accent. Build themes once and apply them to any experience. ## Contrast The theme editor includes a contrast checker. Use it. An accent that looks smart on your monitor can be unreadable on a phone in a kitchen, and text that fails contrast is text some of your learners cannot read at all. ## Light and dark Learners can view in either. Check both — a colour that sits well on white can vanish on a dark background. ## Availability Custom themes are included from the Growth plan upwards. --- ## The asset library and stock images *Account, themes & billing. Reuse images across experiences, and connect your own stock-photo account.* Source: https://support.panova.app/asset-library-and-stock-images ## The asset library An image uploaded once can be reused in any experience you can reach, rather than uploaded again each time — the same photograph in four experiences costs four times the storage against your plan. Every upload is filed at a sharing level: your own files, the workspace's shared library, the whole organisation, or Panova's own stock. See [Sharing assets with your team](/support/articles/sharing-assets-with-your-team). ## Adding files The button above the shelf names where a file will land — **Upload to Workspace**, **Upload to Organisation**. Choose the library first, then upload. **You can choose several at once**, or drop a handful onto the panel. They go up one after another rather than all together, and the dialog counts through them — *Uploading 2 of 5*. Anything refused is left out and the rest still land, so one bad file in a folder of ten does not cost you the other nine. A set arrives undescribed, because nobody has been asked what five pictures show. Add the descriptions afterwards from the library. ## Stock images Panova can search Pexels, Unsplash and Pixabay from inside the image picker, Pexels, Pixabay and Coverr for video, and Freesound from inside the audio picker. This uses **your own** provider key, added on **Account → Integrations**, so the usage and the terms are yours. Keys are stored encrypted and used only on your behalf. A key is free from all five, but read what each one commits you to first — a new Unsplash key is rate-limited until Unsplash approves it, and that takes them about five working days. See [Connecting a stock photo or sound provider](/support/articles/connecting-a-stock-provider). ## Storage Storage counts against your plan. **Organisation → Usage** shows what is being used and by which workspace. --- ## Plans, limits and usage *Account, themes & billing. What each plan includes, what happens at a limit, and where to see your numbers.* Source: https://support.panova.app/plans-limits-and-usage ## Where your own numbers are This article cannot print them, and deliberately does not try: the plans are rows a super admin can edit, so a figure written here would be out of date by the next release. Two screens hold the real ones, and they are the only ones to trust. - **Organisation → Billing** names the plan you are on, lists every plan beside it with what each includes, and shows the four numbers you are measured against. - **Organisation → Usage** shows what you are currently consuming against each of those numbers, broken down by workspace. If you are on a personal account rather than a school's, both are still yours — a single-seat account can reach the page it upgrades from. ## What is limited Plans cap six things: published experiences, storage, active learners, staff members, workspaces, and scenes per experience. - **Published experiences** — how many may be live at once. Drafts are never counted; unpublishing one frees a place immediately. - **Storage** — the size of everything in your asset library. A binned file does not count while it waits. - **Active learners** — people who have done something in the last twelve months. - **Staff members** — colleagues who hold an account in your organisation. ⚠️ **An invitation is checked against this one**, and the entry plans include very few, so this is not a way to give a class of children accounts. See [Getting a class into your experience](/support/articles/getting-a-class-in). - **Workspaces**, and **scenes per experience**. ## What the higher plans unlock Five things, and here is what each one actually is: - **Branching scenarios** — an experience where the learner's choice decides what happens next, rather than everyone walking the same path. Good for a decision you want people to practise making. See [Authoring a branching scenario](/support/articles/authoring-a-branching-scenario). - **Custom themes** — your own colours and lettering on a published experience, instead of the ones Panova ships. See [Themes and branding](/support/articles/themes-and-branding). - **LTI 1.3 launch** — the standard that lets a learning management system (Canvas, Moodle, Blackboard and others) put an experience inside a course. Learners open it from the course, and their marks go back to its gradebook. It is the only route that does both without anybody typing a register. See [Connecting your LMS with LTI 1.3](/support/articles/connecting-your-lms-lti). - **Data access** — two ways for other software to read your Panova data: an **API**, which a developer can call from a script or a dashboard, and an **MCP server**, which lets an AI assistant answer questions about your content. Neither is anything you need in order to teach. See [Data access: the API and the MCP server](/support/articles/data-access-api-and-mcp). - **Priority support** — a named person on our side. ## At a limit Reaching a limit stops the action that would exceed it and says so — it does not delete anything or silently unpublish. Drafts are never capped; only publishing is. Publishing an experience that is already live is never refused, because it is not taking a new place. **Active learners are the exception.** That figure is measured and reported, and it never blocks anybody. Stopping somebody in the middle of an assessment over their institution's billing is the wrong person to punish. Going over shows on Usage and is a conversation about your plan, not an outage. **The two people meters warn you in advance; the other four do not.** As your staff-member or active-learner figure approaches its ceiling, Panova tells the organisation's admins — again when it passes it, and again if somebody is actually turned away. Published experiences, storage, workspaces and scenes give you no warning: you meet them at the door, in the message that refuses what you were doing. That is why a publish can be refused on a day nothing had told you it was coming. ## Changing plan **Organisation → Billing**. Card-paid plans change immediately through the billing portal. Enterprise is quoted, so requesting it opens a conversation rather than charging a card. ## Securing your account **Account → Security** offers two-factor authentication and passkeys. If your organisation has anything worth protecting in Panova — and learner records qualify — turn one of them on. --- ## When a payment fails *Account, themes & billing. A declined card starts a clock, not a downgrade — and what to do inside it.* Source: https://support.panova.app/when-a-payment-fails Cards expire, banks decline things, and none of that is a reason to take a working course offline in the middle of a term. ## Nothing changes, and there is no deadline A failed payment puts your plan on **hold** rather than ending it. Published experiences stay up, learners keep working, and your limits stay where they were, for as long as the payment is outstanding. **Billing** shows that a payment failed and the day it failed. There is no countdown, because there is nothing at the end of one. **Nothing in Panova will change your plan on its own.** No job moves an organisation to a smaller plan overnight, and no account is switched off without a person deciding to. ## Fixing it Update the card in the billing portal from **Organisation → Billing**. As soon as a payment goes through the hold clears on its own — there is nothing to tell us. ## If it is never paid Somebody from our team gets in touch. Any change to your plan is then a conversation and a person's decision, and nothing is deleted by it. > A failed card is a conversation, not a switch-off. Nothing in Panova changes your plan on its own, and there is no deadline on the hold. ## Everything else about the subscription Changing plan, updating a card and cancelling all happen in the billing portal rather than in Panova. It is your card details and your invoice history, so they live with the payment provider rather than with us. --- ## Your organisation's defaults *Account, themes & billing. Content language, time zone and image quality — what each one actually changes.* Source: https://support.panova.app/organisation-defaults-language-and-images **Organisation → Settings** carries three defaults that reach learners. ## Content language This is the language your experiences are **written in** — not the language of the Panova interface. It travels with a published experience and tells a learner's browser what language the page is in, which is what a screen reader chooses a voice from. Set to English while the content is in Welsh, a screen reader will read Welsh aloud in an English voice, and it will be close to unintelligible. **It does not translate anything.** Panova's own interface — buttons, panels, menus — is in English whatever this is set to. And changing it does not reach back into experiences you have already published: those keep the language they were published with, because the words in them did not change either. ## Time zone Dates and times shown around the app are rendered in it. The one deliberate exception is the period labels on Usage and Billing, which stay in the platform's own time so that a label never sits above figures counted for a different month. ## Image quality How much resolution to keep when an image is uploaded. **Space-saving** suits a small allowance, **balanced** is the default, and **best** is always a deliberate choice rather than something we infer for you. This one is worth understanding before you change it, because an upload cannot be revisited — see [What happens to an image when you upload it](/support/articles/what-happens-to-an-uploaded-image). --- ## Sharing assets with your team *Account, themes & billing. The four levels an uploaded file can sit at, and who can put a file at each.* Source: https://support.panova.app/sharing-assets-with-your-team Every file in the asset library sits at one of four **sharing levels**, chosen as you upload it and changeable afterwards. | Level | Who sees it | | --- | --- | | **Personal** | Only you | | **Workspace** | Everyone working in that workspace | | **Organisation** | Everyone in the organisation, in any workspace | | **Panova stock** | Everyone, in every organisation — ours, and read-only | ## Choosing one Personal is the right home for a working file, a rough capture or anything you have not decided about yet. Move it up when it becomes something a colleague would look for. The levels you may use depend on your role: sharing to the whole organisation is an organisation-wide act, so it needs someone who works at that level. Where a level is not yours to use, the library greys it out and says what would change the answer. ## Moving a file later **Edit details**, on any row in the asset library, has a **Sharing** row. Choose a different level and save. The file itself does not move and nothing already using it changes — the scenes and pins holding it keep it. Changing a level asks the same question as uploading at that level, so a destination you could not have filed to in the first place is greyed and says what would change the answer. --- ## What happens to an image when you upload it *Scenes & images. It is re-encoded once and the original is not kept — so upload the good one.* Source: https://support.panova.app/what-happens-to-an-uploaded-image An uploaded image is re-encoded **once**, as it arrives, and the file you sent is not kept. That makes it worth thirty seconds of thought before you upload, because it cannot be revisited afterwards. ## Upload the best version you have Do not shrink a photograph to "save space" first. Panova will size it for you, and it cannot put back detail that was gone before it arrived. Keep your masters wherever you keep the rest of your originals. ## Two sizes, by what the image is for - A **backdrop** fills a view — a scene background, a cover, a page hero — and keeps up to 4096px on the default quality setting. - Anything **inline** sits inside a panel — a pin's media, an intro image — and keeps 1600px, which is more than a panel can show. The distinction matters most for 360°. A viewer showing 90° of an equirectangular photo is showing a quarter of its width stretched across the whole screen, so a panorama needs far more pixels than a picture that will sit in a box. A file uploaded straight to the asset library is treated as a backdrop, because it might end up behind a whole scene and guessing small there is the mistake that cannot be undone. ## Changing the numbers An organisation admin can move both, on **Organisation → Settings**. Space-saving trades sharpness for a smaller storage bill; best keeps more of what you sent. See [Your organisation's defaults](/support/articles/organisation-defaults-language-and-images). ## Rotation Photographs taken on a phone or a 360° camera carry an orientation flag rather than being stored the right way up. Panova applies it on the way in, so an image that looked correct in your photo app looks correct on the scene. > Your file is re-encoded once, on the way in, and the original is not kept. That is why the size is decided before you say what the picture is for. ## A linked picture skips all of this A picture you point at with a **URL** is not re-encoded, not resized and not stored — it stays on somebody else's server exactly as it is, which is also why it can disappear. Ticking **Save a copy to my library** on that tab brings it through the same path as an upload. --- ## Pin icons and colours *Pins & contexts. Giving pins a glyph and contexts a colour — and where the icon deliberately does not appear.* Source: https://support.panova.app/pin-icons-and-colours ## Icons A pin can carry an icon chosen from a library of about 1,750 — a fire extinguisher, a plug socket, a first-aid cross. Pick one that names the thing rather than decorating it: an icon a learner can read at a glance saves them opening the pin to find out whether it is relevant. ## Colours A context's colour is either one of the six house colours, which follow whichever theme the experience is using, or one you add yourself to the experience's own palette. Two things about the palette are worth knowing: - **A new context takes the first colour its scene is not already using.** Contexts are told apart by colour before anyone reads their names, so two identical ones would be worse than none. - **Removing a colour from the palette repaints nothing.** It stops being offered to new contexts; every context already wearing it keeps it, and a version you published with it goes on looking the way it did. That is what makes the remove control safe to press. ## Where icons do not appear Inside an activity — Wayfinding, Pin the Space, and the rest — pins are drawn as plain markers, without your icon. This is deliberate, not a fault to report. In an activity the marker **is** the task: it is a drop target, or an answer to be found. An icon that names what a pin is would answer the question the activity is asking, and a decorative one competes with it. Icons are for free exploration, where a learner is choosing what to look at rather than being asked to find something. --- ## Version history: preview, serve and restore *Publishing & sharing. Everything you can do with a version you have already published.* Source: https://support.panova.app/version-history-preview-serve-restore Open version history from the **status chip** in the editor header — the one that says whether you have unpublished changes. It lists every version with its number, title, who published it and when. Each version offers five things, in order of how much they touch. ## Its own link A link that always opens that version, however many times you publish afterwards. See [Sending a class to one version](/support/articles/sending-a-class-to-one-version). ## Preview Opens that version in a new tab, exactly as a learner received it. Changes nothing, and is the sensible first move before pressing any of the rest. ## Serve this version Re-points the plain share link at that version for everybody, until you change it again. Your draft is untouched. ## Copy to new Writes that version out as a **new experience** in the same workspace and leaves this one exactly as it was. This is the safe way to pick up an older direction without losing the current one. ## Restore Replaces your working draft with that version, discarding anything authored since. It is the only destructive control here, and the only one that asks before it runs. One consequence is worth reading twice: **scenes come back as new ones**, so attempts learners have already taken will no longer line up with them. Restore is for recovering a direction, not for correcting a live assessment. > Both start from an old version. One writes over your draft; the other leaves everything alone. ## "Published before restoring was possible" Restoring and copying both read the authored snapshot taken at publish time. Versions published before those snapshots existed do not carry one, so both controls are unavailable on them. They cannot be rebuilt from the learner's copy instead: that copy never contained your author-only contexts, so a draft rebuilt from it would quietly delete the content you chose to keep back. --- ## Sending a class to one version *Publishing & sharing. Hold one group on one version without freezing the experience for everyone else.* Source: https://support.panova.app/sending-a-class-to-one-version An experience has **two kinds of link**, and they are two addresses rather than a setting to choose between. Both work at the same time. ## The plain link The one in the header. It follows every future publish, so whoever holds it always gets your latest work. This is the right link for nearly everything. ## A version's own link Copy it from version history, from the row of the version you want. It goes on serving that version however many times you publish afterwards — the link for a class sitting an assessment, or a course that has been signed off. ## Why not Freeze the experience Because **Freeze** is one answer for everybody. Choosing it for one class re-points every link already handed out, including the ones you sent to people who should be seeing your newest version. Two addresses avoid that entirely: this January's cohort keeps January's content, everyone else moves on, and you do not have to remember which setting the experience is in. ## What is frozen, and what is not Only the **content** is frozen. A learner on a version link meets the same activities, the same attempt allowances and the same rules as everyone else, and their work counts towards the same single grade — one experience is one grade however many links reach it. So do not use a version link to give a group different rules. Use it when they must all see the same thing. --- ## Setting up your account *Getting started. What signing up creates, and what the setup wizard is for.* Source: https://support.panova.app/setting-up-your-account ## Signing up gives you a working account Registering creates your **organisation**, a first **workspace** inside it, and makes you the organisation's admin. That happens as you sign up, before you see anything else — so the account works whatever you do next. ## The five steps You land in a short wizard of five steps, and it refines what you already have. 1. **You** — your **Full name**, **Your time zone**, and your **Account email**, which is shown here and cannot be changed on this screen. 2. **Organisation** — its **Organisation name**, a **Description** if you want one, the name of your **First workspace**, the **Content language** and the **Time zone** the organisation runs in. 3. **First experience** — a name, and Panova opens it for you at the end. **Skip — I'll create one later** is a real answer, not a way of putting it off. 4. **Security** — a second factor, and whether your email address is confirmed. Both are below. 5. **Launch** — what you are about to save, and the button that saves it. Nothing is saved until you press the button at the end, and **you can leave at any point**. Abandoning it half-way costs you the typing, not the account — everything it asks about can be set later from **Organisation → Settings** and **Members**. What you have typed is kept for as long as the tab is open. That is what makes the Security step work at all: setting up a factor leaves this page and comes back, and without it you would return to step one with the organisation name you had typed wiped. ## Confirming your email The wizard shows whether your address is confirmed, with a **Resend** button beside it when it is not, and does not stop you if it is not. Everything past setup does, so confirm it when the email arrives — but a slow inbox should not cost you a wizard's worth of typing. Open the link in this browser and you come straight back to where you were. ## Two-factor authentication You are an organisation admin from your first minute, and admin accounts need a second factor, so the wizard asks for one. There are three to choose from — a **passkey**, an **authenticator app**, or a code sent to your email address. A passkey is offered first because it is the one you can turn on without reaching for a second device. Set one up there and you will not be asked again on your way in. ## If you were invited You do not see this wizard. An invitation admits you to somebody else's organisation, so registering builds you none of your own, and sign-up hands you to **Notifications**, where the offer is waiting. Sign-up also locks the address to the one that was invited — an account made at any other address could never accept what is sitting in that inbox. ## The tour A short walkthrough of the app opens the first time you reach the dashboard. Dismiss it and it stays dismissed; if you want it back, it is on the dashboard and in the **?** help panel in the header.