Granted full seat, but can only make specific edits

Hey ​@I8tg — welcome to Figma Forum, and thanks for flagging this. That does sound unusual. If someone has full edit access, they should be able to modify both elements and text without restrictions. I just tested this on my side and wasn’t able to reproduce the behavior, so let’s dig a little deeper together.

When you have a moment, please check in with them and confirm a few details:

• Can they review if any of the layers they’re trying to edit are locked: Lock and unlock layers?
• Are they seeing any error messages, or is the text layer simply not responding to edits?
• If they select the text layer from the left panel first, does that allow them to edit?
• Does this happen in the browser, the desktop app, or both?
• If they’re using the Figma Desktop App, can they make sure they’re on version 125.10.8 or later?

A few designers in the community have also surfaced similar scenarios and shared what worked for them. When they have time, could they take a look at the thread linked here and let us know if any of suggestions help: Can’t edit the text layer while double clicking the text layer, or any kind of text?

If the issue continues after that, a quick walkthrough would be helpful — either a screenshot or a short recording showing the layers panel and the steps that lead to the unexpected behavior. With those details, we’ll be able to zero in on what’s going on and move forward.

Appreciate you sticking with us on this. Keep me posted on how it’s going!

Thanks for your reply ​@Tom Reem, and your thoughtful suggestions. My client is using the browser version—Chrome—for Windows (apparently a recent version, as I can tell from our Zoom meetings). He’s not seeing any error messages. I’ve had him restart it several times to no avail. He grew frustrated and asked me to remove his seat; he’s just been having me make the changes which is fine.

As for your other questions, I haven’t asked him about these, but I can if he wishes to try it again.

Thanks for the update, ​@I8tg — thanks for the update, and sorry for the frustration here. We definitely want to make sure this is working as expected.

I’ve gone ahead and opened a ticket with our Product Support team so they can take a closer look at the file and account setup. Your case number is: 1648506, and you can reply directly to that email with any additional details or context as they review.

Really appreciate you flagging this and your patience while we dig in — we’ll work to get this sorted. 🙏🏻