# Lira help center > Lira helps people practice workplace conversations with AI, review private feedback, and earn certificates. These guides cover learners, managers, and workspace admins. Guide links below serve public documentation as Markdown. Workspace access still requires sign-in and the appropriate role; this documentation does not grant access to private practice or workspace data. ## Get started - [Welcome to Lira](https://lira.thoughtly.com/docs/get-started/overview.md): Build confidence through realistic practice, focused feedback, and a clear next step. - [Your first practice](https://lira.thoughtly.com/docs/get-started/first-practice.md): Go from choosing a scenario to finding one useful improvement in your first conversation. - [Workspaces and roles](https://lira.thoughtly.com/docs/get-started/workspaces-and-roles.md): Choose the right workspace and understand which controls your role provides. - [Quick tour](https://lira.thoughtly.com/docs/get-started/product-walkthrough.md): Four short steps to find your way around Lira. ## Practice - [Find a scenario](https://lira.thoughtly.com/docs/practice/scenarios.md): Find available practice, return to drafts, and organize your scenario library. - [Read a scenario overview](https://lira.thoughtly.com/docs/practice/scenario-overview.md): Understand the goal, counterpart, and requirements before you start practicing. - [Start and control a practice call](https://lira.thoughtly.com/docs/practice/start-call.md): Check your devices, begin a browser conversation, and find the call controls. - [Create and share a scenario](https://lira.thoughtly.com/docs/practice/private-prep.md): Describe a conversation, refine its brief, and choose how to share it. - [Folders, drafts, and Trash](https://lira.thoughtly.com/docs/practice/organize-scenarios.md): File scenarios, clean up drafts in bulk, and restore deleted work. - [Practice with live coaching](https://lira.thoughtly.com/docs/practice/live-coaching.md): Get optional suggestions during a desktop call, then practice independently to qualify. ## Results & progress - [Understand feedback and scoring](https://lira.thoughtly.com/docs/results/feedback-and-scoring.md): Read your results, use the evidence, and understand what makes an attempt qualify. - [Review recordings and transcripts](https://lira.thoughtly.com/docs/results/recordings-and-transcripts.md): Replay the conversation, follow the transcript, and jump directly to useful moments. - [Share a practice attempt](https://lira.thoughtly.com/docs/results/submitting-and-sharing.md): Share a completed scenario attempt, copy its replay link, and change access later. - [Earn and share certificates](https://lira.thoughtly.com/docs/results/certificates.md): Find your credentials, share a prepared LinkedIn post, and control public certificate access. - [Understand leaderboards](https://lira.thoughtly.com/docs/results/leaderboards.md): See how shared practice scores are ranked and how workspace privacy affects People and Teams views. ## Manage training - [Create and edit scenarios](https://lira.thoughtly.com/docs/manage-training/create-scenarios.md): Turn a repeatable conversation into a clear practice brief with meaningful scoring. - [Manage workspace knowledge](https://lira.thoughtly.com/docs/manage-training/knowledge-sources.md): Ground scenarios in approved website pages, documents, and product information. - [Design scoring and certificate requirements](https://lira.thoughtly.com/docs/manage-training/scoring-and-certificates.md): Define observable skills and a fair, explicit standard for completing a scenario. - [Assign and manage training](https://lira.thoughtly.com/docs/manage-training/assignments.md): Choose who should practice a published scenario and track assignment completion. - [Manage people and teams](https://lira.thoughtly.com/docs/manage-training/people-and-teams.md): Invite people, organize reporting relationships, and keep workspace access intentional. - [Review submitted results](https://lira.thoughtly.com/docs/manage-training/reviewing-results.md): Find the training results you can review and give focused, actionable coaching. ## Workspace & account - [Manage your account](https://lira.thoughtly.com/docs/workspace/account.md): Update your profile, protect your sign-in, and distinguish personal settings from workspace settings. - [Workspace settings and branding](https://lira.thoughtly.com/docs/workspace/settings-and-branding.md): Manage company details, certificate branding, and your workspace's sign-in requirement. - [Privacy, sharing, and retention](https://lira.thoughtly.com/docs/workspace/privacy.md): Understand what stays private, what a submission shares, and why content may become unavailable. - [Connect an AI agent](https://lira.thoughtly.com/docs/workspace/ai-agents.md): Use ChatGPT, Claude, Codex, or another agent to manage training and explore permitted workspace data. - [Manage email notifications](https://lira.thoughtly.com/docs/workspace/email-notifications.md): Choose your reminders and understand the training, invitation, and account emails Lira sends. - [Set up two-factor authentication and passkeys](https://lira.thoughtly.com/docs/workspace/account-security.md): Protect your account, verify a required sign-in, and manage your workspace's security requirement. - [Review and export the audit log](https://lira.thoughtly.com/docs/workspace/audit-log.md): Find workspace changes and support access, inspect an event, and export matching activity. - [Manage API keys](https://lira.thoughtly.com/docs/workspace/api-keys.md): Create and revoke credentials for programmatic workspace administration. ## Troubleshooting - [Fix microphone and audio problems](https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio.md): Check permissions, choose the correct device, and recover when you cannot hear or be heard. - [Recover from a connection problem](https://lira.thoughtly.com/docs/troubleshooting/connection.md): Handle reconnecting calls, unavailable practice, and interrupted saves without losing context. - [Find missing or incomplete feedback](https://lira.thoughtly.com/docs/troubleshooting/feedback.md): Distinguish a preparing score, streamed coaching, and unavailable call content. - [Resolve sign-in and workspace access](https://lira.thoughtly.com/docs/troubleshooting/access.md): Find the right account, complete security verification, handle invitations, and understand missing permissions. - [Contact support](https://lira.thoughtly.com/docs/troubleshooting/contact-support.md): Share beta feedback about your current screen or get help from Thoughtly Lira. ## Optional - [Complete documentation](https://lira.thoughtly.com/llms-full.txt): All published guides in one Markdown file. - [Help center](https://lira.thoughtly.com/docs): Browse the documentation website. --- # Welcome to Lira > Build confidence through realistic practice, focused feedback, and a clear next step. Source: https://lira.thoughtly.com/docs/get-started/overview Audience: everyone Last reviewed: 2026-11-03 Lira helps you rehearse conversations before they matter. Choose a scenario, speak with an AI counterpart in your browser, and review feedback grounded in your conversation. ## Your practice loop 1. **Choose a scenario.** Explore the scenarios available in your workspace. Assigned scenarios appear prominently, alongside other opportunities to practice. 2. **Read the brief.** Understand your counterpart, the situation, your goal, and the scoring rubric. 3. **Have the conversation.** Check your microphone, start the call, and practice in your own words. 4. **Pick one thing to improve.** Review the available feedback, replay useful moments, and try again. A scenario is a simulation. Agreeing to a meeting or next step during a practice call does not book a real meeting or contact a customer. ## Find your way around | Area | What you can do | | --- | --- | | Scenarios | Browse scenarios and open your assigned practice. | | Progress | Return to your attempts and available feedback. | | Certificates | View the credentials you have earned. | | Leaderboard | See qualifying submitted results, when your workspace enables rankings. | | My prep | Prepare privately for a particular meeting, when available in your workspace. | Managers and admins have additional controls for creating scenarios, assigning training, and reviewing results they are authorized to see. Your workspace role determines which controls appear. > **Practice and sharing are separate** > > Practicing does not automatically submit your conversation to a manager. Workspace privacy settings determine what is retained and which sharing options are available. Earning a certificate does not require publishing it. Start with [your first practice](https://lira.thoughtly.com/docs/get-started/first-practice), or learn about [workspaces and roles](https://lira.thoughtly.com/docs/get-started/workspaces-and-roles). ![Practice metrics and weekly activity above a result table showing scores, certificates, and Private or Submitted visibility.](https://lira.thoughtly.com/docs/images/product/progress.webp) Progress brings your practice history, activity, certificates, and sharing status into one place. ## Find help as you go The top-left Lira logo on public pages, including sign-in and the help center, opens the [Lira product page](https://thoughtly.com/product/lira) in a new tab. Open the **Help center** from the workspace menu or the question-mark icon beside Notifications. It opens in a new tab so you can keep your place in Lira. Use the search bar in the help center's top navigation to find a guide. You can also press **⌘K** on a Mac or **Ctrl+K** on Windows and Linux. To report an issue or suggest an improvement about your current screen, select the small blue **Beta** button beside Help in your workspace header. On other pages, find it beside the Lira logo. See [beta feedback and support](https://lira.thoughtly.com/docs/troubleshooting/contact-support#share-beta-feedback) for what is included and how to get help. ### Ask AI about Lira In the help center's top navigation, select **Ask AI** beside **Open Lira**, then choose **ChatGPT**, **Claude**, **Perplexity**, or **Grok**. Each menu item shows the assistant's logo and opens a new tab with a prompt pointing to Lira's public documentation. ![The Ask AI about Lira dropdown lists ChatGPT, Claude, Perplexity, and Grok with their company logos and new-tab arrows.](https://lira.thoughtly.com/docs/images/product/docs-ai-menu.webp) Choose an assistant from Ask AI beside Open Lira. You can use this without signing in to Lira; the assistant may ask you to sign in to its own service. This shares only public guides, and does not connect the assistant to your workspace or private practice. If the assistant cannot read the link, open [the complete documentation](https://lira.thoughtly.com/llms-full.txt) and paste the relevant guide into your chat. --- # Your first practice > Go from choosing a scenario to finding one useful improvement in your first conversation. Source: https://lira.thoughtly.com/docs/get-started/first-practice Audience: everyone Last reviewed: 2026-10-30 You need access to a Lira workspace, a working microphone, and a browser that can access it. Headphones can help you hear clearly and reduce echo. ## Start with Getting started On your first visit, confirm your name and complete the private **Getting started** conversation before entering the workspace. Lira prepares it from approved workspace context and shared training. Allow one to two minutes; no product knowledge, passing score, or completed objective is required. The certificate preview shows what you will earn. Select **Start practice** to check your microphone before the conversation begins; your certificate is awarded after you finish the call. ![Getting started with a Start practice button, privacy and an Up to 2 minutes note beneath it, and a first-certificate preview.](https://lira.thoughtly.com/docs/images/product/onboarding-first-practice.webp) Start a short private conversation and see the certificate you will earn. Check your microphone and choose **Start call**. Your practice partner explains how Lira helps you practice real conversations and get feedback, then asks what you would like to get better at. You try one playful exercise based on your goal, such as a quick pitch, get a little feedback, and answer one final question about what you would like to try next. The partner then wraps up and wishes you well. The conversation ends automatically within two minutes; choose **End** if you want to finish sooner. Every completed starter conversation receives a **Getting started** certificate, regardless of score. A microphone or calling failure lets you retry; it does not count as a completed conversation. If a call ends without confirmed completion, Lira returns you to **Start practice** with an explanation. Try another short conversation using the same practice. ![The Getting started screen explains that the previous call did not have confirmed completion and offers Start practice again.](https://lira.thoughtly.com/docs/images/product/onboarding-practice-interrupted.webp) An interrupted conversation keeps your setup and offers a fresh attempt. After the conversation, a brief processing indicator appears before Lira opens the full-screen award. If you refresh or return later, you resume this step until you continue. If progress cannot be checked, choose **Check again**; your completed conversation stays saved. ![The onboarding shell shows a single centered processing indicator before the certificate appears.](https://lira.thoughtly.com/docs/images/product/onboarding-certificate-preparing.webp) Lira finishes saving your practice before opening the award. Choose **Continue** to enter the workspace and open the [four-step quick tour](https://lira.thoughtly.com/docs/get-started/product-walkthrough). Close the award or press **Escape** to enter without starting the tour. You can pause it at any time or reopen it from Help. The starter is private, does not complete an assignment, and does not appear in team rankings. Your certificate stays private until you choose to share it. Below **Continue**, choose the optional **Connect LinkedIn & share** action when available, or **Share on LinkedIn** if already connected, to open certificate sharing. Choose **Share on LinkedIn** to share the prepared post, or **Copy link** to share the certificate elsewhere. If you need to connect first, authorization alone does not publish anything; choose Share again when you return. Optional caption editing is in **Sharing options → Review or edit post**. You can close sharing and continue, or share later from **Certificates**. See [certificate sharing](https://lira.thoughtly.com/docs/results/certificates#share-on-linkedin) for privacy and connection controls. ![A fictional Jordan Rivera certificate is presented in a pale blue envelope with Continue and a borderless Share on LinkedIn action below it.](https://lira.thoughtly.com/docs/images/product/linkedin-first-award.png) Continue into Lira or choose the optional LinkedIn action below it. Once you enter the workspace, the **Getting started** example moves to **Trash** and leaves your active scenario library. Your practice remains in **Progress**, and your first certificate remains in **Certificates**. If onboarding is unfinished, the example stays available so you can complete it. The steps below apply to ordinary practice after onboarding. ## 1. Choose your conversation Open **Scenarios** and select a scenario. Active assignments appear with the earliest due date first and undated assignments afterward, but you can also explore other published scenarios available to you. If you are completing an assignment, open its assigned card so the attempt is connected to that assignment. Read the **Pre-Call Brief**, then the objective and requirements in **Grading**. You do not need to memorize a script. Focus on what you want to learn about the person you will speak with. ![The scenario's artwork header shows its title, five-minute duration, difficulty and voice, with Start practice in the action bar above.](https://lira.thoughtly.com/docs/images/product/scenario-overview.png) Review the call settings, then choose Start practice when you are ready. ## 2. Check your audio Select **Start practice**. In **Ready to practice?**, enable your microphone when prompted. Choose the right microphone, speak to check the input indicator, and use **Test speaker** to check playback. ![The Ready to practice? dialog shows the microphone selector, input indicator, speaker test, Cancel, and Start call.](https://lira.thoughtly.com/docs/images/product/practice-ready-dialog.png) Check your microphone and speaker before starting the call. Allowing microphone access prepares the call; it does not begin the conversation. Select **Start call** when you are ready. If the check fails, follow [microphone and audio troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio). ## 3. Practice, then end the call Speak naturally and give your counterpart time to respond. Use **Mute** if you need a pause, and **End** when you have finished. On phones, the call fills the screen. On desktop, the bottom call bar remains available while you navigate within the workspace. ![A full-screen mobile call shows the Lira logo above the conversation title and elapsed time, with large circular Mute and red End controls below.](https://lira.thoughtly.com/docs/images/product/practice-call-controls.webp) The mobile call screen keeps the conversation and its controls in focus. ## 4. Review one thing When feedback is ready, open the attempt. Read the overall outcome, then review a skill and its supporting moments. If recording and transcript content are available, use them to hear what happened in context. Choose one change to make before selecting **Practice again**. Short calls still receive a score when dialogue was captured, with zero for skills not demonstrated. A score based on an incomplete capture does not establish certificate eligibility. > **You choose whether to submit** > > An eligible assigned attempt can be submitted separately, depending on workspace privacy. You can review your feedback before making that decision. Next: [Understand feedback and scoring](https://lira.thoughtly.com/docs/results/feedback-and-scoring). --- # Workspaces and roles > Choose the right workspace and understand which controls your role provides. Source: https://lira.thoughtly.com/docs/get-started/workspaces-and-roles Audience: everyone Last reviewed: 2026-10-27 A workspace keeps an organization's scenarios, people, assignments, and settings together. Your role belongs to that workspace, so your access may differ between workspaces. ![Workspace menu showing two example workspaces, account settings, workspace settings, Help center, and Sign out.](https://lira.thoughtly.com/docs/images/product/workspace-menu.webp) Switch workspaces or open your account from one menu. Workspace settings are shown to admins. ## Switch workspaces Open the workspace menu at the top of the sidebar and choose a workspace. The selected workspace is marked in the list. If you cannot see the workspace you expected, check that you signed in with the email address used for your invitation. During onboarding, the workspace menu is in the top-right corner. You can switch workspaces, open the **Help center**, or sign out while your progress is saved. Each workspace has its own onboarding progress. When you sign in to an account with more than one workspace, choose which workspace to open. Switching workspaces may ask you to sign in again or complete that workspace's security checks before it opens. If you see **Secure your account**, your workspace requires two-factor authentication. Set up or verify an authenticator app or a passkey; either method works. This check comes before onboarding as well as ordinary workspace access. See [account security](https://lira.thoughtly.com/docs/workspace/account-security). The same menu provides **Your account** and **Sign out**. Your account page shows your profile information; the menu keeps those details out of the navigation. ## Understand your role | Role | Typical access | | --- | --- | | Trainee | Practice available scenarios, review personal progress, and manage their own certificate sharing. | | Manager | Practice and author scenarios, assign training to people they manage, and review eligible submitted results within that scope. | | Admin | Manage the workspace, its people and roles, workspace settings, and training across the workspace. | Managers can edit training scenarios they created; admins can manage shared scenarios throughout their workspace. Private personal scenarios remain owner-only for every role. A manager's access to people and submitted results is limited to the people they manage. Being an admin or manager does not grant access to everyone's unsubmitted practice or private meeting prep. [Workspace privacy](https://lira.thoughtly.com/docs/workspace/privacy) still applies. ## Join or change access Use your invitation to join the workspace. If your invitation has expired, was revoked, or uses a different email address, ask a workspace admin for help. Only an authorized admin can change your workspace role. If this is your first sign-in, Lira may email a secure password-setup link after you enter your invited address. Open it in the same browser, set your password, then choose **Back to log in** to continue joining. If the link or invitation expires, request a fresh link or ask your workspace admin for a new invitation. ### Your first visit Every role follows the same short welcome, including the first admin of a team-provisioned workspace. Complete any required [account security check](https://lira.thoughtly.com/docs/workspace/account-security), then confirm your **First name** and optional **Last name**. Your existing name is prefilled; compound names stay in the field you entered them in. Choose **Continue**. ![A welcome form with separate First name and optional Last name fields, prefilled with fictional Jordan Rivera details, and a Continue button.](https://lira.thoughtly.com/docs/images/product/onboarding-welcome.webp) Confirm your name once before your first conversation. Lira prepares a private **Getting started** scenario using approved workspace context and shared training. In one to two minutes, you meet Lira, share your goal, try one playful practice turn, and reflect on what to try next. There is no passing score or required objective. Enable your microphone, check your audio, and start the call when you are ready. Completing the conversation awards your first certificate regardless of your score. After this practice, Lira prepares and presents your first certificate. If preparation, microphone access, or calling fails, your progress stays saved. Use the recovery action shown or return later to try again. See [microphone help](https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio) and [connection help](https://lira.thoughtly.com/docs/troubleshooting/connection). The full-screen award presents your **Getting started** certificate. You return to this step after a refresh until you continue. Choose **Continue** to open the workspace with the [four-step quick tour](https://lira.thoughtly.com/docs/get-started/product-walkthrough). Close the award or press **Escape** to enter without the tour. Your requested page is preserved; otherwise admins and managers enter **Overview**, and trainees enter **Scenarios**. Your starter scenario stays private and moves to **Trash** when you finish onboarding. It cannot be shared or published as team training. Your practice remains in **Progress**, and its certificate stays in **Certificates**, private until you choose to publish it. It does not complete a team assignment or enter a leaderboard. See [certificates](https://lira.thoughtly.com/docs/results/certificates). ### Joining as an admin Your workspace is provisioned by the Lira team. Joining does not require company, product, team, or scenario setup. After your first practice, use [workspace settings](https://lira.thoughtly.com/docs/workspace/settings-and-branding), [People](https://lira.thoughtly.com/docs/manage-training/people-and-teams), and [Scenarios](https://lira.thoughtly.com/docs/manage-training/create-scenarios) to manage the workspace. Admins and managers see a next action on **Overview**: invite people, create a scenario, or assign training, based on the eligible people and training available to them. Existing activity remains visible. Managers with a saved setup from an earlier visit can choose **Review saved team setup** on **My team** after onboarding. Review the recipients and training, then deliberately send or confirm discard. Opening the review does not send invitations or assignments. People and scenarios that are no longer eligible must be corrected before sending. If a control is missing, first check your selected workspace and role. See [access troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/access) if you still cannot reach something you need. --- # Quick tour > Four short steps to find your way around Lira. Source: https://lira.thoughtly.com/docs/get-started/product-walkthrough Audience: everyone Last reviewed: 2026-10-27 Lira’s optional tour covers the basics in four steps: your workspace, the navigation, choosing a scenario, and finding help. The navigation and scenario tips adapt to your role. Choose **Continue** on your first certificate to open the tour in your workspace. If you close the certificate instead, a dismissible **Take the quick tour** offer lets you start later. You can also choose **Onboarding guide** from the question-mark menu in the workspace header. The optional LinkedIn sharing action on your first award is separate from the tour. Connecting or reviewing a post does not start the tour or prevent you from continuing into the workspace. ![The first tour tip, This is your workspace, highlights the workspace menu and provides Next and Pause controls.](https://lira.thoughtly.com/docs/images/product/onboarding-first-tour.webp) Continue from your first certificate to the four-step tour. ![An optional Find your way around offer with Take the quick tour and a dismiss control.](https://lira.thoughtly.com/docs/images/product/tour-offer.webp) Start the four-step tour when you want it, or dismiss the offer and begin working. If your workspace requires [two-factor authentication](https://lira.thoughtly.com/docs/workspace/account-security), complete setup or verify your sign-in with an authenticator app or a passkey before onboarding. The optional tour remains four steps. ![The header's question-mark menu showing Contact support, Onboarding guide, and Documentation.](https://lira.thoughtly.com/docs/images/product/help-menu.jpg) Choose Onboarding guide for the short tour. ## Move at your own pace Use **Back** and **Next** to move through the four tips. The close button or **Escape** pauses the tour; **Onboarding guide** takes you back to your saved place. Choose **Done** on the last tip to close it. Opening the guide after finishing starts it again. The tour highlights existing controls. It does not start a call, assign training, or change workspace data. Closing it never prevents you from using Lira. Practice takes priority: the tour pauses while a call is in progress, including microphone permission and a disconnected call awaiting your action. Return to **Onboarding guide** after finishing or closing the call. ## When you need more detail Use the question icon beside a tip’s title to open its related guide in a new tab. The header’s **Documentation** menu item opens the complete help center, and **Contact support** opens the support chat. Continue with [Your first practice](https://lira.thoughtly.com/docs/get-started/first-practice), [Assign and manage training](https://lira.thoughtly.com/docs/manage-training/assignments), or [Review submitted results](https://lira.thoughtly.com/docs/manage-training/reviewing-results) when you need those workflows. --- # Find a scenario > Find available practice, return to drafts, and organize your scenario library. Source: https://lira.thoughtly.com/docs/practice/scenarios Audience: everyone Last reviewed: 2026-10-30 **Scenarios** brings the scenarios you can access into one library. **Available** contains ready scenarios; **Drafts** contains unfinished work. **Closed** includes closed scenarios you manage and completed assigned versions you can revisit. **Trash** keeps deleted scenarios, with recovery available for scenarios you can manage. ![The Drafts list shows two Untitled scenario entries beneath shared folders, with Created by identifying You and a fictional teammate.](https://lira.thoughtly.com/docs/images/product/scenario-unnamed-drafts.png) Unnamed drafts stay visible, with their creator shown in List. When you switch views, a moving underline appears beneath the destination tab. The current list stays visible until the new view is ready. If the view cannot load, choose **Try again**. ![Scenario view tabs with Available still selected and a loading underline beneath Drafts.](https://lira.thoughtly.com/docs/images/product/scenario-view-loading.png) Loading feedback stays with the view you chose. ## Find the right conversation - **Search scenarios** by title or description. Search from **All scenarios** looks across folders; search inside a folder stays within it. - Open a folder to see scenarios you can access. Folders organize the library for everyone in the workspace; private scenarios stay private. Choose **All scenarios** in the breadcrumb to return to the directory root. - Open **Filter** to choose difficulty or show scenarios created by you, private to you, or shared with the workspace. - Sort by **Recently edited**, **Newest first**, **Most popular**, or **A–Z**. Available, Drafts and Closed show subfolders first, followed by the scenarios filed in the current location. At **All scenarios**, those scenarios are **Unfiled**. Use the breadcrumb to move through nested folders or return to the root. Folder counts include direct scenarios you can access across all views, including Trash, so a folder can contain scenarios even when its current view is empty. Trash shows deleted scenarios across folders without a folder section. Choose **Grid** for cards and folder tiles or **List** for compact rows with folders first. Available starts in Grid; Drafts, Closed and Trash start in List. Once you choose a layout, it follows you between views and folders. The larger assigned section keeps its own card layout. List includes **Created by** so you can identify each scenario's author. Your own scenarios show **You**. On narrow screens, this attribution appears below the title. Drafts without a name appear as **Untitled scenario** in either layout. Search for **Untitled scenario** to find them; **A–Z** sorts them by that displayed name. Open a draft to continue editing it. Each directory page contains up to 24 scenarios; folders and featured assignments do not use those places. Use **Previous** and **Next** below the results to change pages. Changing the view, folder, search, filters or ordering returns to page one. Page changes bring you to the start of the updated results. At the root, view-tab counts cover scenarios across folders; the page range describes the directory results. On Available at the directory root, **Assigned to you** shows up to three active assignments in larger cards above the directory. This section appears when search, difficulty and ownership filters are clear, and stays visible as you change directory pages. On a phone, swipe across the assigned cards to see the next one. Keyboard focus also brings each card into view. Open one to keep its assignment context. Cards show a short description of the conversation, along with the folder and difficulty. Open a scenario to read its full pre-call brief. Until you have a score, the footer shows estimated duration. After a scored attempt, **Best** replaces duration with your personal best out of 100, including a score of zero. Sharing settings stay in the details preview. Open a scenario to see its practice activity. Most popular reflects practice activity; open a scenario to review its goal before choosing it. Hover over a card to preview **Duration**, **Created by**, **Visibility**, and **Status** in a floating tooltip. The tooltip follows your cursor and stays inside the screen edges. Focus the card link with a keyboard to see the same details. On touch screens, the details appear below the description, and **Best** stays in the footer. Press **Escape** or click elsewhere to dismiss the tooltip; the card stays in place. Your personal best also appears under **Your progress** on the scenario page. In the visibility details, **Only you** means owner-only access and **Workspace** means workspace sharing. Unpublished training drafts still require authoring permission. Sharing a scenario does not share your existing attempts or feedback. **Assigned** identifies an assignment and **Certified** reflects an earned certificate. Private drafts show **You**, **Only you**, and **Draft**. Long titles and metadata may be shortened with an ellipsis. The tooltip shows the full creator name and metadata; open the scenario to read its full title and complete brief. ![A compact assigned scenario shows Best 3 out of 100 in its footer, while a floating preview shows duration, creator, workspace visibility and assignment status.](https://lira.thoughtly.com/docs/images/product/scenario-card-details.png) Your personal best replaces duration in the footer; sharing stays in details. ## Open or manage a scenario Open a card to read the brief and scoring rubric. Right-click a card or row, or touch and hold it on a phone, for actions you are allowed to perform, such as **Edit**, **Assign**, **Move to folder**, or **Delete scenario**. With a keyboard, focus the card link or row title and press **Menu** or **Shift+F10**. The scenario page and editor also offer an **Actions** button. Published training can be assigned by an authorized manager or admin even when that person cannot edit it. Choose **Create scenario** to open the [scenario studio](https://lira.thoughtly.com/docs/practice/private-prep). Scenarios created from your workspace member account start private, including for managers and admins. For high-volume cleanup, use **Select** and the [folder and Trash controls](https://lira.thoughtly.com/docs/practice/organize-scenarios). With a mouse or trackpad, drag a card or row you can manage onto a folder tile or row. Use **Move to folder** from the context menu with touch or a keyboard. [Folder guidance](https://lira.thoughtly.com/docs/practice/organize-scenarios#drag-scenarios-into-folders) covers filing several scenarios together and returning them to the root. ## Complete an assignment Open the assigned scenario and start practice from its assignment context. Existing assignments retain their original published requirements when a new version is saved. An assignment is completed by meeting its certificate requirements in a qualifying attempt; submission remains a separate sharing decision. ## When the library looks empty Choose **All scenarios**, then search from the root to look across folders. Check the selected view, filters and workspace. An unfinished scenario may be in **Drafts**, and one you deleted may be in **Trash**. A manager or admin may need to publish or assign team training before it becomes available to you. The private **Getting started** example moves to **Trash** when you finish onboarding, keeping it out of your active library. Your first practice and certificate remain available in **Progress** and **Certificates**. Next: [Read a scenario overview](https://lira.thoughtly.com/docs/practice/scenario-overview) or [organize and recover scenarios](https://lira.thoughtly.com/docs/practice/organize-scenarios). --- # Read a scenario overview > Understand the goal, counterpart, and requirements before you start practicing. Source: https://lira.thoughtly.com/docs/practice/scenario-overview Audience: everyone Last reviewed: 2026-10-30 The scenario overview is your brief for the conversation. It uses the same document layout as the editor, without its chat or editing hints: artwork and call settings above the brief and grading. **Start practice** stays in the top action bar. ![An owner's scenario overview with Edit, Assign, Actions and Start practice above an artwork header with the scenario title, duration, Expert difficulty and voice.](https://lira.thoughtly.com/docs/images/product/scenario-actions-header.png) Start practice from the action bar; review the call settings below. ## Read these first The **Pre-Call Brief** explains your role, the situation, and any background you should know before the conversation. **Grading** contains the objective you are working toward and how performance will be assessed. Read both before starting; the counterpart may have information you will need to learn during the call. The settings panel shows the maximum call length, difficulty, and voice with its language. You do not need to change your account to practice in a scenario's language. The play button beside a supported voice previews a short English sample without starting a call. The description below difficulty explains what to expect. **Expert** is intentionally intense: the counterpart can interrupt a long pitch, challenge assumptions, react sharply or sarcastically to pressure, and end the conversation early. Long speaking turns or extended unexplained silence can prompt a response; ordinary thinking pauses, filler, accents, and stuttering are not failures. At any difficulty, a clear request to hang up or stop the role-play ends the call. The browser call ends automatically when the counterpart leaves; you do not need to press **End call**. The folder and publishing details identify the scenario you are using. Filing does not change its conversation or who can access it. If it is assigned, the assignment context helps distinguish it from general practice. ## Start a fresh conversation Each practice call starts independently. Your counterpart receives the scenario's private instructions, but not your previous practice transcripts, scores, coaching, goal, or scoring rubric. Its starting manner and patience can vary between attempts while its identity and the scenario's facts stay consistent. Within the call, it remembers what you have discussed, including unfinished answers and earlier refusals. If the brief describes a fictional earlier conversation, that is part of the scenario rather than memory of an earlier attempt. The creator's scenario defines the person and situation. Difficulty adjusts their patience and resistance: - **Easy:** patient and cooperative, with clear answers and room to recover. - **Medium:** ordinary skepticism and relevant concerns, with occasional redirection. - **Hard:** guarded and impatient; challenges claims, interrupts rambling, and may leave an unproductive exchange. - **Expert:** highly resistant and unpredictable; can respond bluntly, interrupt quickly, or end the call after a brief exchange. Understanding your explanation does not mean agreeing with it or accepting a next step. Listen to the actual response and acknowledge the person's concerns. Relevant answers and changed behavior can earn more attention, but do not guarantee a successful outcome. Short calls still receive feedback when usable dialogue was captured; skills not demonstrated receive zero. See [feedback and scoring](https://lira.thoughtly.com/docs/results/feedback-and-scoring). There is no fixed discovery-question or meeting-booking checklist for every call. A support conversation follows its own problem and circumstances. To change a scenario you own, use [Edit to describe the change in chat](https://lira.thoughtly.com/docs/manage-training/create-scenarios). ## Understand the rubric **Grading** brings the objective, passing score, objective requirement and skill rubric together. Each skill shows its share of the overall score with a percentage and a small bar. Any individual minimum is shown beside the skill. Open **View standards** for expected behaviors and an example. Training scenarios also show certificate validity. You must meet the applicable requirements in the same attempt. A strong result in one skill on one call does not combine with another call to qualify. See [feedback and scoring](https://lira.thoughtly.com/docs/results/feedback-and-scoring) for details. ![Grading combines the objective, passing requirements and rubric with proportional skill weights and expandable standards.](https://lira.thoughtly.com/docs/images/product/scoring-rubric.webp) See what is graded, how it is weighted and what good looks like. ## Return to your progress Below grading, **Scenario activity** brings together the number of people certified on this version, your personal best and attempt count where available. Recent attempts open their feedback; **View leaderboard** shows eligible submitted results, rather than every private practice call. Activity-only workspaces do not show personal scores. Folder, publishing and assignment details appear in the panel's footer. Scenarios without activity show **Scenario details** instead. ![Scenario activity groups people certified, personal best, attempt count, recent attempts and scenario details in one panel.](https://lira.thoughtly.com/docs/images/product/scenario-activity.png) Review results and scenario details together; open an attempt for its feedback. Select **Start practice** when you are ready. The row above the conversation contains the actions available to you: owners can change sharing, authorized authors can open **Edit**, and authorized managers and admins can assign published training or publish a reviewed scenario. **Back to scenarios** returns to the library. The folder label opens the same Move picker as the actions menu. On a narrow screen, editing, workspace access and assignment actions move into **Actions**, leaving the back arrow and **Start practice** in one compact row. ![A mobile scenario overview with a compact back arrow, Actions menu and Start practice button above the brief.](https://lira.thoughtly.com/docs/images/product/scenario-overview-mobile.png) Use Actions for scenario management while the practice button stays within reach. Authors can use **Test call** inside Edit for simulated feedback and editor test history, subject to workspace privacy and retention. Those tests do not appear in learner practice history or rankings. Use **Start practice** on the scenario page when you want a saved learner attempt. See [test a scenario](https://lira.thoughtly.com/docs/manage-training/create-scenarios#test-the-scenario). Use **Actions** to [move or delete the scenario](https://lira.thoughtly.com/docs/practice/organize-scenarios). Delete moves it to recoverable Trash. Existing attempts and results remain available under the same privacy rules. > **Published versions preserve context** > > An existing assignment or attempt can use an earlier published version. Its original rubric and certificate requirements still apply, even if the scenario has since been updated. > > When the versions differ, **Open your assigned version** returns to your assignment from the current scenario. From the assignment, **Open current scenario** shows the latest published settings. Start practice from the assigned version when you want an attempt to count toward that assignment. --- # Start and control a practice call > Check your devices, begin a browser conversation, and find the call controls. Source: https://lira.thoughtly.com/docs/practice/start-call Audience: everyone Last reviewed: 2026-11-03 Practice calls take place in your browser. Keep the Lira tab open and use a stable connection while you practice. ## Before the conversation When available on desktop, [live coaching](https://lira.thoughtly.com/docs/practice/live-coaching) offers optional suggestions during the call. Enabling it makes the attempt practice-only: it cannot earn a certificate, enter leaderboards or complete assigned training. 1. Open a scenario and select **Start practice**. 2. If access has not been granted, select **Enable microphone** or the muted microphone selector. Allow access in the browser prompt. 3. Choose the microphone you want to use. Speak a few words and check the input indicator. 4. Select **Test speaker** and confirm you can hear the sound. 5. Select **Start call** to begin. If you have already granted access, the microphone check may connect automatically. The conversation still waits for you to select **Start call**. The scenario can have you call the counterpart or answer an incoming customer. Follow its brief when the call connects. Each new attempt starts independently: the counterpart does not remember earlier practice calls, scores or feedback, and does not receive your training goal or scoring rubric. Its mood and attention may differ each time. ## Answer an incoming customer call Some scenarios make you the representative receiving a customer's call. Select **Start practice** and complete the same microphone check. The dialog shows **Incoming practice call** and may ring through your selected speaker. Choose **Answer call**, wait for the connection, then greet the customer. They explain their problem after you answer. Cancel stops ringing and closes the check without starting an attempt. ![The compact Incoming practice call dialog with microphone and speaker controls, Cancel, and Answer call.](https://lira.thoughtly.com/docs/images/product/incoming-practice-call.webp) Check your audio, then answer and greet the customer. ## During the call Use **Mute** to stop sending microphone audio, then **Unmute** to continue. The call timer and connection status help you see whether the conversation is active. On desktop, you can navigate within the workspace without losing the call controls. On phones, the call fills the screen, with the scenario name and timer above large, round controls. **Mute** turns white while your microphone is muted; select **Unmute** to continue. The red handset ends the call. Another scenario’s **Start practice** stays unavailable until the current call ends. In the final minute of the scenario’s maximum conversation length, a countdown appears in the call controls. You’ll hear a short beep each second for the last ten seconds. At the time limit, the call ends automatically and the hang-up sound plays. Muting your microphone does not mute these reminders. Reconnecting does not restart the time limit. ![A countdown in the center of the call controls shows the remaining time beside the Mute and End controls.](https://lira.thoughtly.com/docs/images/product/call-countdown.webp) The final-minute countdown shows how long remains before the call ends automatically. ![A full-screen mobile call with the Lira logo above the scenario name and timer, a final-minute countdown below, and circular Mute and red End controls near the bottom.](https://lira.thoughtly.com/docs/images/product/call-countdown-mobile.webp) On phones, the call fills the screen, with the remaining time below the timer and large controls within reach. Select **End** when you have finished. If ending fails, use **Retry end** when offered instead of repeatedly starting a new call. If the practice partner ends the call, three short beeps confirm the disconnect. After the call ends, Lira prepares the available feedback. To practice the same scenario again after a call ends, return to the scenario and select **Start practice**. Each new call creates a separate attempt, including while the previous call’s feedback is still being prepared. ## When something interrupts the call If Lira shows **Reconnecting**, pause and give the connection time to recover. Use the recovery action shown if it cannot reconnect. A microphone that disconnects may need to be reconnected or selected again. If starting or resuming reports that the call has already ended, select **Retry**, check your microphone, and select **Start call** or **Answer call**, as shown, to begin a new attempt. Avoid closing or refreshing the tab as a way to end a conversation. If a call was interrupted, return to its attempt before assuming the result was lost or starting over. Microphone access, recording availability, and permission to share audio are different things. Review [recordings and transcripts](https://lira.thoughtly.com/docs/results/recordings-and-transcripts) and [privacy](https://lira.thoughtly.com/docs/workspace/privacy) for what can be retained or shared. Need help? Start with [audio](https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio) or [connection troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/connection). --- # Create and share a scenario > Describe a conversation, refine its brief, and choose how to share it. Source: https://lira.thoughtly.com/docs/practice/private-prep Audience: everyone Last reviewed: 2026-11-12 Every workspace member can create a scenario for an upcoming conversation. All scenarios live in **Scenarios** and start **Private to you**, including when an admin creates one. You can use the same scenario privately, share it with coworkers, or publish it as team training when your role permits. ## Describe your conversation Choose **Create scenario** to open the scenario studio. Share a rough idea, choose a practice direction, or describe the person, situation and desired outcome in the message box. Lira looks for relevant public information when appropriate, then asks follow-up questions before building. Say “don’t browse” to skip public web research. Answer the questions or use the × on the question card to skip the rest and continue with what you have shared. **Add a product link** prepares a request you can finish with a public website. Everyone uses this same flow, including managers creating team training. Opening New does not create a draft; the first accepted request does. Unsent text stays available during the workspace session and clears on refresh, workspace changes, or sign-out. See [answer a follow-up question](https://lira.thoughtly.com/docs/manage-training/create-scenarios#answer-a-follow-up-question) for more detail. ![A compact sidebar offers a message box, practice directions and Add a product link beside a text-free canvas with faint blue contour artwork.](https://lira.thoughtly.com/docs/images/product/scenario-create.png) Create, test and improve the scenario in one workspace. Send your request to prepare a brief, call settings and scoring rubric. The initial request stays in the conversation while the document takes shape. **Preview · Not saved** identifies changes that are still being prepared; Lira saves them together after validation succeeds. Generation continues if you leave or refresh; reopen the scenario to continue in the same studio. A background creation can notify you without interrupting your current work. Newer changes are not silently replaced, and stopping a job or retrying a failure does not delete the draft. If creation fails, **Edit and retry** returns the request to an empty message box so you can send it again. Review the Pre-Call Brief, goal, skills and call settings before starting practice. Choose **Edit** on an existing scenario to return to Lira. Ask a question, review a test, or request a change; an answer or review can leave the scenario unchanged. As the scenario's author, you can ask Lira to show or explain the counterpart instructions. They are not exposed as a raw editable field or included in learner-facing scenario pages. ## Practice and improve Use **Test call** in the studio to check the scenario before learner practice. Where privacy permits, your private **Test history** keeps simulated feedback and available replay for up to 90 days. **Review with AI** references that exact test in chat so you can discuss it or request improvements. These authoring tests stay out of learner practice history, certificates and rankings. Activity-only feedback remains temporary. See [testing and iteration](https://lira.thoughtly.com/docs/manage-training/create-scenarios#test-the-scenario). Start practice from the scenario overview. Scenarios use the same browser call, recording player, transcript, highlights, and feedback regardless of how they are shared. You can repeat a scenario as often as you need. Each call starts fresh from the creator's scenario. Your counterpart does not receive your earlier practice transcripts, scores, coaching, goal, or rubric. Its manner and patience can vary between calls, and it responds to the questions, answers, and boundaries established within that call. Difficulty adjusts how readily it cooperates, pushes back, interrupts, or leaves. See [starting a fresh conversation](https://lira.thoughtly.com/docs/practice/scenario-overview#start-a-fresh-conversation) for all four difficulties. Return to the scenario's practice history to open an attempt and review available feedback. Retained recordings and transcripts depend on the workspace's privacy policy and the content available for that attempt. A newly created scenario provides grades and feedback. It does not automatically issue an official certificate, create an assignment, submit an attempt, or place private results on the leaderboard. Your workspace’s privacy and retention settings still apply. ## Share the scenario The owner can choose **Share with workspace** once the brief is ready. Coworkers can immediately discover and practice it. The owner and authorized workspace admins can edit the shared brief. Sharing the scenario does not share your previous attempts, authoring tests, recordings, feedback, uploaded files, or private AI generation jobs. Your supporting material remains accessible only to you. Choose **Share** on the scenario overview or **Actions → Workspace access…** in the editor. Select **Private to you** or **Share with workspace**, then save your choice. Opening the panel does not change access. ![The Workspace access dialog offers Private to you and Share with workspace, with an explicit Save workspace access button.](https://lira.thoughtly.com/docs/images/product/workspace-scenario-access.png) Choose and save workspace access without sharing previous practice results. To remove coworkers’ discovery and new-call access, select **Private to you** and save. They retain access to their own completed attempt snapshots and private results. Your scenario stays in your collection for future practice. An authorized manager or admin can choose **Publish** in the editor after reviewing the rubric and certificate requirements, then confirm **Publish training**. This makes the scenario official workspace training and creates a new published version. It does not certify earlier personal attempts or expose your private supporting material. Sharing workspace access alone keeps the scenario personal and does not enable assignments or official certificates. Use the collection's **Filter** menu to find **Private to you**, **Shared with workspace**, or **Created by you** scenarios. Use [folders and Trash](https://lira.thoughtly.com/docs/practice/organize-scenarios) to file scenarios and remove unwanted drafts. Folder names and organization are shared across the workspace. Each folder can contain private and workspace scenarios, but private scenarios stay owner-only, including against workspace admins. Moving a scenario does not share it. Changing access or publishing keeps its folder automatically; use **Move to folder** in the library to change the location. ## Older meeting preparations Saved meeting preparations now open as personal scenarios. Their private ownership, versions, and attempt history are preserved. Existing preparation links redirect to the corresponding scenario; there is no separate preparation collection to maintain. Next: [Read the scenario overview](https://lira.thoughtly.com/docs/practice/scenario-overview) or [review your feedback](https://lira.thoughtly.com/docs/results/feedback-and-scoring). --- # Folders, drafts, and Trash > File scenarios, clean up drafts in bulk, and restore deleted work. Source: https://lira.thoughtly.com/docs/practice/organize-scenarios Audience: everyone Last reviewed: 2026-10-30 Open **Scenarios** to organize the library with folders and the **Available**, **Drafts**, **Closed**, and **Trash** views. Use **Grid** or **List** for the directory; the same search, filters and actions work in either layout. Your role determines the actions and views available to you. ## File scenarios in folders Each scenario can belong to one folder or remain **Unfiled**. Folders organize the library for everyone in the workspace. Any folder can contain private scenarios and scenarios shared with the workspace. A folder name is an organizing label, not information supplied to the AI conversation. Existing folders keep their names and contents, including folders that already share a name. Rename them to make them easier to distinguish. New folders must have different names within the same location. In Available, Drafts and Closed, each location shows its subfolders followed by the scenarios filed directly there. At **All scenarios**, the scenarios are **Unfiled**. Grid shows folder tiles; List shows folder rows before scenario rows. Use the breadcrumb to return to a parent folder or **All scenarios**. Trash shows deleted scenarios across folders without folder tiles or rows. Inside a folder, its name appears once in the breadcrumb. Cards and list rows omit the repeated location. When a root search finds scenarios across folders, their folder labels remain visible so you can tell them apart. **Recently edited** sorts folders by their latest change, just as it does scenarios. In List, folders also show **Last edited**. A folder’s date includes its own changes, subfolder changes, and edits to scenarios you can access inside it across all views. Empty folders use their own last change. **A–Z** keeps alphabetical ordering. ![Folder rows show Last edited dates and follow Recently edited ordering above scenario rows, with Created by attribution shown for scenarios.](https://lira.thoughtly.com/docs/images/product/scenario-folder-dates.png) Folder dates and ordering follow the latest accessible edit. While a folder loads, the current directory stays visible with a loading indicator. If it cannot load, choose **Try again**; an empty-folder message appears only after the folder has loaded. If a folder contains scenarios but none in the selected view, choose another view. Use **Create scenario** to start a private scenario in the current folder, or move an existing scenario here from **All scenarios**. Named-folder counts include scenarios filed directly there that you can access across Available, Drafts, Closed and Trash. Subfolders keep their own contents and counts. Search and the selected view can therefore show fewer scenarios than a folder's count. Search from the root looks across folders; search inside a folder stays within it. Folder names and organization are shared. Workspace members can create, rename, move, and delete folders. Moving or renaming a folder changes its location for everyone. Each scenario keeps its own access: a private scenario stays visible only to its owner, including when an admin opens the same folder. Counts include only scenarios you can access. Your existing scenario permissions determine which scenarios you can move, edit, or assign. Use **Move to folder** in a scenario's actions, or select its folder label on the scenario page. Search for a folder, then select its row; parent paths distinguish folders with the same name. Choose **Unfiled** to return a scenario to the root. Choose **Move scenario** to confirm. The new location applies to everyone who can access the scenario. Moving never changes privacy, publishes training, or rewrites a scoring standard. Private and workspace scenarios can be moved together into the same folder. To create a destination from the picker, select its parent and choose **New folder**. Enter a name in the next step; the parent location appears below the heading. **Back to folders** returns without creating anything. After creation, the picker selects the new folder. Choose **Move scenario** to finish filing. ![The folder picker shows folder names with their parent paths, a selected destination, New folder, Cancel, and Move scenario.](https://lira.thoughtly.com/docs/images/product/scenario-folders.png) Search or select a destination, then move the scenario. Choose **New folder** to create a folder in your current location. The dialog shows **Location** before you enter its name. There is no folder access setting to choose; all folders use the same shared organization. ![The New folder dialog displays Discovery / First calls as its location before the folder name is entered.](https://lira.thoughtly.com/docs/images/product/scenario-subfolder.png) Create a subfolder in the location you are viewing. Right-click a folder tile or row to open **Rename**, **Move to folder**, and **Delete folder**. On a phone, touch and hold the folder. With a keyboard, focus its link and press **Menu** or **Shift+F10**. These actions appear only for folders you can manage. You can also use **Manage**, where full paths distinguish folders with the same name and **Create in** selects a parent for a new folder. ![The folder context menu offers Rename, Move to folder, and Delete folder.](https://lira.thoughtly.com/docs/images/product/scenario-folder-menu.png) Open a folder’s actions directly from its tile or row. Choose **Rename** from the folder’s menu, or use its pencil button in **Manage**. The **Rename folder** dialog opens with the current **Folder name** selected. Type the new name and choose **Save** to update the shared name and close the dialog. **Cancel** keeps the existing name. If the name is already used in that location, choose another; if someone changed the folder first, refresh and try again. ![The Rename folder dialog has Discovery selected in its Folder name field, with Cancel and Save actions.](https://lira.thoughtly.com/docs/images/product/scenario-folder-rename.png) Enter the new name and save; the dialog closes when the name is updated. Deleting a folder asks you to confirm that it and every subfolder will be removed. Choose **Cancel** to keep the folder. After confirmation, scenarios anywhere in that branch, including those in Trash, become **Unfiled**; their content and access are kept, and no scenarios are moved to Trash by deleting a folder. When you create with a folder selected, the new private scenario uses that folder. From **All scenarios**, a new scenario starts **Unfiled**. Sharing, publishing training, or making a scenario private keeps its folder automatically. To change the location, use **Move to folder** in the library. Filing never changes who can access it. ## Use background actions Right-click empty space in the library to open its actions. On a phone, touch and hold empty space. With a keyboard, focus **Scenario library background**, then press **Menu** or **Shift+F10**. - **New scenario** opens the same studio as **Create scenario** in the toolbar. Opening New creates nothing; sending the first accepted request creates a private scenario in the current folder, or **Unfiled** at **All scenarios**. - **New folder** opens the same folder dialog as the directory action and creates inside the current location. Check **Location** in the dialog before creating it. - **Select all on this page** enters selection mode and checks the current page's scenarios that you can manage. It excludes folders and the larger assigned section, and is unavailable when there are no selectable scenarios or the view is loading. - **Refresh** reloads the current view. It is unavailable while that view is already loading. You can also create a folder with the directory's **New folder** action or enter selection mode with **Select** in the toolbar. A normal click on empty space does not open a menu or create anything. Cards, folder links and search fields keep their own interactions. ![The library background menu offers New scenario, New folder, Select all on this page, and Refresh.](https://lira.thoughtly.com/docs/images/product/scenario-background-menu.png) Open quick actions from empty space without leaving the directory. ## Drag scenarios into folders With a mouse or trackpad, drag a scenario card or row you can manage onto a folder tile or row. Inside a folder, drop onto a parent in the breadcrumb to file it there, or onto **All scenarios** to return it to the unfiled root. Available, Drafts and Closed support filing when you have permission. Trash scenarios must be restored before filing. To move a group, choose **Select**, check scenarios you can manage, then drag one of the selected items. This moves the current page's selection together, including private and workspace scenarios in the same batch. Dragging an item outside that selection moves only that item. For touch or keyboard use, open the scenario's context menu and choose **Move to folder**. Touch and hold a card or row; with a keyboard, focus its link or title and press **Menu** or **Shift+F10**. Choose **Unfiled** in that picker to return a scenario to the root. The same picker is available from the folder label on the scenario page. Filing through either path keeps the scenario's access, conversation, generation and published requirements unchanged. A scenario filed from the root leaves the unfiled results; open its destination folder to find it. ## Move folders With a mouse or trackpad, drag a folder tile or row onto another folder to place it inside. To move it up, drop it onto an ancestor in the breadcrumb, or onto **All scenarios** to move it to the root. The destination highlights before you release. The folder keeps all its subfolders and scenarios. ![Inside Discovery, the Qualification folder highlights as a drop destination for the First calls folder; All scenarios is available in the breadcrumb.](https://lira.thoughtly.com/docs/images/product/scenario-folder-move.png) Drop onto another folder to nest it, or onto a breadcrumb to move it up. Workspace members can move folders. Moving a folder changes the shared organization and keeps each scenario's access unchanged. A folder cannot move into itself, one of its own subfolders, or its current location. A destination with another folder of the same name requires a different name or location. For keyboard or touch use, open the folder's context menu and choose **Move to folder**: right-click it, touch and hold it, or focus its link and press **Menu** or **Shift+F10**. In **Move folder**, select a destination or **All scenarios**, then choose **Move folder**. Paths distinguish folders with the same name; the folder and its descendants are excluded from the choices. **Cancel** leaves it where it was. ![The Move folder dialog for First calls offers All scenarios and other folders, with Discovery / Qualification selected and Cancel and Move folder actions.](https://lira.thoughtly.com/docs/images/product/scenario-folder-move-picker.png) The same folder move is available from the context menu. If the move fails, the folder stays visible and an error explains the next step. Refresh before trying again if another change made the folder out of date. Press **Escape** before releasing a drag to cancel it. ## Clean up several drafts Open **Drafts**, enter a folder if needed, and choose **Select**. The selection bar starts at zero; check scenarios to enable the available actions. **Select all on this page** selects only the current page's scenarios. Folder entries and the larger assigned section are outside this selection. Use **Move to…** to file the selection or **Delete** to move it to Trash. **Cancel** exits selection mode. Changing the view, folder, filters, or page clears the selection. Unnamed drafts appear as **Untitled scenario** in Grid and List. In List, **Created by** helps distinguish authors; **You** identifies your own scenarios. Open a draft to review it before moving or deleting it. In Grid, a checkbox replaces each selectable scenario’s thumbnail while its title stays in place. Canceling selection restores the artwork. ![Two scenario cards in selection mode, one checked and one unchecked, with checkboxes replacing their thumbnails.](https://lira.thoughtly.com/docs/images/product/scenario-selection-grid.png) Select scenarios to move or delete them together. Right-click an individual card or row, or touch and hold it on a phone, to open its actions. With a keyboard, focus the card link or row title and press **Menu** or **Shift+F10**. The scenario page and editor also have an **Actions** button. A bulk action rechecks every selected scenario; a stale revision or changed permission prevents a partial update. Refresh the view and select again if asked. ![Two Untitled scenario drafts are selected below shared folders, with Created by attribution and Move to and Delete actions available for the pair.](https://lira.thoughtly.com/docs/images/product/scenario-selected.png) Move private and workspace scenarios together from the current page. ## Delete a scenario Choose **Delete scenario** from its card, row, scenario page, or editor. Unused drafts move straight to **Trash**. Scenarios with practice history or active assignments show one confirmation explaining the effect on existing training. ![One Trash confirmation explains that an active assignment stops accepting new practice while historical results and active calls are preserved.](https://lira.thoughtly.com/docs/images/product/scenario-delete-impact.png) Review the effect on existing training before moving a used scenario to Trash. Deleting stops new practice and assignment access and cancels pending generation and calls that have not started. Calls already active may finish. Existing results, certificates, recordings and assignment history retain their normal access and retention rules. After deletion, **Undo** is available for ten seconds. You can also restore later from **Trash**. Trashing is recoverable and does not permanently erase historical evidence. ## Restore from Trash Open **Trash** and choose **Restore** from a scenario's actions, or select several rows and restore them together. Restore keeps the previous privacy and Closed status. It does not restart cancelled generation or restore a deleted folder. A scenario whose folder was deleted returns Unfiled. ![The Trash list contains a recoverable fictional private scenario, its creator, deletion date and page count.](https://lira.thoughtly.com/docs/images/product/scenario-trash.png) Trash keeps deleted scenarios recoverable without an automatic expiry. If another person changed a scenario after your view loaded, refresh before restoring it. An old Undo action cannot undo a newer deletion. Trash does not expire automatically in this release. The private **Getting started** example moves here automatically after onboarding. It is read-only and has no **Restore** action; its practice and certificate remain available in **Progress** and **Certificates**. Next: [Create or refine a scenario](https://lira.thoughtly.com/docs/manage-training/create-scenarios) or [find available practice](https://lira.thoughtly.com/docs/practice/scenarios). --- # Practice with live coaching > Get optional suggestions during a desktop call, then practice independently to qualify. Source: https://lira.thoughtly.com/docs/practice/live-coaching Audience: everyone Last reviewed: 2026-11-04 Live coaching is an optional desktop feature for personal and workspace practice. When it is available, a silent coach uses your scenario brief, goal, scoring standards and live conversation to suggest what you could say next. You choose whether to use the suggestion. ## Choose coaching before a call Select **Start practice** and check your microphone and speaker. Once your microphone is ready, choose **Start with coaching** to review guided practice. Read the confirmation, then select **Start coached call**. **Back** returns to your device check with the same microphone settings. To practice independently, use **Start call** instead. Coaching starts off for each new attempt. Your microphone check stays local; the conversation starts only after you choose a start action. ![The microphone check offers Start with coaching beside the normal Start call action, without a coaching toggle or card.](https://lira.thoughtly.com/docs/images/product/live-coaching-setup.webp) Check your devices, then choose how to practice. ![The coaching confirmation explains guided practice and its qualification rules, with Back and Start coached call actions.](https://lira.thoughtly.com/docs/images/product/live-coaching-confirm.webp) Review guided practice before the call starts. Back keeps your device check intact. > **Coached practice does not qualify** > > Coached attempts receive scores and feedback under your workspace's privacy settings and count as practice activity. They cannot earn a certificate, enter leaderboards or complete assigned training. Pausing or switching coaching off does not restore eligibility for that attempt. Start a new independent attempt when you are ready to qualify. ## Read the next suggested response A slim caption rises above the call bar when the coach has a relevant suggestion. It shows the suggested response beside a small coach icon, with no extra heading. The response appears as the coach prepares it. Your page stays available while guidance is visible. Completed suggestions stay visible while you read and speak, including while the coach prepares the next response. A small progress mark shows when the coach is waiting for the next useful suggestion. New suggestions arrive above the call bar as the conversation changes. An unfinished suggestion clears if your reply interrupts it; guidance based on an interrupted counterpart turn is also cleared. The coach does not speak into the call or determine your score. ![A slim navy coaching caption shows one suggested response, a small coach icon and a pause control above the call bar.](https://lira.thoughtly.com/docs/images/product/live-coaching.webp) One timely suggestion appears above the call controls while the page stays available. ![A compact Listening pill with a progress indicator and pause control appears above the call bar while a new suggestion is being prepared.](https://lira.thoughtly.com/docs/images/product/live-coaching-working.webp) When there is no completed suggestion to keep, a small listening indicator shows that coaching is working. ## Pause guidance during a call Choose coaching before starting your call. The call controller keeps Mute and End available without an additional coaching button. Close the caption or press **Escape** to pause coaching. Your call continues. Coaching stays paused for the rest of that call; you can choose it again before your next call. Opening another dialog keeps its usual keyboard behavior. Coaching is absent from the full-screen mobile call experience and from author test calls. Moving an active coached call into the mobile layout pauses guidance for the rest of the call. The attempt remains coached. ## If guidance is unavailable The voice call continues if coaching is slow or temporarily unavailable. An availability message appears in the call bar. You can finish the conversation and choose coaching again before your next call. This remains a coached practice attempt. If no coaching choice appears, you can continue with ordinary practice. After the call, open your [feedback](https://lira.thoughtly.com/docs/results/feedback-and-scoring). For device help, see [microphone and audio troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio). --- # Understand feedback and scoring > Read your results, use the evidence, and understand what makes an attempt qualify. Source: https://lira.thoughtly.com/docs/results/feedback-and-scoring Audience: everyone Last reviewed: 2026-10-29 Open an attempt from **Progress** or a scenario's **Recent attempts** to see its result. The attempt keeps the scenario version and scoring requirements used for that conversation. **Test call** inside the scenario editor is a private authoring test. Where privacy permits retention, its simulated feedback can be reopened from **Test history** for up to 90 days; closing it does not delete it. Activity-only feedback remains temporary. These tests do not add a learner result to Progress, earn a certificate or enter rankings. See [test a scenario](https://lira.thoughtly.com/docs/manage-training/create-scenarios#test-the-scenario). ![Practice a conversation, review your private feedback, then choose your next step.](https://lira.thoughtly.com/docs/images/review-loop.svg) One conversation. One useful improvement. Repeat at your own pace. ## Before your first attempt An empty **Progress** page introduces the practice and feedback cycle. Choose **Practice a scenario** to open your available scenarios. Your attempts and private feedback will appear in Progress after you practice. ![An illustrated No practice history yet panel with a Practice a scenario action and three steps for practicing, reviewing feedback, and improving.](https://lira.thoughtly.com/docs/images/product/progress-empty.webp) Your first conversation starts your practice history. ## Find a previous attempt On **Progress**, search appears below your summary cards, followed by **Filter**. Narrow the history by scenario or outcome, then select a scenario title to open its attempt. The count and page controls sit below the table; searching or filtering returns you to its first page. ![A bordered Search results field followed by Filter, with Explore scenarios on the right.](https://lira.thoughtly.com/docs/images/product/progress-toolbar.png) Find a past practice call using the same controls as the other collection pages. ## Start with the outcome After the call ends, **Call complete** confirms that Lira is preparing your feedback. This page updates automatically; you can leave and return to the same attempt. Recording and transcript sections appear only when that content is available, so you may see feedback before the recording finishes saving. ![Call complete followed by Preparing your feedback and a note that the page updates automatically, with no empty recording or transcript panels.](https://lira.thoughtly.com/docs/images/product/call-complete.webp) Your call has ended. Feedback appears automatically when the review is ready. The result shows your performance score and whether the attempt met its certificate requirements. For results with saved feedback, the score can appear before the written coaching finishes. An earned training certificate can open as soon as the validated result is saved; it does not wait for the coaching text or recording. Every completed conversation with usable captured dialogue receives a score, including short calls and calls ended by the counterpart. A skill you did not demonstrate receives **0** and remains part of the overall average. This applies to custom skills too. **Not scored** is reserved for attempts that could not be evaluated, such as an unconnected call, unavailable conversation evidence, or unsuccessful feedback processing. It is different from poor performance. ![An overall score of 88 with Requirements met and a breakdown of four individual skill scores.](https://lira.thoughtly.com/docs/images/product/feedback-scores.webp) Review the overall result and the individual skills that contributed to it. This example uses demonstration data. ## Read coaching as it arrives When **Preparing your coaching…** appears beside a saved result, the summary, skill observations, and next steps fill in as they are written. You can begin reviewing the score and its supporting evidence while that text arrives. Written coaching explains the saved grades; it does not change your score, goal outcome, or certificate eligibility. ![A saved score of 87 out of 100 above a partially written summary and Preparing your coaching status.](https://lira.thoughtly.com/docs/images/product/coaching-streaming.png) Your score is saved while written coaching continues to arrive. This example uses demonstration data. You can leave and return to the same attempt. Reopening or refreshing reconnects to the latest saved feedback without placing another call or restarting grading. If the connection is interrupted, the page checks for updates automatically. In **Activity only** mode, feedback continues to arrive as one temporary result and remains subject to its existing delivery window. If the page says **Written coaching couldn’t be prepared. Your score is still available.**, the score and any earned certificate remain available according to your privacy settings. Use the rubric and available evidence to choose your next practice focus. See [feedback troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/feedback) for the difference between missing coaching and an unavailable score. ## Recover unavailable feedback A completed call can temporarily have feedback unavailable even when its recording or transcript is ready. Lira attempts automatic grading recovery. If the result says **We couldn’t prepare feedback**, choose **Retry feedback** when offered to retry that same conversation once, without placing another call. The control belongs to the caller and requires the original temporary evidence to remain available; it does not extend retention or allow regrading a completed score. If recovery is unavailable or still fails, review any permitted playback and choose **Practice again** for a new conversation. A grading error is not a zero performance score. See [feedback troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/feedback) for access, expiry, and missing-media guidance. ## Review the skills Select a skill to see what happened in the conversation, the supporting moments, and what to try next. When retained call content is available, play a highlight to hear it in context. Use feedback as a practical coaching aid. If a comment seems surprising, compare it with the transcript, recording, and written scoring standard. AI feedback can be imperfect; your manager can help you interpret a submitted result. ## How qualification works - Skills are scored out of 100. The overall score is their equally weighted average, including zeros for skills not demonstrated. - A scenario can require a minimum overall score, individual skill minimums, and achievement of its goal. - All required conditions must be assessed and met **in the same attempt**. - Displayed scores may be rounded. Qualification uses the underlying value, so a rounded number alone does not establish that a minimum was met. A score can still be available when part of the conversation was not captured. It reflects the available dialogue; incomplete evidence cannot establish certificate eligibility. **Capture incomplete** explains when this prevents a certificate, even if the displayed score meets every grading requirement. Review the available feedback and replay, then choose **Practice again** to start a new call. Regrading cannot restore missing conversation. ![A fictional result keeps its score of 100 visible while explaining that incomplete call capture prevents certification and that Practice again starts a new call.](https://lira.thoughtly.com/docs/images/product/incomplete-call-capture.png) A passing score needs complete call capture before the attempt can earn a certificate. Your certificate requirements are shown with the result. Scores from separate attempts are not combined to qualify. > **Choose one next step** > > Pick a specific change, such as asking a follow-up question before recommending a solution. Then use **Practice again** to try it in a new conversation. See [certificates](https://lira.thoughtly.com/docs/results/certificates) for credential details and [feedback troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/feedback) if your result is missing or incomplete. --- # Review recordings and transcripts > Replay the conversation, follow the transcript, and jump directly to useful moments. Source: https://lira.thoughtly.com/docs/results/recordings-and-transcripts Audience: everyone Last reviewed: 2026-10-28 An attempt brings the available recording, transcript, and feedback together. Recording and transcript availability depend on the content saved for that call, workspace privacy, and retention. For an authoring **Test call**, open the test card or **Test history** in the scenario studio. Only the person who made that test can access it; sharing the scenario does not share its tests. Permitted test recordings, transcripts and feedback have a maximum 90-day cutoff. Activity-only tests do not retain media. See [test review and iteration](https://lira.thoughtly.com/docs/manage-training/create-scenarios#reopen-and-replay-a-test). Long scenario labels above the recording title stay on one line. Hover over the label to read its full text. ![Recording playback with scenario artwork beside a transcript showing speakers and timestamps.](https://lira.thoughtly.com/docs/images/product/recording-and-transcript.webp) Play the recording and follow the transcript alongside it. Select a timestamp to revisit that moment. ## Listen with the transcript Select the play control to start the recording. Use the timeline to seek, the 10-second controls to move backward or forward, and the playback-speed menu to listen at a comfortable pace. The transcript follows the conversation during playback. Where timing data is available, the active passage and words are highlighted as the recording plays. If you scroll to read elsewhere, you can return to the playback position using the transcript's follow control. Select a timed transcript passage or a highlight's play button to jump to that part of the recording. Highlights connect the feedback to specific moments instead of requiring you to search the whole conversation. ## Understand missing content The attempt shows only the media that is available. If just the transcript is ready, it fills the review area; a missing recording does not leave an empty player beside it. If neither is available, you can still review the feedback without empty media panels. An opted-in browser recording can appear shortly after the score. ![A full-width transcript showing the learner and AI counterpart, with no empty recording player.](https://lira.thoughtly.com/docs/images/product/transcript-only.webp) Read an available transcript on its own while the recording is saving or when audio was not retained. | State | What to do | | --- | --- | | Recording or transcript has not appeared | Review the feedback or media that is available. Reopen the attempt later if content is still saving. | | No recording saved | Read the transcript or feedback that is available; not every call has retained audio. Public replays explain when media was not retained. | | Recording could not be loaded | Press play to retry after checking your connection. | | Transcript is no longer available | Access or retention may have changed; refreshing cannot restore deleted content. | Audio and transcript are separate. A missing recording does not necessarily mean the transcript or feedback is missing too. > **Reviewing does not publish** > > Playing your own recording does not share your attempt. In Submitted results mode, choosing **Share** creates a public replay link and enables leaderboard playback when recorded audio is available. Workspace privacy and retention rules still apply. Public replays show the available overall score on the player. Detailed skill scores, coaching feedback, and the scoring rubric remain private. Read [submitting and sharing](https://lira.thoughtly.com/docs/results/submitting-and-sharing) before sharing a replay, or [privacy](https://lira.thoughtly.com/docs/workspace/privacy) to understand retention and access. --- # Share a practice attempt > Share a completed scenario attempt, copy its replay link, and change access later. Source: https://lira.thoughtly.com/docs/results/submitting-and-sharing Audience: everyone Last reviewed: 2026-10-23 Practice starts private. Review the result before choosing to share it. You can share completed training attempts from any scenario, whether assigned or started directly from Practice. You do not need to pass the scenario or earn its certificate first. Private meeting prep and author test calls are not training submissions, and workspace privacy settings still apply. ## Share an attempt In **Submitted results** mode, open the attempt and select **Share**. Read the dialog, then confirm **Share attempt**. This action: - Makes the available score, feedback, and call content accessible to authorized reviewers. Managers can review people they manage; workspace admins have workspace-wide reviewer access. - Adds the available score to enabled [leaderboards](https://lira.thoughtly.com/docs/results/leaderboards). Your highest shared score is used for your ranking. An attempt without a score can be shared, but does not receive an invented ranking score. - Creates a public replay link showing the available conversation and overall score. When recorded audio is available, sharing also enables playback from the leaderboard. ![Share attempt dialog explaining that sharing adds the available score to the leaderboard and lets anyone with the link replay the conversation, with Cancel and Share attempt actions.](https://lira.thoughtly.com/docs/images/product/attempt-sharing.webp) Confirm Share attempt to add your available score to the leaderboard and create an unlisted replay link. Use **Copy link** in the confirmation dialog. You can reopen **Share** later to copy the link again. ## Understand who can open the link **Anyone with the replay link can open it without signing in.** The page shows your name, the scenario title, the available overall score, and the available recording and transcript. The overall score appears in the top-right corner of the replay player. Detailed skill scores, coaching feedback, and the scoring rubric remain private. ![Public replay player for the fictional Handle pricing pushback scenario with a tilted 88 out of 100 overall-score badge in its top-right corner and messages that no recording or transcript was retained.](https://lira.thoughtly.com/docs/images/product/public-attempt-replay.webp) The public page shows the available overall score even when no recording or transcript was retained. Fictional example shown. Replay links are unlisted and excluded from search indexing. That does not prevent someone who has the link from forwarding it. Copy the replay link from **Share**, rather than the private attempt URL in your browser's address bar. If no recording or transcript was retained, the shared page explains that the conversation content is unavailable. Sharing does not restore expired or deleted content. An attempt without a saved assessment remains shareable by link, but does not appear in reviewer queues or scored rankings. Its public page does not invent a score. Sharing does not recreate an assessment that was never saved or has expired. ## Change access Select **Turn off link** in the sharing dialog to revoke public access. This leaves the submission available to authorized reviewers and eligible leaderboards. Creating another link produces a new URL; the old link stays unavailable. To remove submission-based reviewer and ranking access as well, use the withdrawal control on the attempt. Withdrawal also revokes its replay link. It does not undo an earned certificate or restore content that has expired. ## Other privacy modes - In **Anonymous team scores** mode, select **Submit** and consent to contribute to anonymous team rankings. This does not create a public replay link or named reviewer access. - **Activity only** mode does not offer saved-result sharing or public replay links. See [privacy](https://lira.thoughtly.com/docs/workspace/privacy) for the effect of workspace privacy changes and [certificates](https://lira.thoughtly.com/docs/results/certificates) for the separate certificate-sharing flow. --- # Earn and share certificates > Find your credentials, share a prepared LinkedIn post, and control public certificate access. Source: https://lira.thoughtly.com/docs/results/certificates Audience: everyone Last reviewed: 2026-10-28 Your **Getting started** certificate recognizes your first completed practice. It has no passing score, required objective, or expiry, and stays private until you choose to share it. It does not complete an assignment or affect team rankings. Your **Getting started** certificate and new training certificates use the same full-screen award, with the certificate presented in an envelope. Close it when you are ready to continue; the certificate remains in your collection. During onboarding, **Continue** opens your workspace and the quick tour. Closing the award or pressing **Escape** enters without starting the tour. ![A first-certificate example for fictional Jordan Rivera shows the shared envelope presentation, Continue, and a borderless Share on LinkedIn action below it.](https://lira.thoughtly.com/docs/images/product/linkedin-first-award.png) First-certificate example of the shared award design. Training awards use View Results. The optional LinkedIn action sits below the award's main button. A training award offers **Share on LinkedIn** below **View Results**. When connected sharing is available, your first award offers **Connect LinkedIn & share**, or **Share on LinkedIn** if you have already connected, below **Continue**. You can close sharing to return to the award, or continue and share later from **Certificates**. Other certificates record that you met a training scenario's requirements. Those requirements can include an overall score, individual skill minimums, and the scenario goal. ![A fictional Getting started certificate for Alex Rivera with the Northstar logo above the award title, as rendered in the downloaded certificate.](https://lira.thoughtly.com/docs/images/product/certificate-logo.png) Your uploaded logo appears on the certificate and its exported image. ## Earn a certificate Open the scenario's certificate requirements before practicing. Meet every requirement in one qualifying training attempt. Requirements are not combined across attempts, and private meeting prep or author test calls do not award training certificates. When a qualifying attempt belongs to an assignment, it also completes that assignment. You do not need to submit the attempt or publish the certificate for that completion to count. Certificate completion can be retained even when the workspace does not retain detailed scores. After your current browser or phone practice earns a new certificate, the shared award opens once that certificate is ready. Choose **View Results**, close it, or press Escape to dismiss the award and stay on the same results page. Your score and feedback remain visible, and keyboard focus returns to the results heading. Opening the sharing dialog does not dismiss the award. ![A newly earned fictional training certificate appears in the shared envelope award with View Results above Share on LinkedIn.](https://lira.thoughtly.com/docs/images/product/training-certificate-award.png) View Results dismisses the award and keeps your results on the same page. If you reload the same tab while the result is still processing or before dismissing the new award, Lira can restore it when the certificate is ready. Opening an older completed result or returning to an acknowledged award does not replay it. The certificate remains in **Certificates**. ## Find and download it Open **Certificates** in the sidebar, or open the certificate from a qualifying result. Review the recipient, issuer, issue date, and expiry before sharing. Use **Download PDF** to save a copy. Certificate dates stay the same in your collection, sharing details, public verification page, and downloaded PDF, even when you view them from another time zone. Your workspace logo appears on the certificate and its downloaded or shared copies. If no logo was saved when it was issued, the certificate uses your workspace's current uploaded logo. Certificates with saved artwork keep their original logo. If a logo is unavailable, the issuer name is shown instead. Search your collection by title or issuer. Open **Filter** beside search to choose **Valid**, **Expired**, or **Revoked**, or clear it to return to all statuses. **Explore scenarios** stays on the right of the toolbar. ![A bordered Search certificates field followed by Filter and an Explore scenarios action.](https://lira.thoughtly.com/docs/images/product/certificates-toolbar.png) Search and status filters sit together above your certificate collection. A scenario may issue a certificate with an expiry date or no expiry. Expired and revoked certificates are different from currently valid credentials; check the status shown on the certificate. ## Share on LinkedIn Open **Share certificate**, or **Share** in your certificate collection. The dialog shows your certificate, **Share on LinkedIn**, and **Copy link**. Lira prepares the caption and certificate link automatically, so you can share without typing anything. When connected sharing is available: 1. Choose **Share on LinkedIn**. If your account is not connected, complete LinkedIn's sign-in and permission steps, then choose **Share on LinkedIn** again when you return. Connecting alone does not publish anything. 2. To check the account or change the caption first, open **Sharing options → Review or edit post**. Before connecting, this option is called **Preview post**. Use **Back to certificate** to return; your edits are preserved. 3. When connected, **Share on LinkedIn** makes the certificate public and sends the prepared or edited post to your LinkedIn feed. If your workspace has configured an issuer company page, the optional post review shows its **Company tag**. Keeping its `@Page name` in the caption includes the tag; removing it leaves the company untagged. ![The Share certificate dialog shows the certificate with Share on LinkedIn and a smaller Copy link action underneath, plus Sharing options in the header.](https://lira.thoughtly.com/docs/images/product/certificate-sharing.png) Share your achievement on LinkedIn or copy its public link. Each post requires your action. Connecting does not turn on automatic posts or add certifications to your LinkedIn profile's credentials section. If you prefer to use LinkedIn's own composer, open **Sharing options** and choose **Share through the LinkedIn website instead** before connecting. When connected sharing is unavailable, **Share on LinkedIn** uses that website flow directly. It makes your certificate public and opens LinkedIn with its verification link. LinkedIn may show the certificate image as a link preview; add your caption and finish publishing there. Lira cannot prefill that website composer or confirm whether you posted. ## After publishing A confirmed post opens **Shared on LinkedIn** with your certificate and **View LinkedIn post**. Use that action to see it on LinkedIn, or close the dialog when you are finished. **Copy link** remains below the main action when you want to share the credential elsewhere. ![Shared on LinkedIn presents a fictional certificate, View LinkedIn post, and a smaller Copy link action, with Sharing options and Close in the header.](https://lira.thoughtly.com/docs/images/product/linkedin-share-success.png) Open your confirmed post, copy the certificate link, or close the dialog. ## Share a direct link Choose **Copy link** below the LinkedIn button to make the certificate public and copy its verification link. Send it by email, chat, or anywhere you want to share it. Apps that support link previews can show the certificate image too. If clipboard access is blocked, the dialog shows a selectable certificate URL so you can copy it directly. The raw URL stays hidden after a successful copy. Closing the dialog before sharing keeps a private certificate private. ## Manage privacy and your connection Open **Sharing options** (the three-dot button in the header) to review the certificate's public-access status. Choose **Make certificate private** to turn off the public verification page and its preview image. The certificate stays in your collection. Your LinkedIn post and its uploaded image are separate copies: making the certificate private or disconnecting LinkedIn does not remove them. Manage or delete those copies on LinkedIn. Choose **Sharing options → Disconnect LinkedIn** to stop Lira using that LinkedIn connection. You can connect again later. If access expires or LinkedIn rejects the connection, choose **Share on LinkedIn** to reconnect. Disconnecting does not make a public certificate private. Other sites may keep images they already cached or that someone saved while the certificate was public. ## If sharing does not finish If the dialog says the post is being published, choose **Sharing options → Check status** after a moment. If it says **Check your LinkedIn profile**, LinkedIn did not confirm the result. Choose **Open LinkedIn** and check your activity before posting again, or use **Sharing options → Check status** to refresh Lira's result. Lira does not automatically resend a post with an uncertain result. ![Check your LinkedIn profile explains the unconfirmed result above a fictional certificate, Open LinkedIn, and Copy link, with Sharing options in the header.](https://lira.thoughtly.com/docs/images/product/linkedin-share-unknown.png) Check LinkedIn before posting again when the result is unconfirmed. A confirmed failure keeps your draft so you can correct it or reconnect. If the website composer cannot display a preview, its service may be unable to reach the certificate URL. You can still use the public verification link; a private preview address is not reachable by LinkedIn. > **A certificate is not a replay** > > Publishing a certificate does not publish your recording, transcript, or full feedback. Those have a separate submission and replay-sharing flow. A LinkedIn post contains only the prepared or edited caption, the certificate image, and the verification link. If qualification seems incorrect, compare the attempt with [the scoring requirements](https://lira.thoughtly.com/docs/results/feedback-and-scoring) and contact your workspace admin. --- # Understand leaderboards > See how shared practice scores are ranked and how workspace privacy affects People and Teams views. Source: https://lira.thoughtly.com/docs/results/leaderboards Audience: everyone Last reviewed: 2026-10-27 Leaderboards use training results learners choose to share. Assigned and standalone scenario practice both count, including attempts that did not pass. Private, unshared practice and private personal practice are excluded. ![Three fictional participants ranked with shared scores of 88, 76, and 47, including an attempt below the passing score.](https://lira.thoughtly.com/docs/images/product/leaderboard.webp) Shared scores can enter the leaderboard without a passing result. This example uses fictional participants. ## What earns a place Complete a scenario, review the result, and choose **Share** on the attempt. You do not need an assignment, a passing score, or a certificate. A person's highest shared score is used for their ranking. Team rankings average the member scores represented in the ranking. An attempt marked **Not scored** can have a replay link, but cannot enter the scored rankings until a score is available. Lira does not substitute zero for a missing score. Use the available scenario or team filters to compare the relevant results. Different scenarios can assess different skills and requirements, so always check what the selected view represents. ## People and Teams **People** displays named rankings when the workspace uses Submitted results mode and the People leaderboard is enabled. **Teams** is available when enabled and allowed by the privacy mode. In Anonymous team scores mode, contributors must consent, and a team needs at least five consenting contributors before an aggregate is shown. There is no individual score drilldown in that mode. Workspace admins manage ranking preferences under **Privacy & rankings**. Depending on those settings and available results, you may see one view, both views, or no rankings. ## Why a result may not appear - The attempt has not been shared or does not have an available score. - A higher shared score already represents the person in the selected view. - You are viewing a different scenario or team. - The submission was withdrawn, access changed, or its eligible data expired. - Rankings are disabled or a privacy threshold has not been reached. Earning a certificate alone does not share your score. In Submitted results mode, **Share** also enables leaderboard playback when recorded audio is available. Turning off the public replay link leaves the shared leaderboard result in place; withdrawing the submission removes it. An empty leaderboard is an invitation to practice, not evidence that an existing private attempt has disappeared. Learn about [submitting an attempt](https://lira.thoughtly.com/docs/results/submitting-and-sharing) or [workspace privacy](https://lira.thoughtly.com/docs/workspace/privacy). --- # Create and edit scenarios > Turn a repeatable conversation into a clear practice brief with meaningful scoring. Source: https://lira.thoughtly.com/docs/manage-training/create-scenarios Audience: everyone Last reviewed: 2026-11-12 Every member can create a [personal scenario](https://lira.thoughtly.com/docs/practice/private-prep), which starts private. Managers and admins can also author workspace training with assignments and certificate requirements. Managers can edit their training; admins can manage shared workspace scenarios. Another member’s private scenarios and source files remain unavailable to admins. ## Start with a goal Open **Scenarios** and choose **Create scenario**. The studio opens with a compact set of starting options and a message box beside an empty scenario canvas. Start with what you want someone to get better at: explaining value, troubleshooting a problem, or handling a difficult conversation. Share a rough idea in the message box and let the conversation help you define the goal, the person and situation, and what good performance looks like. Already know what you want? Type a complete description and send it. The same conversation handles both starting points. The sales, support and difficult-conversation examples fill the message box without sending, so you can change them first. You can also right-click empty space in the library and choose **New scenario**. This opens the same studio and uses the same [folder rules](https://lira.thoughtly.com/docs/practice/organize-scenarios). Send your request with the arrow button or Enter. Use Shift + Enter for a new line; ⌘/Ctrl + Enter also sends. Lira looks for relevant public information when appropriate, then asks focused follow-up questions before building the counterpart, brief, goal, call settings, and scoring rubric. Say “don’t browse” to skip public web research. Answer as much as you like, or use the × on the question card to skip the remaining questions and continue with the details already provided. Everything continues in the same conversation; test calls become available after the scenario is configured. The first accepted request creates a private draft; opening New does not create a record or start a call. You do not need to choose between personal practice and official training first. Scenarios start private for every role, including managers and admins. Unsent text is kept during the workspace session; refresh, workspace changes, and sign-out clear it. ![A compact creation sidebar offers a message box, practice directions and Add a product link beside a text-free canvas with faint blue contour artwork.](https://lira.thoughtly.com/docs/images/product/scenario-create.png) Share a rough idea or a complete description in the same conversation. ### Answer a follow-up question Before building a new scenario, Lira shows a question card in the chat to clarify details such as the goal, situation, or what success looks like. Choose a suggested answer or type your own in the field below the choices. Some questions let you select several answers. **Continue** moves to the next question; leave it blank to skip that question. **Back** lets you revise your choices before **Send answers** continues the conversation. The × in the card’s upper-right corner skips the remaining questions and asks Lira to proceed, preserving any answers already entered. Lira can also ask a question during a later edit when a missing detail matters. You can ignore a card and send a normal message, such as asking Lira to build with reasonable choices. Earlier questions stay readable in the conversation. Reopening the draft restores its latest questions, but unsent selections can reset when you leave or refresh. Your answers use the same private authoring history and permissions as other messages; they do not publish or share the scenario. If an answer cannot be sent, retry from the question card or use **Retry message** beneath the message. ![A question card asks what the learner should practice, with suggested choices, a free-text field, Continue, and a close button to skip the questions.](https://lira.thoughtly.com/docs/images/product/scenario-questionnaire.webp) Choose an answer or add your own without leaving the scenario conversation. ### Bring in your product Paste a public website or product page and ask Lira to use it. For example: “Use this product page to build an inbound troubleshooting call,” followed by the URL. **Add a product link** puts a starter request in the message box and preserves anything you already wrote. Add the URL and send when ready. Lira can research public product details and support information, then use those facts in the scenario. You can also describe a fictional product, supply the relevant context yourself, or say “don’t browse.” Research is used when it helps your request, not for every wording or grading change. ### In a new workspace After your private [Getting started practice](https://lira.thoughtly.com/docs/get-started/first-practice), create team training here. Company and product setup are not onboarding steps. Review the generated scenario, then explicitly publish it as training when it is ready. The private starter scenario cannot be edited, shared, or turned into team training. ## Follow the activity Your initial request stays in the editing conversation as the scenario takes shape. **Thinking** contains short public progress summaries and folds away when the work finishes; reopen it to review the activity. Text appears in the brief, grading and call settings while Lira writes. **Preview · Not saved** means the visible changes are temporary until the complete update passes validation and saves together. Public research includes source links you can inspect. Activity does not expose private model reasoning or claim research that did not happen. ![The creation conversation sits beside a fictional scenario with Preview · Not saved in the toolbar.](https://lira.thoughtly.com/docs/images/product/scenario-generating.png) The first request and unsaved preview stay together while Lira works. Include a public product website, such as `https://example.com`, or ask Lira to find missing public product facts. It can search, read public pages or documents, and compare relevant sources. Private prompts, source content and test transcripts are not sent to the web search service. If research is unavailable, Lira tells you and works from the context already available. ![A compact Thinking section shows completed web research, an expandable source link, and a running text simulation.](https://lira.thoughtly.com/docs/images/product/scenario-agent-tools.webp) Follow the actual work and open the sources used by Lira. You can leave the page or refresh while accepted work continues. Reopen the same scenario or its notification to return to the studio. A background creation can notify you when it is ready; foreground edits report their result in the conversation. **Stop** stops the current job without deleting the draft. If creation takes too long or otherwise fails, **Edit and retry** returns your request to an empty message box; the last saved draft remains unchanged. On larger screens, **Setup incomplete** marks a draft that is not ready to test. Correct the request or unavailable sources and send it again. Unfinished work remains in **Drafts**, where you can also [remove unwanted drafts](https://lira.thoughtly.com/docs/practice/organize-scenarios). Processing knowledge sources can delay generation until they are ready. If the scenario finishes but a requested check or review takes too long, Lira can save the validated scenario and tell you that the follow-up did not finish. Review the saved scenario and ask for the check again when ready. ![A stopped creation keeps the original request above a Creation stopped message and an Edit and retry action.](https://lira.thoughtly.com/docs/images/product/scenario-recovery.png) A stopped or failed request leaves a clear way to continue. ## Review and refine When generation finishes, review the saved scenario in the same studio. There is no extra acceptance screen or automatic call. It stays private. AI can suggest a fictional counterpart, but product claims still need your review. While you follow the live draft, the scenario canvas gently returns to the heading when creation finishes. Scroll, touch or use the keyboard to stop that movement. If you have already scrolled away to read, your position stays under your control. Reduced motion returns to the heading immediately. The conversation and any unsent follow-up stay in place. ![The completed scenario canvas starts at its heading, with call settings and the pre-call brief ready to review.](https://lira.thoughtly.com/docs/images/product/scenario-created.png) Review the saved scenario from the top after creation finishes. Choose **Edit** on an existing scenario to refine the scenario in chat. The page shows the **Pre-Call Brief**, call settings, grading objective and rubric, so you can see what learners will receive. Ask **Lira** for a change: “Make the customer less patient,” “Use an inbound support call,” or “Grade how clearly I explain the next step.” The scenario name appears in the breadcrumb at the top. **Back to scenarios** returns to the catalog; the studio toolbar keeps the saved state and call actions together. ![The scenario title appears in the top breadcrumb, with a standalone Back to scenarios link below and call actions on the right.](https://lira.thoughtly.com/docs/images/product/scenario-studio-navigation.webp) The scenario name stays in the breadcrumb while the studio toolbar stays clear. The settings panel shows the maximum call length, what the difficulty means, and the selected voice and language. Select the voice name to open the voice picker, where you can browse and preview the available voices. The play button beside the selected voice gives you a quick English sample without starting a call or changing the scenario. Select it again to pause. Choose a voice and select **Use** to request the change in the editing conversation. On smaller screens, **Chat** opens so you can follow the update or retry a failed request. Your unsent message stays in place, and the saved voice changes when Lira completes the update. Closing the picker without choosing **Use** leaves the scenario unchanged. ![The scenario title and three-column call settings sit over full-width artwork. The settings show maximum call length, Expert difficulty with its current description, and voice with a play button and language.](https://lira.thoughtly.com/docs/images/product/scenario-call-settings.webp) Preview the selected voice before testing the scenario. ![A searchable voice picker with playable samples, Marin selected, and Cancel and Use Marin controls.](https://lira.thoughtly.com/docs/images/product/scenario-voice-picker.png) Compare voice samples, then confirm the voice you want. Other underlined settings and help icons offer an explanation and example requests for Lira. Hover, focus a help control with the keyboard, or tap it on a phone; press Escape or tap outside to close it. Use an example as your next chat message when you want a change. Opening help does not change the scenario. For example, **Valid for 365 days** describes certificate expiry, measured from when a training certificate is earned. Its help shows how to ask for certificates that stay valid indefinitely or expire after 30 days. Skill-weight help shows how to give a skill more influence or return all skills to equal weighting. ![Certificate expiry help appears next to Valid for 365 days, with example requests to keep certificates valid indefinitely or expire them after 30 days.](https://lira.thoughtly.com/docs/images/product/scenario-setting-help.webp) Understand a setting and find a useful way to ask Lira to change it. You can also ask a question or request a review. Lira can answer without changing the scenario. When you request an edit, it changes the relevant fields without rewriting unrelated settings. Changes save together after validation, and the final reply explains the result. A conversational answer does not create a new scenario version. **Grading** brings the objective, passing requirements and skill criteria together. Each skill shows its share of the overall score with a percentage and a small bar. Skills count equally by default. Ask Lira to change their importance—for example, “Make the first skill count for 40% and split the rest equally.” The percentages show each skill’s contribution, not a score already earned. Weighting does not change a skill’s individual passing minimum or whether the objective is required. Choose **View standards** to read the full expected behaviors and example, with no additional expansion needed. Those panels stay open if Lira edits them. ![One grading panel with the objective, passing score and two skills, each contributing fifty percent of the overall score.](https://lira.thoughtly.com/docs/images/product/scenario-grading-rubric.webp) Review the objective, passing requirements and contribution of each skill. ![An expanded skill rubric showing expected behaviors and an example, with a softly highlighted field while Lira edits it.](https://lira.thoughtly.com/docs/images/product/scenario-grading-standards.webp) See expected behaviors and examples in View standards. Starter suggestions appear above the message box when you open the editor, including scenarios with an existing conversation. After a reply, contextual suggestions can replace them. Select a suggestion to fill the message box without sending; review or edit it first. Suggestions fade away as you start a draft and return when the box is empty. Press Enter to send and Shift + Enter for a new line. The compact message box expands for longer requests, and you can keep a draft while Lira works. If you scroll back through the conversation, **Latest update** returns to the newest reply. **Update failed** means the update could not finish; **Stopped** means it was cancelled. In either case, **Edit and retry** puts the earlier request back in an empty composer; a newer unsent draft is preserved. ![A failed scenario update shows Update failed, confirms that the saved scenario is unchanged, and offers Edit and retry.](https://lira.thoughtly.com/docs/images/product/scenario-update-failed.png) A failed update is distinct from one you stopped, and keeps a way to retry. ![Make it more challenging and Improve the grading suggestions above the empty scenario chat input.](https://lira.thoughtly.com/docs/images/product/scenario-chat-suggestions.webp) Start with a suggestion or write your own request. If a message could not be sent, choose **Retry message** beneath that message. Lira retries the original request and keeps any newer text in your message box. Routine edits use the scenario and available context. For fresh research, ask Lira to check current information or include a public source URL. Say “don’t browse” to skip public web research. Edit keeps the app navigation alongside one scenario document and a compact conversation. Use **Back to scenarios** to return to the catalog with its filters. Until the scenario is configured, smaller screens open **Chat** so Lira’s next question is visible. Choose **Scenario** or **Chat** to switch between the document and conversation. Your unsent message stays in place. Each pane scrolls independently, and the message composer stays at the bottom of Chat. The conversation fades softly behind the suggestions and input as you scroll; the latest reply remains readable above them. ![Conversation text fades softly behind follow-up suggestions above the message input.](https://lira.thoughtly.com/docs/images/product/scenario-chat-gradient.webp) Read the conversation while keeping the message box within reach. A compact **Sending…** or **Thinking…** line appears where Lira’s reply will arrive, with a subtle shimmer while work is underway. While Lira is getting started, only **Thinking…** appears. Activity details become available once Lira has progress to show, and you can keep writing your next message. You can also start a draft while your saved conversation loads; suggestions do not move the loading label. Reduced motion keeps the text and progress mark still. ![A request to clarify the pre-call brief with a compact Thinking… status beneath it.](https://lira.thoughtly.com/docs/images/product/scenario-chat-waiting.webp) Thinking… stays compact until Lira has progress to show. As Lira writes, changed text appears directly in its field. A small black pointer, soft highlight and text cursor show where it is working. **Thinking** shows a short action such as **Writing the pre-call brief…**. The pointer glides between sections and stays visible during pauses, without leaving an editing highlight on a field that is no longer being changed. Scroll the document whenever you like; **Follow changes** returns to the active field. Your message draft and input focus stay in place. Text arrives in short updates, and edited sections resize gently as Lira writes. Longer titles, briefs and rubric entries remain in the document without separate scroll areas. Panels that Lira opens stay open until you close them. **Thinking** stays visible while the update is running, including pauses after an interim reply. When the update finishes, the untouched summary folds to **Thought for…**, with the elapsed time before the final reply, such as **Thought for 8s**. Open it again to review the activity; if you open or close it yourself, Lira keeps that choice. The final reply explains what changed. ![An expanded Thought for 8s summary with closely spaced steps for the scenario outline, call behavior and pre-call brief.](https://lira.thoughtly.com/docs/images/product/scenario-thinking-duration.webp) Review the elapsed thinking time and the steps taken. ![A skill's expected behaviors are being written in the rubric while the toolbar marks the preview as not saved.](https://lira.thoughtly.com/docs/images/product/scenario-live-editing.webp) See the change in its field while Lira writes it. The preview becomes the saved scenario after the update finishes. A completed update can list the public sections that changed; choose **View changes** to move to that section. If public pages were researched, open **Sources** to inspect the citations. The brief and grading remain in the document, and extended scoring behaviors or examples are available under **View standards**. Review the result, then try a call. You can continue refining after practice. Closing the page does not cancel an update; return to the same scenario to see its status. **Stop** cancels the current update and discards its partial preview. If an update fails or another edit wins, the latest saved version stays intact. ![A fictional scenario with Publish and Test call above an empty-chat prompt, starter suggestions, brief and weighted skill rubric.](https://lira.thoughtly.com/docs/images/product/scenario-chat-editor.webp) Review the scenario, describe changes in chat, then publish it as training when ready. Lira also writes a short catalog summary so people can recognize the scenario before opening it. This summary describes only the learner-visible setup; the full brief stays on the scenario page. There is no extra summary field to fill in. The **Pre-Call Brief** is the learner's orientation: their role, the situation, and any background they should have before picking up or placing the call. The **Grading** section holds the objective and skills used to assess the attempt. There is no separate product-name or practice-focus field to maintain. When Lira creates a scenario or changes its brief or counterpart, it keeps the counterpart's name and role consistent between the brief and the person on the call. Hidden motives, diagnoses and scoring instructions stay out of the brief. ### Edit shared details Admins can choose **Edit** on another member's workspace-shared scenario, including one published as training. When the creator's setup is private, chat still lets you update the title, **Pre-Call Brief**, grading, call duration, difficulty, voice and language. On a phone, open **Actions**, choose **Edit**, then switch to **Chat**. Edits save automatically to the same shared scenario. Lira works from the shared details and your requests; it cannot read the creator's hidden counterpart instructions, source material, original conversation or tests. The counterpart's identity and call direction also stay under the creator's control. Your own editing conversation stays separate from other editors' conversations. ![A shared scenario's chat shows Refine the shared details and an editable message box.](https://lira.thoughtly.com/docs/images/product/scenario-shared-editor.webp) Use chat to save changes to the same shared scenario. **Test call** and **Test history** are unavailable in this limited editor. Ask the creator to change private call behavior or run an authoring test. To build your own setup, duplicate the scenario; the original private sources and prompts are not copied. Sharing or publishing a scenario does not share its creator's previous tests or conversation. ### Continue with a suggestion After a reply, Lira may suggest a few next questions or changes based on the current scenario and your request. Choose one to fill the message box, then review, edit or send it. Suggestions arrive separately from the main reply and never hold up editing or queued changes. The chat uses expandable activity summaries. Open **Thinking** to review the public steps taken; web searches and page reads appear only when they occurred. Expand a web step to open its source. The final answer stays visible outside the summary, which folds when the work finishes. ### Stay in sync with other editors Changes made through a connected MCP client or by another authorized editor appear automatically while this page is open. One shared activity entry combines the contributors and their saved updates, such as “Alex and Colin made 15 changes.” Edits through MCP, the Studio agent and other controls count together, even over several days. Each successful save counts once, regardless of how many fields it changes. Choose **View changes** to jump to the affected part of the scenario. Your unsent message and scroll position stay in place. ![One compact entry showing that Alex Morgan and Colin Reed made 15 changes, with a timestamp and View changes action.](https://lira.thoughtly.com/docs/images/product/scenario-shared-edits.webp) Review several editors’ changes in one shared activity entry. Sending a message to Lira in this Studio closes the preceding activity group. Later edits begin a new one; opening the page or returning another day keeps the existing group together. Your own Studio replies already describe your AI edits, so those saves do not add duplicate activity. Other editors’ conversations remain separate from yours. The editor checks for saved changes every few seconds while the page is visible, and again when you return to it. A newer saved version takes precedence over an older unfinished AI preview. Review the current scenario before retrying a conflicting change. The shared activity history requires access to the scenario's private setup; editors limited to shared details still receive the current scenario without that history. Other editors' AI conversations and test evidence remain private. ### Queue follow-up changes Send another message while Lira is working to queue a follow-up. Waiting messages appear in a compact tray above the message box. They run in the order you sent them, one at a time for this scenario. Each starts from the latest saved scenario, including changes made by earlier requests. Sending a follow-up does not interrupt the current update. The queue is saved with your editing conversation. You can leave or refresh the page and return to the same requests. There is no daily allowance for AI generation requests; other scenario and running-work limits still apply. ![Two compact queued messages in an inset tray attached to the message box, each with a pencil to edit and a trash icon to remove, above separate Stop and Queue message buttons.](https://lira.thoughtly.com/docs/images/product/scenario-chat-queue.webp) Press Enter to queue a follow-up while the current change continues. Use the trash icon (**Remove**) on a queued message to discard it before it starts. The pencil icon (**Edit**) takes that message out of the queue and returns its full text to an empty message box. Long messages have a shortened preview in the tray. Review the text and send it again when ready; the new request joins the end of the queue. If you already have an unsent draft, send or clear it before editing a queued message. If the request has already started, these queue actions leave it running. **Stop** affects only the current update. The next queued request can start after the current one completes, fails, or is stopped. To stop all remaining work, remove the queued messages before stopping the current update. A stopped or unsuccessful update keeps the last saved scenario; later requests use that saved state. ## Shape a realistic conversation Describe the person you want to speak with and the situation they are in. Useful details include their role, what happened, what they know, what they care about, and how much patience they have. The AI turns this request into counterpart instructions. There is no raw prompt field in the editor, but authorized editors can ask Lira to show or explain those instructions in chat. Learners and public scenario pages do not receive them. Request behavior changes through the chat. For a fictional exercise, such as selling an imagined magical pen, say that fictional capabilities may be introduced during the conversation. For real products, provide approved facts or a public website and review the result. Lira can research public pages when available; **Sources** in the editing conversation shows which pages were used. Each practice starts fresh. The counterpart receives no earlier practice transcript, score or coaching and does not know the learner's goal or scoring rubric. It can know fictional background included in the scenario, such as a prior discovery call, without remembering an earlier practice attempt. There is no universal discovery-question or meeting-booking requirement: support conversations follow their own situation. The creator's description drives how the counterpart behaves. If a call feels too accommodating or misses an important problem, return to **Edit** and explain what should change. Keep scoring expectations in the grading request so the counterpart cannot coach you toward them. For a shared scenario with private owner material, only the owner can refine its private setup. Other authorized editors can [edit the shared details](https://lira.thoughtly.com/docs/manage-training/create-scenarios#edit-shared-details) or duplicate the scenario to make their own version. Original sources and the author's editing conversation remain private. ## Configure and test Ask for the call direction you need. In a cold call, the learner calls the counterpart. In inbound service, the counterpart calls the learner, who answers as the representative. This controls the browser conversation; it does not place a telephone call to your device. The call settings below the title show the maximum length, difficulty and voice, with the language beneath the voice. Ask Lira to change a setting. Difficulty adjusts patience and resistance within the person and situation you created: - **Easy:** patient and cooperative, with clear answers and room to recover. - **Medium:** ordinary skepticism and relevant concerns, with occasional redirection. - **Hard:** guarded and impatient; challenges claims, interrupts rambling, and may leave an unproductive exchange. - **Expert:** highly resistant and unpredictable; can react bluntly or sarcastically, interrupt quickly, and end the call early. You do not need to write special interruption instructions for the difficulty to take effect. Each new attempt can vary the counterpart's manner and patience without changing the scenario's facts. The counterpart remembers the current conversation, including answers and refusals, but never receives earlier practice evidence or the learner's grading goals. Long speaking turns or extended unexplained silence can prompt a response. Ordinary thinking pauses, filler, accents, and stuttering are not failures. Strong answers can improve engagement, but a successful outcome is not guaranteed. The same levels apply to support and other conversations within their own circumstances; a support customer does not become a cold sales prospect. A clear request to hang up or stop the role-play ends the call instead of switching to a general assistant. A customer-ended call still appears in the learner's attempts with the available recording, transcript and feedback, subject to the workspace's privacy settings. Existing scoring remains unchanged: skills not demonstrated receive zero, including when the conversation ends early. Ask to change the time limit, voice or language when needed, or open the voice picker from the voice name. The maximum length is 1 to 30 minutes; the call ends when it is reached. Existing assignments keep the settings of their assigned version. Use **Test call** in Edit to check the voice, whether the counterpart behaves as intended, and whether the [grading objective is achievable](https://lira.thoughtly.com/docs/manage-training/scoring-and-certificates). ## Test the scenario Authoring tests require access to the scenario's private setup. An editor limited to shared details cannot run a text simulation, start **Test call**, or view **Test history**. Ask the creator to test private call behavior. For a quick automated check, ask Lira to “run a short text simulation and suggest improvements.” It tries up to four synthetic turns and reports limited findings. This is not a real call or score, creates no test-history entry, and cannot check voice or audio. Use **Test call** to try the conversation yourself. Choose **Test call** in Edit, check your microphone and speaker, then start or answer the call. This tests the saved scenario and freezes its grading rules for that call. Finish pending changes before testing. If the scenario changed elsewhere, reopen its latest revision before trying again. When the call ends, feedback opens over the studio with the test timestamp below its heading. **Simulated score** shows the score this conversation would receive under the tested rubric. Read the summary and **Try next** for a practical improvement, then expand **Skill feedback** for each skill’s score, observations and next step. The criteria remain on the scenario page. Written coaching can continue arriving after the score appears. If no usable conversation was captured or scoring failed, the result explains that rather than inventing a score. ![Test feedback with a timestamp just below the heading, a goal-status badge beside the simulated score, concise coaching, and actions to test again or review with AI.](https://lira.thoughtly.com/docs/images/product/editor-test-feedback.webp) A test uses real grading without adding a learner result. This example uses fictional demonstration data. ![A concise list of skill scores with observations from the test call and suggested next steps, without repeating the scoring criteria.](https://lira.thoughtly.com/docs/images/product/editor-test-skills.webp) See how each skill performed in this test. Editor tests stay out of learner practice history, certificates and rankings. Where workspace privacy permits retention, anyone with scenario editing access can view its retained tests, feedback and permitted recordings, or reference a test when chatting with Lira. Choose **Test history** from the top-right **Actions** menu to reopen tests for up to 90 days. Read-only scenario access does not grant access to tests. Private scenarios keep their existing access restrictions. The test timestamp stays visible at the top of its feedback, and closing it does not delete a retained test. Temporary tests remain available only to the person who ran them. ![A compact test call card with its date, score, View test and Review with AI actions.](https://lira.thoughtly.com/docs/images/product/scenario-test-card.webp) Reopen feedback or bring a test into the conversation. ### Reopen and replay a test Open a test card in the conversation or choose **Actions → Test history** and select a call to revisit its feedback. Use the recording controls when available, or expand **Transcript** to read the conversation. Recording depends on consent, workspace policy and whether audio was captured; a missing recording does not mean feedback or the transcript is missing. Reopening feedback or retrying a media load does not place another call. Starting another test creates a separate test of the current saved scenario. Close the feedback dialog to return to editing. **Transcript**, **Key moments** and **Skill feedback** start collapsed and open independently. When enough quoted evidence is available, expand **Key moments** and choose a moment to replay that part of the recording. In transcript-only tests, choosing a moment opens its passage in **Transcript**. ![Test feedback with compact recording controls and collapsed sections for Transcript, Key moments and Skill feedback, with dividers above Key moments and Skill feedback.](https://lira.thoughtly.com/docs/images/product/editor-test-moments.webp) Expand only the evidence you want to review. This example uses fictional demonstration data. ![Scenario Test history with a dated test call and its simulated score.](https://lira.thoughtly.com/docs/images/product/scenario-test-history.webp) Reopen an existing test without placing another call. ![Test feedback with compact recording controls, an expanded transcript and actions to test again or review with AI.](https://lira.thoughtly.com/docs/images/product/editor-test-replay.webp) Replay available evidence alongside the test result. This image uses fictional demonstration content. A test keeps the brief and grading standard it used. Later edits do not rescore that conversation. When an earlier test refers to an older scenario revision, review it as evidence of that earlier version. If failed grading offers **Retry feedback**, it retries the assessment from the same call and frozen rubric while the original evidence window is still valid. It does not place another call or change a completed score. **Check again** refreshes feedback after a loading error; starting another test is a separate action. Activity-only workspaces keep test feedback temporary and do not retain transcripts or recordings for later review. Review that feedback before closing it or its delivery window expires; temporary tests cannot be attached to Lira for AI review. Stricter privacy, lost source access, deletion or expiry can make a retained test unavailable sooner; switching back to a less restrictive setting cannot restore removed content. See [privacy and retention](https://lira.thoughtly.com/docs/workspace/privacy). ### Review a test with Lira Choose **Review with AI** on the test you want to discuss. A removable test reference appears in the message box. Ask what happened, whether the grading matches the conversation, or what should change. Remove the reference if you want to send the message without that test. ![A selected Test call reference with its score and Remove control above a review request in Lira's message box.](https://lira.thoughtly.com/docs/images/product/scenario-test-reference.webp) Check the selected test before sending your question. The selected test is resolved privately on the server; you do not need to copy its transcript into chat. Lira reviews the saved transcript and grading, rather than listening to the audio. A review or answer can leave the scenario unchanged and does not regrade an existing score. Ask explicitly for the edits you want to apply, then test again. Queued follow-ups keep their selected reference, but each starts from the latest saved scenario; the test's original snapshot stays fixed. ![A test card, a review question with its test reference, and Lira's reply saying that no scenario changes were made.](https://lira.thoughtly.com/docs/images/product/scenario-test-review.webp) Discuss the call first, then ask for the changes you want. Keep the same test reference selected to follow up on its review or ask Lira to apply its suggestions. Lira rechecks access to that test before continuing. The counterpart in later calls still receives no previous test transcript, feedback, goal or rubric. Deleted, expired or inaccessible tests cannot be used as new review context. ## Practice, share, or publish training After reviewing and testing the scenario, choose **Start practice** on the scenario page for a saved learner attempt. Personal practice earns grades and feedback without automatically issuing certificates or creating assignments. **Test call** inside Edit remains a private authoring test, separate from those learner results. The owner can choose **Actions → Workspace access…** in the editor, select **Share with workspace**, and save to let coworkers discover and practice the personal scenario. This does not share previous attempts, recordings, feedback, uploaded files, or private generation jobs, and does not enable assignments or official certificates. See [personal scenario sharing](https://lira.thoughtly.com/docs/practice/private-prep). For official team training, an authorized manager or admin can choose **Publish** in the editor after reviewing its rubric and certificate requirements, then confirm **Publish training**. Publication creates an immutable training version using the same scenario identity and keeps its current folder automatically; it does not turn earlier private practice into certified training. Use **Move to folder** in the library to change its location. Assigning people remains a separate, explicit action. ![An explicit training publication confirmation with Keep editing and Publish training actions.](https://lira.thoughtly.com/docs/images/product/scenario-publication.png) Review publication before making training available; its folder stays unchanged. To edit an existing scenario, open its overview and select **Edit**. Personal scenarios and official training use the same chat-led editor. [Folders and Trash](https://lira.thoughtly.com/docs/practice/organize-scenarios) help organize the library without changing the conversation or its published standard. > **Existing attempts keep their standard** > > Saving a new published version does not rewrite earlier attempts or assignments. They retain the brief, rubric, and certificate requirements from the version they started with. Private supporting material stays owner-only when a scenario becomes official training. After publishing training, use **Assign** on the scenario overview or in the editor toolbar to [choose the people who should practice it](https://lira.thoughtly.com/docs/manage-training/assignments). The button is available to authorized managers and admins for published training. --- # Manage workspace knowledge > Ground scenarios in approved website pages, documents, and product information. Source: https://lira.thoughtly.com/docs/manage-training/knowledge-sources Audience: manager, admin Last reviewed: 2026-10-28 Workspace admins manage shared product and company material in **Settings → Company**. Add material you have permission to use and keep it current. The **Connections** group in **Settings → Integrations** also links to these shared knowledge controls. To provide background for an individual scenario, include it in the creation request or ask **Lira** in the scenario studio. You can include a public website for research. See [Create and edit scenarios](https://lira.thoughtly.com/docs/manage-training/create-scenarios). ![Company settings show an empty shared-source table with Add website and Upload files controls.](https://lira.thoughtly.com/docs/images/product/knowledge-sources.webp) Manage approved company and product information in Company settings. ## Choose the right scope - **Shared knowledge** in Company settings is managed by workspace admins and can support workspace scenarios. - Existing **scenario sources** stay attached to their scenario and retain their original permissions. - **Private prep sources** belong to the owner's meeting prep. They do not become shared workspace knowledge. Adding a document to one scope does not make it available everywhere else. ## Add website pages In Company settings, choose **Add website**, enter a complete `https://` website address, and select **Find pages**. Review the returned pages, select the relevant ones, and add them for processing. If discovery fails, check the address and try a directly accessible page. Content behind a login or otherwise inaccessible to Lira may need to be provided as an approved document instead. ## Upload files Choose **Upload files**, then select PDF, DOCX, or TXT files, up to 10 MB per file and 10 files at a time. Prefer focused, current documents over a large set of duplicated or contradictory material. Word documents also have extraction limits to keep imports reliable. If a DOCX cannot be safely read, split it into smaller documents or export the relevant content as PDF or TXT, then upload it again. Wait until the source is **Ready** before relying on it. Processing and failed states are shown alongside each source. For a failed source, review the error and use the retry action when offered; for a partially successful batch, check the list before uploading everything again. ## Use sources when refining Describe the change you need in the scenario's **Lira** chat. Ordinary edits reuse the supplied context. Ask for current information or include a public URL when you want fresh research; naming a product alone does not trigger a lookup on an existing scenario. Activity shows what was actually reviewed and links to public research when available. Existing attached sources retain their stored selection; the scenario editor does not offer manual source controls. The resulting **Pre-Call Brief** is separate from the private instructions used by the counterpart. A source does not automatically give that person every fact in a document. Ask for only the knowledge they should reasonably have, and keep learner objectives and scoring requirements separate from their behavior. ## Review before publishing Check the updated pre-call brief and rubric against the original material, especially product claims, pricing and qualification requirements. Try a practice call and refine the scenario when needed. Published versions preserve the selected source content used for that version. Updating a source does not silently rewrite an existing assignment or attempt. Review and save a new scenario version when the training needs to change. Removing a source requires care. Review the confirmation and stated impact before proceeding. Original source material and the author's editing conversation remain private when a personal scenario is shared. --- # Design scoring and certificate requirements > Define observable skills and a fair, explicit standard for completing a scenario. Source: https://lira.thoughtly.com/docs/manage-training/scoring-and-certificates Audience: manager, admin Last reviewed: 2026-10-29 A good rubric describes behavior a learner can demonstrate in the conversation. The certificate requirements define which parts of that rubric must be met to qualify. ![The objective, passing requirements and skill criteria appear together, with proportional weight bars and individual minimum scores.](https://lira.thoughtly.com/docs/images/product/scoring-rubric.webp) The rubric describes what each skill measures and which minimums apply. ## Write a useful rubric Open **Edit** on the scenario and review **Grading**. Use the chat to describe changes to the objective, skills, observable behaviors, and examples. Keep skills distinct enough that the same behavior is not counted repeatedly. For example, “Ask about the buyer's current workflow and its impact” is easier to assess than “Be excellent at discovery.” Use examples to clarify the standard, not to require one exact script. Skills are scored out of 100 and count equally by default. Use the chat to change their contribution, such as “Give discovery twice the weight of the other skills” or “Make the first skill count for 40% and split the rest equally.” The rubric displays the resulting percentages, and the overall score uses those weights. Every selected skill, including custom skills, receives a numeric score when usable dialogue is captured. A skill not demonstrated receives zero and keeps its configured share of the average. ![A five-skill rubric with Discovery weighted three times as heavily as each other skill, showing 42.9 percent and four 14.3 percent shares.](https://lira.thoughtly.com/docs/images/product/scenario-weighted-rubric.webp) Give the most important skills a larger share of the overall score. ## Choose the qualification gates In the chat, describe whether an overall score and achievement of the objective should be required. Ask for an overall minimum from 0 to 100; decimal scores are supported. A score of 0 is still a requirement, while removing the requirement makes the score informational. Ask for a pass minimum only on skills that must be passed. All skills still contribute to the overall score using their configured weights; a weight is separate from a minimum passing score. You can add, revise or remove skills by describing the change; removing a skill also removes its pass minimum. Review the updated rubric before sharing or publishing. Existing attempts and test calls keep the rubric and weights they used, even after later edits. Set the requirements that matter for this scenario: - A minimum overall score, if needed. - Minimum scores for particular skills, where appropriate. - Achievement of the scenario's desired outcome, when required. All applicable requirements must be assessed and met within one attempt. Scores from separate calls are not combined. A performance score does not automatically award a certificate: incomplete capture or missing evidence of the required outcome cannot establish eligibility. ## Set the certificate details Ask for the certificate validity you need, or no expiry. Review the updated requirements before publishing. Workspace-level issuer, logo, and accent color are managed separately in [Certificate design](https://lira.thoughtly.com/docs/workspace/settings-and-branding). Use an author preview to test the conversation before publishing. A preview does not earn a learner certificate. Check that learners have a realistic opportunity to demonstrate each required skill during the configured call length. > **Changes apply to a new version** > > Saving a changed published scenario creates a new version. Existing assignments and attempts keep their original scoring standard; editing today's rubric does not rescore yesterday's call. Share [the learner scoring guide](https://lira.thoughtly.com/docs/results/feedback-and-scoring) when introducing the scenario so people know what they are practicing toward. --- # Assign and manage training > Choose who should practice a published scenario and track assignment completion. Source: https://lira.thoughtly.com/docs/manage-training/assignments Audience: manager, admin Last reviewed: 2026-10-30 An assignment connects a person with a particular published scenario version. Admins can assign within their workspace; managers can assign to people they manage. ## Before your first assignment If no training has been assigned, **Assignments** shows a short guide to choosing a scenario, selecting people, and following their progress. Choose **Assign training** to begin. If no published scenarios are available, choose **Create scenario** first. ![An illustrated No training assigned yet panel with a Create scenario action and three steps for choosing training, selecting people, and following progress.](https://lira.thoughtly.com/docs/images/product/assignments-empty.webp) Start with a published scenario, then choose who should practice it. ## Assign from a scenario 1. Open the published scenario in **Scenarios**. 2. Select **Assign** on the scenario overview or in its editor toolbar. 3. Search for and select the people who should practice it. 4. Add a due date if one is needed. 5. Review your selection and confirm the assignment. ![The assignment dialog with Jordan Lee and Casey Morgan selected and an optional due date.](https://lira.thoughtly.com/docs/images/product/assign-scenario.webp) Select the people who should practice, then add an optional due date before confirming. The dialog distinguishes people who already have an assignment. **Select visible** selects the available people in the current search results, so check the selection count before confirming. **Assign** is available for published training. If the scenario is still personal or a training draft, an authorized manager or admin must first choose **Publish** in the editor and confirm **Publish training**. Sharing a personal scenario with the workspace alone does not make it assignable. Publication does not assign anyone automatically. For broader training management, use **Assignments**. Review the people, scenario, deadline, and completion information before applying changes. ## Find an assignment On **Assignments**, choose **Active** or **Completed** above the table. Search by scenario or person in the bordered field on the left. In Active, **Filter** narrows the list by assignment status. **Assign training** stays on the right, and page controls appear below the table. ![Active and Completed views above Search scenarios or people, Filter, and Assign training.](https://lira.thoughtly.com/docs/images/product/assignments-toolbar.png) Assignment views and table controls follow the same layout as People. ## What learners see Assigned scenarios appear prominently in the learner's Scenarios collection. Learners can still explore other published scenarios available to them. Ask them to start from the assigned card when working toward that assignment. An assignment is completed by a qualifying attempt that earns the scenario's certificate. Submitting the result is a separate action and is not required to mark the assignment complete. Learners receive assignment and reminder emails when email delivery is enabled for the workspace. A qualifying private attempt stops those reminders; submitting an unsuccessful attempt does not. See [email notifications](https://lira.thoughtly.com/docs/workspace/email-notifications) for the schedule and personal reminder controls. ## Deadlines and changes Use the assignment controls to change a due date or remove an assignment when authorized. Dates use the workspace's time zone, so check that setting before coordinating a deadline across locations. Removing an assignment is different from deleting a learner's account. Read the confirmation carefully; access to assignment-based submission and review can change when the assignment is removed. Existing assignments retain their published scenario version. Saving a revised scenario does not silently change the requirements for people already assigned to it. If an expected person is missing, check their active membership and manager assignment in [People](https://lira.thoughtly.com/docs/manage-training/people-and-teams). Do not create a second invitation until you have checked the existing record. --- # Manage people and teams > Invite people, organize reporting relationships, and keep workspace access intentional. Source: https://lira.thoughtly.com/docs/manage-training/people-and-teams Audience: manager, admin Last reviewed: 2026-10-28 People, teams, and reporting relationships serve different purposes. A person's role controls their permissions; their manager determines managerial scope; their team supports organization and team reporting. ## Find a person Choose **Directory** to see current members or **Pending invitations** to check people who have not joined. Search appears on the left below these views; **Filter** narrows the directory by role or manager. **Invite people** stays on the right of the same toolbar. On a phone, search takes its own row above the controls. Managers see **My team**, with **Direct reports** and **Pending invitations**. Its search, training-progress filter, and invitation action use the same layout. ![Directory and Pending invitations above a bordered search field, Filter, and Invite people.](https://lira.thoughtly.com/docs/images/product/people-toolbar.png) Choose a view, then search or filter its records. Fictional workspace counts shown. ## Invite people Open **People** and choose **Invite people**. Managers see an invitation flow for trainees in their scope; admins can invite trainees, managers, or admins. In **By email**, enter one or more email addresses, separated by commas or new lines. Choose a **Role**, then **Continue**. This first step does not send invitations. Managers can invite only trainees into their own direct-report group; admins can invite trainees, managers, or admins. In **Optional setup**, admins can choose a manager and team. Open **Team** to search existing teams or choose **Create a team…** within the same menu. A new team name can be reviewed before creation; **Cancel** returns to the team picker without creating it. The manager controls coaching scope; the team groups people for organization and reporting. A team label alone does not grant manager access. Managers keep their own reporting scope and can choose only initial training here. For trainees, open **Select training…** under **Training** and search by title. Select or deselect multiple scenarios while the picker stays open. **Clear selection** removes them all; **Done** returns to the invitation draft. The closed control shows one title or a selection count. Search results stay in a bounded scrolling area, including with large catalogs; up to 30 scenarios can be selected. They become available after each trainee joins. **Due date (optional)** appears once training is selected. Choose **Skip and send** to invite people without optional team, manager, or training choices. If you configure these choices, **Send invitation** includes them; **Skip and send** discards them. **Back** keeps the draft and returns to the previous step. With multiple trainee recipients, **Review invitations** lets you customize training for each person using the same searchable picker. Batch training applies to recipients without individual choices. Changing it preserves a person's customized training, including an explicit choice of no training. A due date remains available while any recipient has training; clearing every training choice removes it. If an address is invalid, duplicated, already a member, or already invited, Lira opens a recipient review before optional setup. Correct or exclude entries, then choose **Continue**. Closing and reopening the dialog on the same People page keeps your draft. ![Invitation dialog with email addresses, a Trainee role and permission description, a Continue button and no team or training controls.](https://lira.thoughtly.com/docs/images/product/invite-people.jpg) Add recipients and choose their role. Continue opens optional setup. ![Optional setup with a searchable Team selector and a single compact Training multi-select, Back, and Skip and send.](https://lira.thoughtly.com/docs/images/product/invite-people-options.jpg) Optional choices stay together. Back returns to the recipients. ![Team search above No team and Enterprise sales choices, with Create a team in a separate footer.](https://lira.thoughtly.com/docs/images/product/invite-team-menu.jpg) Create a missing team directly from its picker. Fictional team name shown. ![Training multi-select with searchable bounded results, visible selections, and Clear selection and Done actions.](https://lira.thoughtly.com/docs/images/product/invite-training-search.jpg) Search by title without expanding the invitation form. Fictional catalog shown. For a larger group, choose **Upload CSV** and select a file with an `email` column, up to 500 people. **Continue** opens a review of each source row, its status, and an **Include** checkbox. Choose training for an individual recipient in the review when needed. Correct errors through **Edit list**, then choose **Continue** to reach optional setup and send the selected recipients. After sending, Lira confirms how many invitations are **queued**. Choose **View invitations** to follow their status or **Invite more** to add another group. A partial failure keeps successful recipients queued and lets you retry the remaining recipients without sending duplicates. ## Follow invitation status **Pending invitations** separates the recipient's email, role, delivery status, and invitation date. **Queued** means the email is waiting to be sent; **Sent** means it has been sent and the person has not yet joined. **Couldn’t send** provides a visible **Retry** action. For an expired or unanswered invitation, open its **Actions** menu and choose **Resend invitation**. Use **Revoke invitation** to cancel an unused invitation, then review the confirmation. ![Pending invitation rows with separate Sent, Queued, Couldn’t send, and Expired statuses, a Retry action, and individual Actions menus.](https://lira.thoughtly.com/docs/images/product/pending-invitations.jpg) Check delivery status and recover from a failed or expired invitation. An invited person must sign in with the email address that received the invitation. A pending invitation is not the same as an active membership. An invited admin confirms their name, completes a short private Getting started conversation, and receives a starter certificate before opening the existing workspace. The same welcome applies to managers and trainees. See [joining as an admin](https://lira.thoughtly.com/docs/get-started/workspaces-and-roles#joining-as-an-admin). ## Roles and reporting relationships Admins can update a member's role, manager, and team through that person's controls. Check the consequences before changing access: - A manager can manage only the people assigned to them. - Managers can edit scenarios they created; admins can manage workspace scenarios. - A team label alone does not grant manager permissions or access to private results. Lira prevents changes that would leave the workspace without an active admin. Arrange replacement admin access before removing or demoting its last admin. ## Teams and training Teams group leaderboard results and training reports. They do not grant coaching access; the manager relationship controls that scope. To move an existing person, an admin opens **People**, chooses their name, then **More → Member settings → Team → Save member**. Changing a team also changes how that person’s existing results and assignments are grouped in team rankings and reports. Admins can create teams for organization and reporting, then associate people with them. Keep names recognizable to the people who use the workspace. Use [Assignments](https://lira.thoughtly.com/docs/manage-training/assignments) to choose the training people should complete. Team membership and training assignments are related organizational tools, but they are not interchangeable. ## Remove access carefully Use the member controls to remove access, or an invitation's **Actions** menu to revoke it when authorized. Review the confirmation before proceeding. Revoking an invitation also removes training attached to that invitation. Removed members cannot continue using that workspace, and access to their shared results may change. For sign-in problems, send the person to [access troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/access). --- # Review submitted results > Find the training results you can review and give focused, actionable coaching. Source: https://lira.thoughtly.com/docs/manage-training/reviewing-results Audience: manager, admin Last reviewed: 2026-10-23 **Results** is for eligible attempts learners have chosen to submit. It is not a view into every private practice call. In Submitted results mode, admins can review submitted training within the workspace. Managers can review eligible submissions from people they manage. Private prep, unsubmitted practice, and unavailable content remain outside that access. Learners can share completed attempts from assigned training or standalone scenario practice. Sharing does not require a passing score or a certificate. ## Find a result Use the search field to find a person or scenario. Choose **Last 7 days**, **Last 28 days**, **Last 90 days**, or **All time**, and open **Filter** to narrow by scenario or manager. Remove an active filter using its chip below the toolbar. The **New** and **Reviewed** views separate submissions that need attention from those already reviewed. The table shows each person's scenario, score, certificate status, review status, and submission date. Select a scenario title to open its result, or a person's name to open their profile. ![All submissions, New, and Reviewed views above a bordered search field, Filter, and date range.](https://lira.thoughtly.com/docs/images/product/submitted-results.png) Choose a submission view, then search, filter, or change the date range. Results display ten submissions per page. Use **Previous**, **Next**, or the page number to browse a longer history. The count below the table shows which results are on the current page. An empty view can mean there are no submitted attempts in the current scope or that filters exclude them. It does not necessarily mean people have not practiced. ## Overview date range The date selector on **Overview** updates participation, practice activity, certificates, assignment progress, and submissions ready for review. Choose **Last 7 days**, **Last 28 days** (the default), or **Last 90 days**. The selected range stays in the URL when you refresh or use Back and Forward. Activity is compared with the immediately preceding period of the same length. Assignment progress includes currently active assignments and assignments completed during the selected period; older completed assignments are excluded. **Current team standing** is the current leaderboard position, independent of the date filter. Select **View results** under the review list to keep the same date range on the Results page. Existing role permissions and workspace privacy settings apply to every period. ![Overview set to Last 7 days, with participation, completed assignments, certificates, and practice activity for the selected period.](https://lira.thoughtly.com/docs/images/product/overview-period.png) Choose a period to update overview analytics. Fictional demonstration data shown. ## Review in context Open a submission to see its scenario, attempt, and original scoring requirements. Start with the outcome, then inspect the skills and supporting moments. Play the recording or read the transcript when retained content is available. Skills not demonstrated receive zero, including in short calls. **Not scored** means the attempt could not be evaluated, rather than that the performance was poor. A score based on incomplete capture can support coaching, but does not establish certificate eligibility. ## Give a useful next step Use the available coaching controls to add a note and mark the submission reviewed. Make the note specific: identify a moment, explain its effect, and suggest one behavior to try next. Learners can return to submitted feedback and acknowledge it. Coaching notes do not replace the saved rubric or recalculate the certificate qualification. If the scenario itself needs a better standard, update its next version separately. > **Privacy can limit this screen** > > Anonymous team scores mode provides aggregates, not named result review. Activity only mode retains participation and credential completion without reviewer access to detailed scores or call content. Learners can also withdraw submissions. See [workspace privacy](https://lira.thoughtly.com/docs/workspace/privacy) for the exact boundaries and [recordings and transcripts](https://lira.thoughtly.com/docs/results/recordings-and-transcripts) for playback help. --- # Manage your account > Update your profile, protect your sign-in, and distinguish personal settings from workspace settings. Source: https://lira.thoughtly.com/docs/workspace/account Audience: everyone Last reviewed: 2026-10-24 Open the workspace menu at the top of the sidebar and select **Your account**. Your account page shows the name and email address associated with your sign-in. ![Workspace menu showing two example workspaces, account settings, workspace settings, Help center, and Sign out.](https://lira.thoughtly.com/docs/images/product/workspace-menu.webp) Switch workspaces or open your account from one menu. Workspace settings are shown to admins. ## Update your name Edit **First name** and **Last name**, then select **Save changes**. Wait for the save confirmation before leaving the page. If saving fails, the page keeps an error visible so you can try again. Your email address is displayed as your sign-in identity. It is not an editable field on this page. Contact [help@thoughtly.com](mailto:help@thoughtly.com) if you need help with the identity used to access Lira. ## Protect your sign-in Use **Account security** on this page to set up an authenticator app, add a passkey, or remove a method after verifying your email in a dialog. If your workspace requires two-factor authentication, either an authenticator app or a passkey meets that requirement. See [two-factor authentication and passkeys](https://lira.thoughtly.com/docs/workspace/account-security) for setup, required sign-in verification, and recovery. ## Choose your email notifications Choose the **Email notifications** tab to manage optional training reminders, certificate reminders, and weekly team summaries for your current workspace. Every role can manage their own preferences. See [email notifications](https://lira.thoughtly.com/docs/workspace/email-notifications) for schedules and essential messages. ## Choose a workspace Use the workspace menu to move between workspaces you belong to. Your selected workspace determines which scenarios and assignments you see. Your role may be different in each workspace. Changing your profile does not change your workspace role or reporting relationship. Ask a workspace admin if you need different permissions, a different manager, or access to another workspace. ## Sign out and sign back in Select **Sign out** in the workspace menu when you finish on a shared device or need to change accounts. Use the email address connected to your invitation when you sign back in. If the workspace is missing or you reach an access-pending screen, avoid creating a second account as a workaround. Check the invitation address and follow [access troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/access). ## Where other settings live Personal account details belong here. Company information, certificate branding, and workspace privacy are separate admin settings. See [workspace settings and branding](https://lira.thoughtly.com/docs/workspace/settings-and-branding) or [workspaces and roles](https://lira.thoughtly.com/docs/get-started/workspaces-and-roles). --- # Workspace settings and branding > Manage company details, certificate branding, and your workspace's sign-in requirement. Source: https://lira.thoughtly.com/docs/workspace/settings-and-branding Audience: admin Last reviewed: 2026-10-27 Workspace admins manage shared settings. Open **Settings** from the workspace menu, then choose the section you need. Confirm the selected workspace before changing information used by other people. ## Company Set the **Company name**, **Website**, and **Workspace time zone**. Use a recognizable name and the intended company website rather than an individual profile. The time zone matters for date-based training deadlines. Check it before coordinating assignments across locations. Save the changes and wait for confirmation. Company settings also contain shared knowledge and branding controls. Manage approved company and product material under [Shared knowledge](https://lira.thoughtly.com/docs/manage-training/knowledge-sources). ## Certificate design Use **Certificate design** to review the issuer name, accent color, and available logo settings. The preview helps you check the identity learners will receive on their certificates. Use a legible logo and an accent color that works with the certificate text. Make sure the issuer is the organization that should stand behind the credential. Your uploaded logo appears on the onboarding preview, earned certificates, shared certificates, and downloaded PDFs. Certificates that were issued before you added a logo also use your current logo. A certificate with a logo already saved at issue keeps that original artwork when you change workspace branding; its issuer name and accent color also stay as issued. ### Tag the issuer's LinkedIn page In **Certificate design**, fill in **LinkedIn page name** with the company page's exact name. In **LinkedIn company page**, paste a URL containing the page's numeric ID, then save the certificate branding. You can copy this URL from the page's admin view; for example, `https://www.linkedin.com/company/123456/admin/`. Lira stores the corresponding public page URL. A short company address such as `https://www.linkedin.com/company/example-company/` does not supply the numeric ID. Use the page's admin URL instead. You need access to the correct company page to obtain it; entering a name alone cannot create a LinkedIn tag. ![Certificate identity settings show the fictional issuer Northstar Academy, its accent color, exact LinkedIn page name, a numeric company URL, Remove LinkedIn page, and Save certificate branding.](https://lira.thoughtly.com/docs/images/product/certificate-linkedin-settings.png) Use the company's exact page name and numeric LinkedIn URL, then save the certificate branding. Members will see this page as **Company tag** when reviewing a connected LinkedIn certificate post. They still decide whether to publish and can remove the tag from their caption. These workspace settings do not connect a member's LinkedIn account or let an admin post for them. See [earn and share certificates](https://lira.thoughtly.com/docs/results/certificates). Choose **Remove LinkedIn page**, then save to stop adding that association to new certificates. Existing certificates retain a saved association. Older certificates without one can use the current page when their saved issuer name matches the current issuer. ## Privacy and rankings Use **Privacy & rankings** to review the current privacy mode and People or Teams leaderboard preferences. Privacy changes can remove access to existing data, so read the impact preview before confirming. See [workspace privacy](https://lira.thoughtly.com/docs/workspace/privacy). ## API keys Open [**API keys**](https://lira.thoughtly.com/settings/api-keys) for programmatic workspace access. This is separate from AI agent sign-in. See [manage API keys](https://lira.thoughtly.com/docs/workspace/api-keys) for access boundaries, secure storage, and revocation. ## Integrations **Connections** groups **Website**, **Files**, and **AI agents** in one list. The website and file management actions open shared knowledge controls in Company settings. ![A Connections panel groups Website, Files, and AI agents into three rows, each with a Manage action; the example AI agent state is Not configured.](https://lira.thoughtly.com/docs/images/product/integrations-connections.webp) Example setup: open the relevant management controls from one Connections list. Choose **Manage** on the **AI agents** row to connect ChatGPT, Claude, Codex, or another compatible agent. The dialog contains setup instructions, connection status, and disconnect controls. Each connection uses your current Admin access and the workspace's privacy rules. See [connect an AI agent](https://lira.thoughtly.com/docs/workspace/ai-agents). ## Security Use **Security** to turn **Require two-factor authentication** on or off. When it is on, every new and existing member, including admins, must use an authenticator app or a passkey before onboarding or workspace access. Each person chooses their method. Set up either method on your own account before turning the requirement on. See [account security](https://lira.thoughtly.com/docs/workspace/account-security) for member setup and verification steps. The switch stays disabled while your enrollment is checked, if you have neither method, or if the check fails. Follow **your account** to finish setup, then return to **Security**. If the check failed, review your account and reload the page. ## Audit log Use **Audit log** to review recorded workspace changes and support access. Filter by activity, person, outcome, or time period, inspect an event, and use **Export CSV** to download up to 1,000 matching retained events. Admin access is required. See [review and export the audit log](https://lira.thoughtly.com/docs/workspace/audit-log) for retention, privacy, and recovery steps. ## Save deliberately Settings sections have their own save or confirmation controls. Navigating away is not a substitute for saving. If a request fails, check your connection and try again; do not assume the visible edit was applied until you see confirmation. If controls are read-only or missing, verify your workspace and admin role. Your personal name is managed separately under [Your account](https://lira.thoughtly.com/docs/workspace/account). --- # Privacy, sharing, and retention > Understand what stays private, what a submission shares, and why content may become unavailable. Source: https://lira.thoughtly.com/docs/workspace/privacy Audience: everyone Last reviewed: 2026-10-28 Member practice starts private, and recording requires the applicable consent. The workspace privacy mode determines which result and sharing features are available. ## Workspace privacy modes | Mode | What it means | | --- | --- | | Submitted results | Choosing Share on a completed training attempt submits available results to authorized reviewers, adds its available score to enabled leaderboards, and creates a public replay link. | | Anonymous team scores | Consenting results contribute to team aggregates once at least five contributors are eligible. Individual scores and call content are not exposed through team rankings. | | Activity only | Participation and credential completion are retained. Detailed scores, recordings, and transcripts are not retained for later result review. | In Activity only mode, feedback may be offered temporarily after the call. Review it when it is available. The **I've read my feedback** action clears temporary feedback, and its delivery window also expires; it is not a saved result you can rely on reopening later. ## What does not happen automatically - Completing a call does not submit it to a manager. - Earning a certificate does not publish that certificate. - Publishing a certificate does not publish the conversation. - Playing a recording does not share the attempt or enable leaderboard playback. - Sharing a personal scenario does not share previous attempts, recordings, feedback, uploaded source files, or private generation jobs. - Personal practice does not become official team training automatically. ## Private authoring tests **Test call** in the scenario studio is separate from learner practice. Where policy permits, the caller can revisit feedback and available recordings or transcripts in private **Test history** for up to 90 days. No certificate, ranking entry or public replay link is created. Other editors, managers and admins do not receive access through a shared scenario or their role. Recording still requires the applicable consent and media policy. Activity-only tests keep immediate feedback temporary and do not retain audio or transcripts for later review. Closing a retained review keeps the test; deleting it removes its feedback and evidence. Stricter privacy, deletion, lost access or expiry can make a test unavailable sooner. Relaxing policy cannot restore removed content. An explicit **Review with AI** reference lets Lira use that owned test as context for authoring. It does not give the counterpart in later calls memory of earlier conversations. See [testing and iteration](https://lira.thoughtly.com/docs/manage-training/create-scenarios#test-the-scenario). ## Sharing a learner result In Submitted results mode, **Share** is an explicit choice to make the available conversation and overall score accessible to anyone with its replay link. The public page is unlisted and excluded from search indexing. Detailed skill scores, coaching, and the scoring rubric remain private. The shared score can also appear on enabled workspace leaderboards, with playback when recorded audio is available. Use **Turn off link** to revoke the public URL while keeping the submission. Withdraw the submission to remove its reviewer and ranking access and revoke the link together. See [sharing an attempt](https://lira.thoughtly.com/docs/results/submitting-and-sharing). ## Programmatic access [Workspace API keys](https://lira.thoughtly.com/docs/workspace/api-keys) and connected AI agents follow the issuing admin’s current access, scenario ownership, workspace privacy, consent, and retention rules. They do not expose another member’s private scenarios or unshared attempts. Requesting a protected recording through an API does not create a public replay link. Revoking an API key stops that credential’s requests. Use **Turn off link** on an attempt to stop access to its public replay. ## Changes and retention Authorized admins can change privacy under **Privacy & rankings**. A stricter mode can remove access to existing scores or call content and schedule its deletion. Moving later to a less restrictive mode does not restore older private or deleted content. Recordings, transcripts, and feedback can also expire under retention rules. Missing content is not necessarily a loading error. A certificate or completed assignment may remain even when the underlying call content is no longer available. For questions about your organization's expectations, contact your workspace admin. For an access or privacy problem you cannot resolve, contact [help@thoughtly.com](mailto:help@thoughtly.com) without including passwords or access tokens. --- # Connect an AI agent > Use ChatGPT, Claude, Codex, or another agent to manage training and explore permitted workspace data. Source: https://lira.thoughtly.com/docs/workspace/ai-agents Audience: admin Last reviewed: 2026-11-02 Connect your preferred AI agent to Lira to create scenarios, manage assignments, and explore submitted results. The connection uses MCP, a standard that lets an agent work with Lira's tools on your behalf. You need an **Admin** role in the Lira workspace and must finish [Getting started](https://lira.thoughtly.com/docs/get-started/first-practice) there before using an agent connection. Each person signs in with their own account, and Lira checks their current access on every request. ## Get your connection details Open [**Settings → Integrations → AI agents**](https://lira.thoughtly.com/settings/integrations#ai-agents) in Lira and choose **Manage**. The dialog contains setup instructions and your connections. Choose your client, then use **Copy setup** for its connection steps. ![The AI agents dialog shows client choices, Codex connection steps using a fictional example endpoint, Copy setup, Copy instructions, Download skill, and a first-connection state.](https://lira.thoughtly.com/docs/images/product/integrations-ai-agents.webp) Example setup with a fictional endpoint: use your workspace’s actual connection details when setting up an agent. The server address for this Lira site is: ```text https://lira.thoughtly.com/mcp ``` If you use more than one Lira environment, copy the address from the workspace you intend to manage. You do not need to create or paste an API key. Building your own integration instead? [Workspace API keys](https://lira.thoughtly.com/docs/workspace/api-keys) authenticate the tools HTTP API. The MCP endpoint shown here continues to use OAuth sign-in. ## Connect your agent Choose the app you use. Keep Lira open while you complete the sign-in in your browser. **Codex** Run these commands in your terminal, then sign in with your Lira admin account. ```sh codex mcp add lira --url 'https://lira.thoughtly.com/mcp' codex mcp login lira ``` 1. In Codex, ask Lira to show your workspace and available tools. If Lira is already configured, skip the add command and run `codex mcp login lira`. You can also manage the connection in Codex's MCP settings. [Codex MCP documentation](https://developers.openai.com/codex/mcp/) **Claude** **Claude Code** Add Lira to Claude Code from your terminal. ```sh claude mcp add --transport http --scope user lira 'https://lira.thoughtly.com/mcp' ``` 1. Open Claude Code, run /mcp, and choose Lira to sign in with your admin account. 2. Ask Lira to show your workspace and available tools. If Lira is already listed, use `/mcp` to authenticate it instead of adding it again. Trust only a project folder you recognize when Claude asks for workspace access. [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp) **Claude web, Desktop, and Cowork** Open **Customize → Connectors**, choose **Add custom connector**, and name it **Lira**. Enter the server address above, keep OAuth authentication, and complete sign-in. For Team or Enterprise workspaces, an authorized owner may need to add the connector in **Organization settings → Connectors** first. Enable Lira in the conversation's connectors menu before using it. These remote connectors require a server reachable from Anthropic's cloud, including when you use the Desktop app. [Claude custom connector documentation](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) **ChatGPT** Add Lira as a custom MCP server in ChatGPT. Availability depends on your ChatGPT plan and workspace permissions. 1. In ChatGPT, open Plugins, select +, then Add custom MCP server. 2. Name it Lira, set the server URL to https://lira.thoughtly.com/mcp, and select OAuth authentication. 3. Review the connection and tools, then sign in with your Lira admin account. 4. If you use the legacy Apps settings, choose Apps → Create, then scan the tools and sign in. Custom MCP availability depends on your ChatGPT plan and workspace permissions. An authorized workspace admin may need to create the connection. Review the requested tools and the per-server risk notice before confirming. ChatGPT needs a server reachable from its cloud. A private development address or VPN-only address may work in a local coding client while remaining unavailable to ChatGPT. Ask your Lira administrator for the public server address if this happens. [ChatGPT custom MCP documentation](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt) **Other** Use any MCP client that supports remote Streamable HTTP and OAuth. 1. Add a remote MCP server named Lira with this URL: https://lira.thoughtly.com/mcp 2. Choose Streamable HTTP and OAuth, then sign in with your Lira admin account. 3. Ask Lira to show your workspace and available tools. Your client must support remote Streamable HTTP and OAuth. Follow its connection instructions and use the Lira server address above. Setup menus, skill support, and approval controls vary by client. > **Using a private Lira environment?** > > Hosted ChatGPT and Claude connectors need a server address their service can reach. If your workspace is only available on a private network, use Codex or Claude Code on that network, or ask your Lira administrator for a supported hosted connection. ## Sign in and review access Start the connection from your agent. Your browser opens Lira's secure sign-in page, hosted by WorkOS. Sign in with your Lira account, choose your workspace, and review the requested access. Approve only a workspace you intend the agent to manage, then return to your agent to finish connecting. You need an active Admin role in the selected workspace. ![WorkOS-hosted Lira sign-in with an empty Email field and a Continue with email button.](https://lira.thoughtly.com/docs/images/product/agent-hosted-sign-in.jpg) Sign in to Lira through the secure page hosted by WorkOS. If you cancel, or the request expires or cannot be completed, start a new connection from your agent. Refreshing the old page does not create a new request. ## Add Lira's instructions In the **AI agents** dialog, select **Copy instructions** and add them to the instructions your client uses for Lira. If the client supports installable skills, choose **Download skill** instead and follow that client's installation process. You can also [read the current Lira instructions](https://lira.thoughtly.com/mcp/SKILL.md). The instructions help your agent check the workspace, find real scenario and person IDs, preserve unrelated fields, and retry changes safely. They do not replace your client's permission or approval controls. ## Try your first request Start by confirming context: > Show my Lira workspace and the training tools I can use. Your agent can confirm your workspace and Admin role with `lira_get_context`. If it reports a different workspace, reconnect and select the intended workspace during sign-in. Then give the agent a specific task, such as: - “Create an unpublished discovery scenario for our onboarding product. Show me the draft before publishing.” - “Summarize training participation and submitted results for the last 30 days.” - “Find the people assigned to this scenario and show their completion status.” Review the workspace and proposed changes before approving a write. Ask the agent to report the outcome and link to the affected item in Lira. A queued generation or ingestion job is still in progress until it finishes. ## What the connection can access Agents can work with scenarios, shared training knowledge, assignments, permitted submitted results, coaching, reports, and certificates. Existing [workspace privacy rules](https://lira.thoughtly.com/docs/workspace/privacy) still apply. Private practice and private preparation are not exposed through an admin connection. Recordings stay protected. Requesting a recording does not create a public sharing link. The connection does not manage member roles or invitations, change workspace privacy, place calls, or issue scores and certificates manually. ## Practice after working with an agent Your agent can prepare a scenario and link you to it in Lira. Open that link in the intended workspace, then choose **Start practice**. The call uses your browser and microphone. See [start a practice call](https://lira.thoughtly.com/docs/practice/start-call) for device checks and call controls. An Admin does not need an extra learner or call permission to practice in the browser. If your agent says calls require the browser, follow its scenario link. A draft or closed scenario needs the recovery shown in Lira before ordinary practice is available. Your current workspace access and scenario privacy still apply. ## Manage or disconnect an agent Return to **Settings → Integrations → AI agents** and choose **Manage** to see connection status and last successful use. Copying setup instructions does not create a connection. If Lira is waiting for the first request, return to your agent and ask it to show your workspace, then refresh the connection list. Choose **Disconnect** to stop this connection from using the workspace's tools immediately. Removing a server from your client and disconnecting it in Lira are separate actions. To use a disconnected connection again, choose **Reconnect** in Lira and sign in again if the client asks. ## Troubleshooting | What you see | What to check | | --- | --- | | AI agents is unavailable | Confirm your Lira Admin role. Ask your administrator whether agent connections are enabled. | | The connection request expired or could not be completed | Start the connection again from your agent to open a new browser request, then complete sign-in and review access. | | “Can't verify the user is human” on a WorkOS sign-in page | WorkOS's hosted human-verification check did not succeed; this message does not mean your password is incorrect. Restart the connection and retry sign-in. If the hosted error persists, contact Lira support with the time, your region, and the exact message so it can be investigated with WorkOS. See [WorkOS's verification guidance](https://workos.com/docs/authkit/radar#troubleshoot-turnstile-verification). | | Sign-in succeeds but access is denied | Check the selected workspace and your current role. A disconnected connection stays blocked until you reconnect it in Lira. | | `onboarding_required` | Open the selected workspace in Lira, finish Getting started, then retry your agent request. An onboarding reset also pauses an existing connection until you finish again; the agent cannot complete practice for you. | | The agent says it cannot start a practice call | Open the scenario in Lira and select **Start practice**. Calls run in your browser. An agent's browser requirement does not mean your account needs another permission. | | The server cannot be reached | Check the address and network access. Hosted clients cannot reach a private or VPN-only server by default. | | A scenario changed while you were editing | Ask the agent to read the latest version before applying your change again. | | A request times out | Ask the agent to check whether the action completed before retrying. Do not repeat a create request with a new retry key. | | A transcript, recording, or score is missing | Check submission status and privacy settings. Missing access is not something the agent can override. | For training setup, see [create a scenario](https://lira.thoughtly.com/docs/manage-training/create-scenarios). For shared results, see [review submitted results](https://lira.thoughtly.com/docs/manage-training/reviewing-results). --- # Manage email notifications > Choose your reminders and understand the training, invitation, and account emails Lira sends. Source: https://lira.thoughtly.com/docs/workspace/email-notifications Audience: everyone Last reviewed: 2026-10-28 Lira emails help you keep track of invitations, assigned training, and important account changes. Emails link back to Lira. Recordings, transcripts, scores, and coaching notes stay inside the app. ## Read a Lira email Branded Lira emails use the Thoughtly Lira wordmark, with header colors and artwork that vary by message. The message explains what changed and provides one main action, such as **Accept invitation** or **View training**. Its details and action remain available if your email app blocks images. ![A workspace invitation with the Thoughtly Lira wordmark, workspace name, invitation expiry, and Accept invitation button.](https://lira.thoughtly.com/docs/images/product/lira-email-invitation.png) Review the workspace and invitation expiry before accepting. Sign-in and verification emails keep the code near the top. Never share a code or password-reset link. If a message is unexpected, open Lira directly or [contact support](mailto:help@thoughtly.com). ## Choose your reminders Open the workspace menu, select **Your account**, then choose the [**Email notifications** tab](https://lira.thoughtly.com/settings/email). Learners, managers, and admins can manage their own preferences here. Changes save when you switch an option on or off. ![Settings navigation with Email notifications selected beside separate switches for Training reminders and Weekly team summary.](https://lira.thoughtly.com/docs/images/product/email-notifications.webp) Choose training reminders and the weekly summary in the Email notifications tab. - **Training reminders** controls reminders about incomplete assignments and certificates approaching or reaching expiry. - **Weekly team summary** controls the Monday summary for people who manage a team. A summary is sent only when current direct reports have overdue training. These choices apply to your current workspace. You can also use **Manage email preferences** at the bottom of a reminder email. That link opens the settings for the workspace that sent it. Wait for your preferences to load before changing an option. If they cannot be loaded, check your connection and choose **Try again**. If saving fails, your previous choice is restored and an error appears. Try again before leaving the page. Account security emails, invitations, and essential training confirmations are still sent when reminders are off. Turning off reminders does not change your assignments or their due dates. ## Assigned training and deadlines You receive an email when training is assigned to you. Assignments created together are grouped in one email. A welcome email can include your first assignments when you join a workspace. For incomplete training, reminders begin after three days and repeat weekly. An assignment with a due date also has reminders three days before the deadline and on the due date. Overdue reminders follow on days one, three, and seven, then weekly. Scheduled reminders use 9 a.m. in your workspace's time zone. Weekend reminders move to the next weekday. Eligible training is combined into one reminder per workspace per day, and its current status is checked before sending. A qualifying attempt that meets the scenario's certificate requirements completes the assignment—even when the attempt stays private. Completion stops training reminders. Submitting an unsuccessful attempt does not stop them. A changed deadline or removed assignment can trigger an update if it was already announced to you. Removal stops reminders for that assignment. ## Invitations and account access Workspace invitations arrive immediately, with follow-up reminders after three and six days while the invitation remains valid. Reminders stop when it is accepted, revoked, or expired. An expired invitation does not renew automatically; contact your workspace admin if you need a new one. Sign-in codes, verification codes, and password-reset links arrive when requested. A successful password reset also produces a confirmation. Never share your codes or password-reset links. ## Practice, coaching, and certificates Submitting an attempt produces a confirmation. If processing takes longer than two minutes, Lira can notify you when feedback becomes available. New coaching produces an email that opens the app; the note itself is not included in the email. Completing training produces one confirmation with a link to your certificate. Certificates with an expiry date have reminders 30 and seven days before expiry, followed by an expiry notice. Certificates with no expiry do not receive expiry reminders. Revocation produces an essential status update. ## If an email is missing Check your spam folder, the email address shown in **Your account**, and your notification choices. A completed assignment, expired invitation, removed membership, or replaced certificate may no longer need its earlier reminder. For an invitation or sign-in problem, see [account access help](https://lira.thoughtly.com/docs/troubleshooting/access). For assistance with email delivery, contact [help@thoughtly.com](mailto:help@thoughtly.com). --- # Set up two-factor authentication and passkeys > Protect your account, verify a required sign-in, and manage your workspace's security requirement. Source: https://lira.thoughtly.com/docs/workspace/account-security Audience: everyone Last reviewed: 2026-10-25 An authenticator app adds a six-digit code to sign-in. A passkey lets you sign in with your fingerprint, face, screen lock, or security key. Your workspace can require two-factor authentication; either method meets that requirement. ## Open account security Open the workspace menu and choose **Your account**. Find **Account security** below your profile details. These methods belong to your account and protect it across your workspaces. Only you can enroll or remove your own methods. ![Account security with Authenticator app and Passkeys rows, both marked Not set up, and messages explaining that the methods are unavailable.](https://lira.thoughtly.com/docs/images/product/account-security.webp) Your account lists security methods and explains when one is unavailable. ## Verify your email Before adding or removing a method, Lira opens **Verify your email**. Enter the six-digit code sent to your account email, then choose **Verify code**. Use **Send new code** if you need another email. The dialog closes when verification succeeds and the security change continues on the page. Choose **Cancel**, close the dialog, or press **Escape** to leave verification. ![Verify your email dialog with an empty Email verification code field, Send new code, Cancel, Verify code, and a close button.](https://lira.thoughtly.com/docs/images/product/security-email-verification.webp) Confirm your account email before adding or removing a security method. ## Set up an authenticator app 1. In **Authenticator app**, choose **Set up**. 2. Verify your email in the dialog. 3. Scan the QR code with your authenticator app, or enter the setup key in the app. 4. Enter the six-digit **Authenticator code** from the app and choose **Verify and enable**. Wait for **Your authenticator app is ready.** before leaving. The authenticator status changes to **On**. Keep the authenticator entry so you can retrieve codes when signing in. > **Keep setup details private** > > The QR code and setup key can give someone access to your authenticator codes. Never share them, include them in a screenshot, or send them to support. ## Add a passkey 1. In **Passkeys**, choose **Add passkey**. 2. Verify your email in the dialog. 3. Choose **Create passkey**, then follow your device or password manager's prompt. Wait for **Your passkey is ready.** and check that the passkey appears in the list. You can add more than one passkey. If you cancel the device prompt, you can choose **Create passkey** again or **Cancel** to leave setup. If you are completing required setup, adding the passkey takes you to **Verify this sign-in**. Choose **Sign in with a passkey** to use your new passkey before continuing. If Lira says your browser does not support passkeys, open it in a compatible browser. If either security method is unavailable, contact your workspace admin before changing anything. ## Verify a required sign-in The **Secure your account** screen appears when your workspace requires a method you have not set up, or your current sign-in still needs verification. Complete this screen before onboarding or returning to the workspace. ![Secure your account screen offering Use authenticator app and Sign in with a passkey, with Start again and Sign out below.](https://lira.thoughtly.com/docs/images/product/security-verification.webp) Verify this sign-in with an authenticator app or a passkey. If you have not enrolled a method, follow the setup steps on this screen. If you already have one, use **Use authenticator app**, enter its current code, and choose **Verify and continue**. Alternatively, choose **Sign in with a passkey** and complete the sign-in prompt. Either method meets the workspace's two-factor requirement. Signing in with a password or an email code alone does not satisfy a workspace's two-factor requirement. Adding a passkey also needs the separate passkey sign-in step. Switching workspaces can require verification. **Sign out** lets you return with a different account. Choose **Start again** to restart setup or verification. If an authenticator challenge expires, begin a new verification and enter the latest code from your app. ## Replace or remove a method Add and verify a replacement before removing a method you still need. Choose **Remove** beside the authenticator or passkey, review the confirmation, then verify your account email in the dialog to complete removal. Removing a method does not remove your workspace membership. If any of your active workspaces requires two-factor authentication, keep an authenticator app or at least one passkey. You can choose either method. Add a replacement before removing your last method. If no workspace requires two-factor authentication, you can choose which methods to keep. A disabled **Remove** control explains which required method you need to retain. An admin cannot enroll a personal method for you. ## Require security for a workspace Workspace admins can open **Settings → Security** and turn **Require two-factor authentication** on or off. Set up an authenticator app or a passkey on your own account before turning it on, then choose **Save changes**. ![Workspace Security settings with Require two-factor authentication switched on and Save changes below.](https://lira.thoughtly.com/docs/images/product/workspace-security.webp) Turn two-factor authentication on or off for every member, including admins. If the switch is disabled, follow **your account** to finish setting up an authenticator app or a passkey, then return to **Security**. Lira keeps the control unavailable until it confirms that your account has a method. If the enrollment check fails, review your account and reload the page after checking your connection. ![Workspace Security with the two-factor switch disabled and a First, add an authenticator app or a passkey in your account message linking to account settings.](https://lira.thoughtly.com/docs/images/product/workspace-security-disabled.webp) Set up a personal method before changing the workspace requirement. | Setting | What members need | | --- | --- | | Off | Each person decides whether to add an authenticator app or a passkey. | | On | An authenticator app or a verified passkey. Each person chooses their method. | The saved requirement applies to new and existing members, including admins. People complete setup or verification before they can enter the workspace. The requirement changes account access; it does not change roles or [practice privacy](https://lira.thoughtly.com/docs/workspace/privacy). If another admin changed the requirement while you were editing, refresh and review the current setting before saving again. If security is unavailable, follow the message to contact support. ## Recover from a problem For an incorrect authenticator code, use the latest six-digit code from the correct Lira entry. For an expired email verification, restart the change and request a new code. Wait before retrying if Lira reports too many attempts. If your email is verified but the next setup or removal request fails, choose **Continue** to retry the security change. If verification has expired, cancel and start again for a fresh code. If you lose a device, use another enrolled method that meets your workspace's requirement. If none is available, contact [help@thoughtly.com](mailto:help@thoughtly.com) from your account email. Never send passwords, verification codes, setup keys, QR codes, or security-key details. See [access troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/access) for invitation and permission problems. --- # Review and export the audit log > Find workspace changes and support access, inspect an event, and export matching activity. Source: https://lira.thoughtly.com/docs/workspace/audit-log Audience: admin Last reviewed: 2026-10-24 Workspace admins can open **Settings → Audit log** to review activity in the selected workspace. Managers and trainees cannot view or export this history. Confirm your workspace before investigating a change. On narrower screens, use the **Settings** section menu to choose **Audit log** or move to another settings section. ## Find an event The audit log shows activity recorded by Lira, including supported changes to people, teams, scenarios, assignments, certificates, workspace settings, and AI agent connections, alongside support access. It is not a history of every page visit or private practice conversation. New event coverage starts when that capability becomes available; earlier actions are not reconstructed. Use **All activity**, **Successful**, **Denied**, or **Errors** to choose an outcome. Search activity or people, choose a time period, or use **Filter activity** to select an activity type or person. Filters stay in the page URL so refreshing or using Back preserves your view. ![Audit log with fictional workspace activity, outcome tabs, search, a time period, Filter, Refresh, and Export CSV controls.](https://lira.thoughtly.com/docs/images/product/audit-log.webp) Find workspace activity and export the matching retained history from the same view. Select **Refresh** to load the latest activity. **Older activity** opens the next page; **Newest** returns to the first page. If an older page has expired or its filters changed, choose **Newest activity** and try again. ## Inspect activity Each row shows the activity, person, date and time in UTC, and result. Select its activity label to reveal the event ID, affected resource, and available operation or support-session details. Select the label again or **Close event details** to collapse it. **Successful**, **Denied**, and **Error** describe the action's outcome. **Syncing** or **Delivery delayed** describes delivery to the audit provider; it does not mean an otherwise successful workspace change failed. Delayed delivery can recover without repeating the original action. Audit events contain action and access information, including actor names and resource identifiers. They do not expose scenario text, prompts, scores, transcripts, recordings, credentials, or tokens. The audit log does not grant access to private practice results or bypass the workspace's privacy rules. ## Export matching activity Choose **Export CSV** to prepare a file using the current search, outcome, time period, activity, and person filters. The export includes all matching retained events, including matches beyond the page currently displayed. It does not export only the visible page. An export supports up to **1,000 matching events**. If more match, narrow the time period or other filters, then export again. Lira reports the limit instead of silently leaving events out. Wait for **CSV download prepared** and check your browser's downloads. If preparation fails, your filters remain available. Check your connection and choose **Export CSV** again. If your session or access changed, sign in again and confirm that you still have an active Admin role in the correct workspace. CSV export requires your own workspace Admin session. Exported files contain audit information. Share and store them according to your organization's access and retention requirements. ## Retention and unavailable history The page displays the workspace's audit retention period. Each selected time range is limited to retained events; **All retained activity** does not include expired history. The log reads Lira's recorded events and applies the workspace's current audit-provider retention policy. It does not import unrelated provider events. If the history or retention policy cannot be loaded, select **Try again**. Lira does not show an unlimited or unverified history when that policy is unavailable. **No matching activity** means the current filters found no events; clear the filters or select a different time period. **No activity recorded yet** means no events are available in the selected retained window. See [workspace settings](https://lira.thoughtly.com/docs/workspace/settings-and-branding) for configuration changes, [privacy and retention](https://lira.thoughtly.com/docs/workspace/privacy) for practice data, or [contact support](https://lira.thoughtly.com/docs/troubleshooting/contact-support) if an issue persists. --- # Manage API keys > Create and revoke credentials for programmatic workspace administration. Source: https://lira.thoughtly.com/docs/workspace/api-keys Audience: admin Last reviewed: 2026-10-27 Open [**Settings → API keys**](https://lira.thoughtly.com/settings/api-keys) in the workspace you want to manage. Only active workspace admins who have finished [Getting started](https://lira.thoughtly.com/docs/get-started/first-practice) can create and manage these credentials. API keys let your own software use Lira’s supported programmatic admin capabilities. They do not create additional permissions, workspace members, or usage allowance. Your current role, the workspace’s privacy settings, scenario ownership, and retention rules still apply. ![The API keys page shows fictional CRM automation and Weekly reporting entries, Workspace access, last-used dates, Revoke actions, search, and Create key; no secrets are displayed.](https://lira.thoughtly.com/docs/images/product/workspace-api-keys.webp) Example key metadata: review access and usage without exposing credentials. ## Create and store a key Choose **Create key** and give the integration a recognizable **Key name**. Select **Create key** in the dialog, then **Copy key** and store the value in your server or secret manager. Choose **I’ve saved it** when finished. The full secret is shown only once; Lira cannot display it again later. ![The unsubmitted Create API key dialog shows a Key name field with a Production integration placeholder, Cancel, and Create key.](https://lira.thoughtly.com/docs/images/product/workspace-api-key-create.webp) Example setup: name the integration before creating its credential. Never put a key in a URL, browser code, email, screenshot, or AI chat. Use the authentication mechanism your integration supports and keep credentials outside prompts and source control. ## Choose the right connection For an interactive AI agent, use [**Integrations → AI agents**](https://lira.thoughtly.com/docs/workspace/ai-agents) and the client’s OAuth sign-in. You do not need to create an API key or paste one into the conversation. For your own programmatic integration, a **Workspace** key supports the registered admin tools through the tools API. The tools API has a capability catalog at `GET /api/v1/tools` and executes a named capability at `POST /api/v1/tools/{name}`. It does not add unsupported dashboard actions or change the OAuth-only MCP connection. ## Use the tools API Send the key in the `Authorization` header to retrieve the supported tool names and their input schemas: ```http GET /api/v1/tools Authorization: Bearer ``` Call a returned tool by its exact name. For example, this read confirms the connected workspace: ```http POST /api/v1/tools/lira_get_context Authorization: Bearer Content-Type: application/json {} ``` The request body is the tool’s plain JSON arguments, not a JSON-RPC envelope. Follow the returned input schema. Writes require a UUID `idempotencyKey` in that JSON; reads do not. Reuse the same key and arguments when recovering an uncertain write instead of creating a second operation. The tools API accepts bodies up to 1 MiB and limits each key to 120 requests per minute. Handle authorization, validation, conflict, and rate-limit errors before retrying. The protected recording and certificate download URLs returned by the tools accept the same workspace key in their `Authorization` header. Each download rechecks role, privacy, consent, and retention. Retrieving a descriptor never publishes private content. The `/mcp` protocol endpoint itself continues to require OAuth. ## Understand the access boundary Keys are tied to their issuing admin and workspace. They stop working when revoked or when that admin no longer has active Admin access. If the admin has not finished Getting started, including after an onboarding reset, requests return `onboarding_required` with HTTP 403. The admin must open that workspace in Lira and finish Getting started, then retry with the existing key. An integration cannot complete the practice for its owner. Creating a key never bypasses a private scenario’s ownership, makes an unshared result available, or publishes a recording. The supported admin tools can work with permitted scenarios, shared knowledge, assignments, submitted results, reports, and existing certificates. They do not provide member-role administration, workspace privacy changes, live-call control, or manual score or certificate issuance. ## Revoke or replace a key Return to **Settings → API keys**, choose **Revoke** for the key, and confirm **Revoke key** when its integration is retired or its secret may have been exposed. Revocation stops further authenticated requests. It does not delete scenarios, reset usage, or revoke existing public replay links. To replace a key, create a new one, update your integration’s secret, verify an authorized request, and revoke the old key. If a secret was exposed, revoke it immediately rather than waiting for the replacement to be deployed. Related: [connect an AI agent](https://lira.thoughtly.com/docs/workspace/ai-agents), [workspace privacy](https://lira.thoughtly.com/docs/workspace/privacy), and [workspace settings](https://lira.thoughtly.com/docs/workspace/settings-and-branding). --- # Fix microphone and audio problems > Check permissions, choose the correct device, and recover when you cannot hear or be heard. Source: https://lira.thoughtly.com/docs/troubleshooting/microphone-and-audio Audience: everyone Last reviewed: 2026-10-22 Start with the **Ready to practice?** check before opening a new call. It tests your input and speaker separately so you can identify which side is failing. ## Lira cannot access your microphone 1. Use **Enable microphone** and allow the browser's permission request. 2. If access was blocked earlier, open the browser's site settings for Lira and allow microphone access. 3. Check your operating system's microphone permissions for that browser. 4. Return to Lira and try the microphone check again. If the browser says microphone access is unavailable, open Lira in a browser with microphone support over a secure connection. Managed devices may require your IT team's help to enable access. ## The wrong microphone is selected Choose the intended input in the microphone selector. Speak and watch for an input response. Check any physical mute switch and the operating system's input level. If a device disconnects, reconnect it and run the check again. A Bluetooth headset may appear as a different input after reconnecting. ## Your microphone is busy Close other calling or recording applications that may be holding the device, then try again. If needed, disconnect and reconnect the microphone before returning to the check. ## You cannot hear the test or counterpart Use **Test speaker**. Check system volume, the selected output device, browser tab mute, and headset connections. During a call, use any audio-enable action shown if the browser has blocked playback. For echo or feedback, use headphones and move the microphone away from the speakers. Avoid having the same conversation open with audio on more than one device. If audio worked and then stopped, check the [connection state](https://lira.thoughtly.com/docs/troubleshooting/connection). If the problem persists, contact [help@thoughtly.com](mailto:help@thoughtly.com) with the browser and device you are using and the error text. Do not send passwords or permission tokens. --- # Recover from a connection problem > Handle reconnecting calls, unavailable practice, and interrupted saves without losing context. Source: https://lira.thoughtly.com/docs/troubleshooting/connection Audience: everyone Last reviewed: 2026-10-22 Check the state shown in Lira before starting a second action. A call that is reconnecting, ending, or processing is different from a call that never started. ## The call is reconnecting Pause speaking and give Lira time to reconnect. Check that your internet connection is working and that the microphone is still connected. Keep the tab open. If the call shows a recovery action, use that action to return to the current call. Repeatedly selecting Start practice or opening additional tabs can make it harder to tell which attempt you are reviewing. ## Practice is unavailable Wait for **Preparing practice…** to resolve. If the action becomes **Practice unavailable**, the workspace's current call service or the scenario's voice setup may not be available. Check whether another published scenario is available. If only one scenario is affected, ask its author or a workspace admin to review its call settings. Changing your microphone permissions will not repair an unavailable scenario configuration. ## Ending or saving was interrupted If Lira offers **Retry end**, use it to finish the current attempt. After an interrupted call, check **Progress** or the scenario's **Recent attempts** before assuming no attempt was created. For an interrupted settings save or assignment action, keep the page open, restore connectivity, and use the retry or save control. Check the visible confirmation or updated record before repeating a bulk action. ## Check local conditions - Confirm that other websites load. - If you are switching networks, wait for the connection to settle. - If a managed network blocks calling, ask your IT team for help. - Avoid refreshing during an active call unless recovery guidance specifically requires it. An interrupted conversation is scored on the dialogue that was captured. If no usable conversation evidence is available, the attempt cannot be evaluated; see [feedback troubleshooting](https://lira.thoughtly.com/docs/troubleshooting/feedback). If the issue continues, contact [help@thoughtly.com](mailto:help@thoughtly.com) with the approximate time, scenario, browser, and error message. Avoid including private transcript content unless it is necessary and you are authorized to share it. --- # Find missing or incomplete feedback > Distinguish a preparing score, streamed coaching, and unavailable call content. Source: https://lira.thoughtly.com/docs/troubleshooting/feedback Audience: everyone Last reviewed: 2026-10-28 Open the original attempt from **Progress** or the scenario's **Recent attempts**. Its state is more useful than starting a new call to check whether the previous one saved. ## Feedback is still processing If the page says **Call complete** and **Preparing your feedback**, the call has ended and the result is being prepared. The page updates automatically. You can leave and return to the same attempt; reopening it does not restart grading. Lira automatically tries a second evaluator if the first one cannot provide valid feedback. ## My score is ready but coaching is still appearing **Preparing your coaching…** means the score has been saved and the written explanation is still arriving. The summary, skill observations, and next steps update as they are written. An earned certificate does not have to wait for that text. Coaching does not regrade the conversation or change certificate eligibility. Keep the page open, or return to the same attempt later. If the text stops updating after a connection interruption, refresh the page to reconnect to the latest saved feedback. Refreshing does not place another call, create a second certificate, or restart grading. The page stops waiting when its coaching preparation window ends. **Written coaching couldn’t be prepared. Your score is still available.** means only the written explanation is unavailable. The saved score, supporting evidence, and any earned certificate keep their existing access and privacy rules. Review the rubric and any available playback before choosing your next practice focus. **Retry feedback**, described below, applies to unsuccessful grading; it does not regrade a saved score to recover missing coaching. ## Feedback could not be prepared **We couldn’t prepare feedback** means grading did not finish successfully. It does not mean you performed poorly or that you must immediately repeat the call. An attempt with unavailable feedback can’t be shared. Any permitted recording or transcript remains available separately. If you own the attempt and **Retry feedback** is visible, select it to retry the same conversation once. You do not need to place another call, and this does not use another practice attempt. Wait for the result to update before deciding whether to practice again. Repeated clicks or reopening the page do not create more retries. ![A completed practice call with the We couldn’t prepare feedback message and a Retry feedback button.](https://lira.thoughtly.com/docs/images/product/feedback-retry.webp) Retry feedback for the same conversation when recovery is available. The retry is available only while the original temporary conversation evidence is still available and your access permits it. It does not extend retention. Another person’s result link or workspace admin role does not grant permission to retry their private feedback. If **Retry feedback** is absent, the retry may already have been used, the evidence may have expired, access may have changed, or the conversation may not be assessable. Exceptionally large conversation input cannot be retried. Review any available playback and start a new practice when ready. Contact support if a recorded conversation repeatedly cannot be graded; there is no need to submit an attempt merely to make feedback appear. ## The attempt is not scored Short or unsuccessful conversations still receive scores when usable dialogue was captured. Skills not demonstrated receive zero; a counterpart ending the call does not by itself prevent scoring. **Not scored** means evaluation could not be completed, for example because the call never connected, the conversation evidence is unavailable, or feedback processing failed. It is different from receiving zero for performance. Reopen the attempt to check its status, and contact support with the attempt page if a recorded conversation remains unscored. ## Recording or transcript is missing Recording, transcript, and feedback are separate pieces of an attempt. One may be present while another is still preparing or unavailable. Empty media panels are hidden, so a score can appear without a player, or a transcript can appear on its own. A recording that is still saving can appear after the score. Use a visible retry control for a failed load. Content can also become unavailable because of privacy, retention, or access changes. Reloading cannot recreate a recording that was not saved or restore deleted content. ## Temporary feedback disappeared In **Activity only** mode, detailed feedback arrives as one temporary result. It clears after acknowledgment or when its delivery window ends. Reopening or reconnecting does not extend that window. The workspace may still retain participation and certificate completion. See [privacy and retention](https://lira.thoughtly.com/docs/workspace/privacy). ## A score seems inconsistent Compare the feedback with the transcript, recording, and the requirements saved with that attempt. Displayed values can be rounded, and current scenario settings may belong to a newer version. For unresolved issues, contact [help@thoughtly.com](mailto:help@thoughtly.com) with the attempt page, approximate time, and visible status. Do not include passwords or access tokens. --- # Resolve sign-in and workspace access > Find the right account, complete security verification, handle invitations, and understand missing permissions. Source: https://lira.thoughtly.com/docs/troubleshooting/access Audience: everyone Last reviewed: 2026-10-24 Start by checking your sign-in email and selected workspace. Most missing-scenario or permission problems are specific to one of those two things. ## Your workspace is missing Open the workspace menu and check the available workspaces. Confirm that you signed in with the email address that received the invitation, not a personal address or a different work alias. If needed, sign out and return using the invited account. Ask the workspace admin to check your active membership if the workspace still does not appear. ## An invitation does not work The invitation may have expired, been revoked, or already been accepted. Ask the sender to check its status and retry or replace it if appropriate. If you are signed into another account, sign out before accepting the invitation with the intended email address. Do not forward an invitation to another person as a way to grant them access; they need their own invitation. ## You see access pending Signing in establishes your identity, but does not by itself grant membership in a workspace. Contact the workspace admin or the person who invited you so they can confirm that access is active. ## A page or control is unavailable Your role and reporting relationships determine which actions you can take. For example, trainees do not author scenarios, and managers cannot edit another author's scenario or review an unrelated person's submission. A scenario may also have been closed, an assignment removed, or a submission withdrawn. A missing replay or certificate link may have been made private. These cases do not necessarily indicate a sign-in error. In **Settings → Security**, the two-factor switch stays disabled until Lira confirms that you have an authenticator app or a passkey. Use **your account** beside the switch to finish setup. See [account security](https://lira.thoughtly.com/docs/workspace/account-security). ## You see Secure your account Your workspace requires two-factor authentication before onboarding or workspace access. Use an authenticator app or a passkey; either method meets the requirement. If a method is already enrolled, verify this sign-in using it. A password or email code alone does not satisfy the requirement. Use the latest authenticator code, request a new email code in the verification dialog if it expired, or retry a cancelled passkey prompt. Choose **Start again** to restart setup or verification. If you lost access to every method, contact support from your account email. See [account security](https://lira.thoughtly.com/docs/workspace/account-security) for setup, replacement, and recovery steps. ## Password or sign-in trouble Use the recovery option provided on the sign-in screen. Only use the sign-in methods actually offered for your workspace. If recovery fails, contact [help@thoughtly.com](mailto:help@thoughtly.com) from the address associated with the account. Never send a password, sign-in code, or access token to support. For role changes, contact a workspace admin; see [workspaces and roles](https://lira.thoughtly.com/docs/get-started/workspaces-and-roles). --- # Contact support > Share beta feedback about your current screen or get help from Thoughtly Lira. Source: https://lira.thoughtly.com/docs/troubleshooting/contact-support Audience: everyone Last reviewed: 2026-10-27 Use the small blue **Beta** button to report an issue or suggest an improvement. For help with your account or a conversation with support, use the Messenger or email below. ## Share beta feedback Select **Beta** to open **Share beta feedback**. In your workspace, find it beside the question-mark Help button in the top-right header on desktop and mobile. Before sign-in, during onboarding, and on other pages including the help center, find it beside the Lira logo. Hover over **Beta**, or focus it with the keyboard, to see “Help shape Lira”. On touch screens, tap **Beta** to open the feedback form directly. ![The small blue Beta button immediately before Help and Notifications in the workspace header.](https://lira.thoughtly.com/docs/images/product/beta-workspace-entry-point.webp) In your workspace, select Beta beside Help in the top-right corner. ![The small blue Beta button beside the Thoughtly Lira logo in the sign-in header.](https://lira.thoughtly.com/docs/images/product/beta-entry-point.webp) Select Beta beside the logo to share feedback. 1. Choose whether you are reporting an issue, suggesting an idea, or sharing other feedback. 2. Describe what happened and what you expected. For an issue, include the steps needed to reproduce it. 3. Optionally select **Add screenshot**, review the preview, and remove it if you do not want to include it. The capture shows your current screen’s layout with text, form values, and media masked. 4. Complete the security check if prompted, then send your feedback. ![The Share beta feedback dialog with a feedback category, message field, current-screen context, optional screenshot, and send button.](https://lira.thoughtly.com/docs/images/product/beta-feedback.webp) Send feedback about the screen you are using without leaving it. Lira includes a redacted screen path with your message so the product team knows which area you are using. It removes page IDs, link tokens, query parameters, and fragments. A small diagnostic summary includes your browser family and version, viewport size, connection status, and recent browser error types and counts. It excludes error messages, stack traces, raw console or network logs, request contents, and account or workspace identities. Screenshots are captured only when you select **Add screenshot** and are attached only when you send the form. The preview masks all page text, entered values, and media; it does not include other tabs or browser controls. Recordings, transcripts, and scores are not attached. Share only the details needed to explain your feedback; never include passwords, login codes, or access tokens. A confirmation with a reference means your feedback reached the product team's triage queue. If sending fails, your text stays in the form so you can try again. If a screenshot cannot be captured, you can still send your feedback without one. If feedback or its security check is unavailable, use [help@thoughtly.com](mailto:help@thoughtly.com). If the security check cannot load or stops responding, close and reopen the feedback form to retry. Your draft stays available on the same page. Complete any security prompt before sending. ## Open support chat Sign in to Lira, then open the question-mark menu in the top-right corner and choose **Contact support**. You can also use the chat button in the lower-right corner. While creating or editing a scenario, use the question-mark menu; the floating chat button stays hidden to leave the editor clear. The **Thoughtly Lira** Messenger is available to admins, managers, and trainees. ![The header's question-mark menu with Contact support selected above Onboarding guide and Documentation.](https://lira.thoughtly.com/docs/images/product/help-menu.jpg) Choose Contact support to open the Messenger. ## Start a conversation Opening the Messenger does not send a message. Choose the option to send a message and describe what you need help with. Include the page you were on and what you expected to happen. Sending a support message does not submit a practice attempt or publish a replay. ![The support Messenger’s Messages tab with no previous messages and a Send us a message button.](https://lira.thoughtly.com/docs/images/product/contact-support.png) Choose Send us a message to start a support conversation. Your account ID, name, email, and signup date identify you to support. Lira does not automatically attach practice recordings, transcripts, scores, or scenario instructions to your message. Share only the details needed to explain the issue. ## During practice The chat launcher is hidden while the practice-call controls are visible, so it does not cover **End**, **Mute**, or other call actions. **Contact support** also respects this pause. Close the call controls when you are finished to bring the chat button back. ## If the chat button is missing Make sure you are signed in and have closed the practice-call controls. Try **Contact support** in the question-mark menu, or reload the page if the Messenger has not loaded. Browser extensions or a managed network may block the support widget. If Lira reports that support chat is unavailable, try again or use email. You can also email [help@thoughtly.com](mailto:help@thoughtly.com). Do not include passwords, login codes, or access tokens. The Messenger session is cleared when you sign out. Public replay and certificate pages do not identify their visitors to support.