Help center

Help articles

• Perspective Transcribe · Everyone

  Get started with Perspective Transcribe

  You recorded the conversation because you wanted to remember something. Perspective Transcribe helps you get back to what was said, read the important points, and find the part you need.

• Perspective Transcribe · Everyone

  Record, pause, and save a conversation

  A short pause does not have to become a separate recording. You can pause, collect your thoughts, and continue in the same session.

• Perspective Transcribe · Everyone

  Transcribe an audio file or an audio link

  You do not have to record something again just to get a transcript. If you already have the audio, you can bring it into Perspective Transcribe.

• Perspective Transcribe · Everyone

  Read a transcript and check what was said

  A transcript is useful because you can come back to the words. But speech recognition can miss a name, confuse a phrase, or struggle when people talk over each other. Check important details against the recording.

• Perspective Transcribe · Everyone

  Use a summary and ask questions about a recording

  Sometimes you need the whole conversation. Sometimes you just need to know what was decided. Summary and Chat help you start with that question.

• Perspective Transcribe · Everyone

  Find follow-ups and add them to Reminders

  A task is easier to follow through on when it is somewhere you will look for it. Action Items brings together the tasks the app finds in your recordings, and you can add an item to Apple Reminders.

• Perspective Transcribe · Everyone

  Listen again, export a transcript, or share audio

  You may want to hear the original explanation, send someone the transcript, or keep a copy outside the app. Those are separate choices, and you can choose the one you need.

• Perspective Transcribe · Everyone

  Check, restore, or manage All Access

  Perspective Intelligence All Access is the subscription used for additional Transcribe features. You can check it from inside the app without guessing whether a missing control is a recording problem.

• Perspective Transcribe · Everyone

  Understand storage, iCloud, and deleting recordings

  On-device processing and iCloud storage answer different questions. Processing is how the app turns audio into text and works with that text. Storage is where the saved recordings and results are kept.

• Perspective Transcribe · Everyone

  When recording or transcription does not work

  Start with the message the app gives you. Recording, downloading a model, transcribing, and creating a summary are different stages, and each can need a different fix.

• Perspective Transcribe · Everyone

  Record on Apple Watch and review it on iPhone

  Apple Watch gives you a quick way to capture audio. The recording is sent to iPhone for processing, so the Watch and phone have different jobs.

• Perspective Transcribe · Everyone

  Capture an app and your microphone on Mac

  Quick Capture is for a conversation happening in a Mac app. You choose the app and give it a keyboard shortcut, then use that shortcut to start and stop capturing its audio together with your microphone.

• Start Testing · Everyone

  Sign in and join your team

  An account is how you sign in. An organization is the workspace you join. If you can sign in but cannot find your team's work, check the organization before creating another account.

• Start Testing · Everyone

  Report a bug your team can reproduce

  A useful bug report tells the next person what you did, what you expected, and what happened instead. You do not need to know why the app failed to report it clearly.

• Start Testing · Everyone

  Find your work and update an item

  The Items list is easier to use when it shows the work you need right now. Start with the filters, then open an item before changing its details.

• Start Testing · Everyone

  Add details and mention a teammate

  A comment keeps the next piece of information with the original report. Use it to answer a question, add a test result, or explain that you can still reproduce the problem.

• Start Testing · Everyone

  Send work for review and follow the response

  When you need someone else to check the work, send it for review with enough context for them to make a decision. Approvals keeps the request separate from your everyday item list.

• Start Testing · Everyone

  Approve work or explain what needs to change

  A review should tell the person doing the work whether it meets the request. If it does not, explain what they need to change so they can act on the feedback.

• Start Testing · Everyone

  Update your profile and sign-in settings

  Your profile tells teammates who you are. Your sign-in settings control how you get back into the account. You can review both without changing your role in an organization.

• Start Testing · Everyone

  Choose which notification emails you receive

  You may want assignment emails but not every other update. Personal Settings lets you change individual email categories without asking an admin to change the whole organization.

• Start Testing · Everyone

  Find a project and the right instructions

  A project brings together the work for a product or effort. Before adding or changing something, make sure you are in the intended organization and project.

• Start Testing · Everyone

  Create a project and update its details

  Give a project a name the team will recognize. You can add more detail later; the important starting point is knowing which work belongs there.

• Start Testing · Everyone

  Plan features, tasks, and milestones

  A feature describes a capability you want to build. A task is a smaller piece of work. A milestone groups work around a target, such as a release.

• Start Testing · Organization admins

  Choose the right role and project access

  Start with what the person needs to do. Someone who needs to file a bug does not necessarily need control of billing, integrations, or the rest of the organization.

• Start Testing · Organization admins

  Create or revise a custom role

  A custom role is useful when several people need the same set of permissions. Be clear about the work it should allow before selecting every checkbox.

• Start Testing · Organization admins

  Invite teammates and manage their membership

  Before inviting someone, decide which role and projects they need. The invitation is easier to get right when those choices are made together.

• Start Testing · Organization admins

  Require approval for work in a project

  Some work needs another person's check before it is accepted or finished. Project approval settings let you define who needs that check and who makes the decision.

• Start Testing · Organization admins

  Archive, delete, or restore a project

  Archiving and deleting serve different purposes. Archive a project when you want it out of the active list but may need it again. Delete it only when you intend it to enter the removal process.

• Start Testing · Everyone

  Run a report and save the results

  A report helps you answer a specific question about the work. Decide what you need to know before exporting a large list.

• Start Testing · Organization admins

  Decide what happens when work goes quiet

  Escalation draws attention to work that has gone without activity. It works best when the waiting period and the person receiving the alert are both clear.

• Start Testing · Organization admins

  Review your plan, billing, and AI access

  A missing control can be a permission problem. A message about capacity or AI credits can be a plan problem. Check which one you have before changing billing.

• Start Testing · Organization admins

  Update organization details and review activity

  Organization settings affect other people, so check the selected organization before making a change. The controls available there depend on the feature and your access.

• Start Testing · Everyone

  Ask Lyra for help and check the result

  Give Lyra a clear outcome: find a report, summarize the work, or prepare a specific change. Then check what it found and what it proposes to do.

• Start Testing · Everyone

  Understand points, achievements, and levels

  If your organization uses points and achievements, they give you another way to see recorded activity. They are optional and depend on the organization's settings.

• Start Testing · Organization admins

  Connect sources and check imported work

  Before running an import, decide which source, history, and direction you want. A manual sync should follow the saved policy you reviewed.

• Start Testing · Organization admins

  Create a key for a connected tool and retire it safely

  An API key lets a tool connect without asking you to sign in for every request. Treat it as a secret, and create it for a specific purpose you can recognize later.

• Start Testing · Everyone

  Ask support for help and follow the request

  Start with the step that failed and the message you received. You do not need to diagnose the cause before asking for help.

• Start Testing · Organization admins

  Give support temporary access to investigate

  Temporary support access can let support investigate with you without creating a permanent admin account. Only grant it when you intend that person to enter the organization.

• Start Testing · Everyone

  Work on a Help Desk ticket

  A support conversation needs a clear next step. Help Desk keeps the customer's request, your replies, and the team's internal notes together.

• Start Testing · Organization admins

  Choose a Help Desk layout and set up email

  Choose the inbox arrangement that fits how the team answers requests. One support team may want a central inbox; separate departments may prefer project inboxes.