Skip to main content

I just want to reinforce what Luis posted last year, since I agree 100% with him.

 

Original thread: 

 

It would be incredibly helpful if there were a way to include a rejection reason when declining a Figma seat upgrade request.

I frequently receive upgrade notifications from across the organization, and in most cases, the requestors are unaware that there's an internal approval process they need to follow, such as submitting a request through our IT department rather than requesting directly via Figma.

Lately, this has become quite challenging to manage. When I reject these requests, I often receive frustrated follow-up emails from users who don’t understand why their upgrade was denied. Being able to provide a brief explanation at the time of rejection would save time, reduce confusion, and help streamline communication.

Thanks for considering this!

 

Be the first to reply!

Reply