Skip to main content
Jose Luis Pereira
New Member
Oct 28, 2026 11:34 AM UTC
Solved

Private OAuth app returns "doesn't exist" for team members without a Full seat

Our private OAuth app [redacted] is published as Private to our team OPNOVA, on a Professional plan. It is on Version 1 and has no pending changes. The redirect URL [redacted] and the scopes (file_comments:read, current_user:read) match the app settings.

 

Members with a Full seat can authorize the app: the owner, and another member who is not an admin. Members with a Dev seat or a View seat get [redacted] doesn't exist" from https://www.figma.com/oauth. This also happens in an incognito window where the Dev member is signed in only with her account.

 

The thread 53959 reports the same error for a private app published to a team: https://forum.figma.com/report-a-problem-6/oauth-app-with-valid-client-id-returns-doesn-t-exist-on-figma-com-oauth-endpoint-private-app-published-to-team-53959

 

Do private OAuth apps on a Professional team require a Full seat? If they do not, how can our Dev and View members authorize the app?

    ksn
    ksnSolution
    Community Support
    Oct 30, 2026 3:53 PM UTC

    Hey ​@Jose Luis Pereira - stepping in to help Jaycee.

    First, I wanted to note that I redacted some of the information you posted. I did this just to cover all bases, to prevent any potential bad actor -- there is an unlikely chance, but better safe than sorry.

    From my understanding, seats shouldn’t matter. Team members with a Dev/View seat should still be able to access/authenticate through the OAuth app, but the actions through the app may be limited.

    Unfortunately, I am not able to provide a confident answer. In speaking with our technical quality team, they want to be able to do more investigation on your teams. They have some questions regarding the members and access, and will need to do this securely via email.

    I’ve gone ahead and made a support ticket on your behalf (#2232246). Please take a look at your email, and reply when you have a chance.

    Thank you!

    4 replies

    Jaycee Lewis
    Figmate
    Figmate
    Oct 28, 2026 7:21 PM UTC

    Hey ​@Jose Luis Pereira 🤩 Thanks for your post. I appreciate the details and the link 🙌

    Knowing that Full-seat members can authorize the app while Dev- and View-seat members receive the same error, sounds unexpected.

    One question to help us get started — can you confirm whether the affected Dev- and View-seat members are members of the OPNOVA team where the app is published?

    Thanks! — Jaycee

     

    Jose Luis Pereira
    New Member
    Oct 30, 2026 11:20 AM UTC

    Hi Jaycee, thanks for looking into this.

     

    Yes. Both affected users are members of the OPNOVA team, as the team admin console's member list shows: one with a Dev seat and one with a View seat.

     

    One more data point: a team admin with a View seat can authorize the app. Results so far:

    Who Seat Team admin Result
    Owner Full Yes Works
    Member Full No Works
    Member View Yes Works
    Member Dev No "doesn't exist"
    Member View No "doesn't exist”

     

    ksn
    Figmate
    ksnSolution
    Community Support
    Oct 30, 2026 3:53 PM UTC

    Hey ​@Jose Luis Pereira - stepping in to help Jaycee.

    First, I wanted to note that I redacted some of the information you posted. I did this just to cover all bases, to prevent any potential bad actor -- there is an unlikely chance, but better safe than sorry.

    From my understanding, seats shouldn’t matter. Team members with a Dev/View seat should still be able to access/authenticate through the OAuth app, but the actions through the app may be limited.

    Unfortunately, I am not able to provide a confident answer. In speaking with our technical quality team, they want to be able to do more investigation on your teams. They have some questions regarding the members and access, and will need to do this securely via email.

    I’ve gone ahead and made a support ticket on your behalf (#2232246). Please take a look at your email, and reply when you have a chance.

    Thank you!