Skip to main content

Hello! For several days now, I’ve been unable to edit text within a shape. I can still move the shape, edit text within a sticky, or other text fields. Create new shapes, and edit text within those. No other functionality issues.

What’s strange is that I am only having trouble editing text within shapes that were created on the day I first opened the board. Any sticky notes, titles, or other notes created that same day are still editable. 

I’ve shared the board with colleagues and they are running into the same issue. I’ve cleared my cache as well. I’m using the web app on my Mac, logging in behind SSO.

Any ideas on what the issue may be?

Hi ​@Melissa Biser, thanks for the clear description — that sounds unusual, especially since the issue only affects shapes created on the day the board was first opened.

 

A few things you might try or check:

  1. Locked Content (but not visually indicated)
    Occasionally, shapes may be locked in a way that doesn’t show the lock icon clearly. Try right-clicking on one of the affected shapes and see if the “Unlock” option appears.

  2. Layering or Grouping
    It's possible the shapes were grouped or placed behind other transparent objects that are preventing direct editing. You can try:

    • Right-click > “Bring to Front”

    • Use Tab or Shift + Tab to cycle through objects

    • Check if they are part of a group and temporarily ungroup them

  3. Board Permissions or App Glitch
    If multiple users are seeing the same issue and new shapes are editable, it may be a board-specific bug or content corruption. Try duplicating the board (Board settings > Duplicate) and testing whether the issue persists on the new copy.

  4. Browser Extensions or SSO Layer
    Even though you're behind SSO, some browser extensions or strict security settings can interfere with content editing. Try incognito mode or a different browser to rule that out.

 

If the issue persists even on a duplicated board, I recommend contacting Miro Support with the board link (if possible) so they can investigate logs on the backend.

 

Let me know if any of the above helps or if you'd like help testing further!


Reply