How to activate Figma Professional — seats, teams, and the files you already have

Two things decide whether this goes smoothly. The first is which email address your Figma account actually uses. Sign in at figma.com, open the account menu at the top of the file browser, and read the address there. People sign up once with an email and a password, click “Continue with Google” months later, and end up unsure which login holds their work. Whatever that address is, that is the one the seat has to be attached to.

The second is the part most people get wrong: a Figma paid plan belongs to a team, not to a person. You do not upgrade an account. You upgrade one team, and the people inside it hold seats on that team. A file only gets the paid features once it lives in a project inside that team.

So before you message anyone, settle three things: how many people need to edit, how many only need to look and comment, and whether you already have a team or have been working alone in Drafts. ROSH™ Company Labs quotes Figma by seat and by term, so those numbers are the quote. Price on request — there is no figure printed on this page, because a printed figure would be a guess about your team.

The order only really matters at two points: the team has to exist before the plan can land on it, and the plan has to be live before you move files in.

1. Sign in at figma.com and note the exact email address on the account.
2. Decide the team. Open the one you already have, or create one from the left sidebar and give it a name you will still recognise in a year.
3. Message ROSH™ Company Labs on WhatsApp with that email, the team name, how many people need to edit, and how long you want the term. A quote comes back in dirham.
4. Pay with a local method that suits you. Activation follows once the payment is confirmed.
5. Reload figma.com and open the team. The plan now sits on it.
6. Invite your people from the team page and set each one as an editor or as a viewer. Editing seats are the ones that cost money.
7. Move your existing work in: open Drafts, right-click a file, choose “Move to project”, and pick a project inside the paid team. File by file, and only files you are happy for the team to see.
8. Open one moved file and publish your shared library from the Assets panel, if you use a library.
9. Write the end date of the term in your calendar. Nothing here renews on its own.

Check it yourself on figma.com, in a browser, signed in as you. A screenshot from a seller proves nothing — including one from us.

Open the team, then its settings. The plan or billing tab names the plan, the number of seats, and the date the term runs to. Your own name should appear in the member list with an editing seat beside it, not a view-only one.

Then test it on a file, because the settings page can be perfectly correct while your file is still in the wrong place. Open a file you moved into the team and try to publish it as a shared library from the Assets panel. Library publishing is a paid-team feature, so if the option works, the team is genuinely on a paid plan and the file is genuinely inside it. Version history on that file should also stop cutting off at the free plan’s window.

If any of those three checks fails, stop and send a message before inviting the rest of your team. Adding people on top of a half-finished setup only makes it harder to unpick.

• Everything still looks limited. You are looking at Drafts, which sit outside every team, so the plan does not reach them. Move the file into a project inside the paid team.
• The plan landed on the wrong team. If you have several teams, open each one and read its settings. Say so early — it is easier to correct before twenty files have moved.
• Someone cannot edit. They hold a view or comment seat. Change their role in team settings, knowing it adds a billed seat, so make it a decision rather than a reflex.
• The invitation never arrived. Check spam, check the address letter by letter, then resend it. A pending invitation costs nothing until it is accepted.
• Two accounts, one person. A password account and a Google sign-in can leave you in the wrong file browser. Read the address in the account menu before concluding that a file is gone.
• A private file suddenly has an audience. Moving a draft into a team hands it to everyone with access to that project. Confidential client work belongs in a restricted project, or stays in Drafts.

One case has no technical fix. A seller who asks for your Figma password, or hands you a login into a stranger’s team, is not selling you a licence — that access can be withdrawn overnight, taking your file history with it. ROSH™ Company Labs works with the address you already use.

The term stops on the date you agreed, and nothing renews automatically. There is no card on file, no subscription running quietly in the background, and no guaranteed reminder. Put the date in your calendar and message on WhatsApp a week or two before it if you want to continue. The price is quoted again at that point, because Figma’s own pricing and the exchange rate both move.

If you let it lapse, the team drops back to free-plan limits. Figma’s approach on downgrade is to restrict rather than delete: files beyond the free limits become read-only instead of disappearing. Still, read Figma’s own help pages on downgrading before the date arrives — vendors change these rules, and the version published on their site is the one that counts.

Either way, do the housekeeping before the last day. Export what a client might ask for, and move anything personal back into Drafts. A shared library cannot be published from a free team, so if colleagues depend on yours, warn them before it stops updating.

And the standing facts: ROSH™ Company Labs is independent of Figma, is not a formally registered company, issues no tax invoice, and promises no refunds. Purchases are at your own risk. If that does not work for your accountant, buy directly from Figma.