Skip to main content

Admin message for seat requests on Enterprise plan

  • April 28, 2026
  • 0 replies
  • 23 views

Alessandro Mastrogiacomo

In our organization we use Figma on an Enterprise plan, and we manage a large number of users coming from a broader international company structure. When users request a paid seat (Full, Dev, or Viewer with collaboration), they can currently add a note for the admin, which is helpful on their side.

What is missing for us is the reverse: a way for admins to show a short configurable message to the requester at the moment they ask for a seat. This message could:

  • Indicate who to contact (e.g. a specific Microsoft Teams channel or an email address for our design tooling team).

  • Provide a short checklist of what to verify before sending the request (correct account, correct workspace, business justification, cost center, manager approval, etc.).

  • Clarify how the approval flow works in a large enterprise context (for example, “Your request will only be processed after you or your manager contact us on Teams with X/Y info”).

Because of the size of our company, we get a high volume of seat requests that we cannot efficiently triage inside Figma alone. Many are accidental (wrong account/workspace) or incomplete (no context, no manager approval), so we often end up waiting until the requester or their manager finds the right Teams channel and contacts us manually. This creates a slow, manual, and fragmented experience both for admins and for users.

A small admin-configurable message, shown directly in the seat request UI, would let us guide people to the right process up front and reduce unnecessary or invalid requests. It would also improve transparency for requesters, since they would immediately see what is expected of them before or after they click “Request seat.”

Feature proposal:

  • Add an “Admin note to requester” field at organization or workspace level (Enterprise only, or at least org-level).

  • This note appears next to the seat request form or confirmation for users in that org/workspace.

  • Basic formatting support (line breaks, links) would be enough so we can point to internal docs or a Teams channel.

This would be a small change in the UI but would greatly improve governance and communication for large Enterprise customers managing many seat requests across multiple regions and departments.