Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

Accounts, Files, Teams and Plans in Figma

Create a Figma account and understand files, projects, drafts, teams, seats and sharing permissions, with a runnable stand-in that models who can do what in a file.

Before you draw anything you need somewhere to put it. Figma organizes work in a small hierarchy of files, projects and teams inside a workspace, and it controls who can see or change each one with permissions. Understanding this structure early saves you from lost files and from accidentally giving the whole internet access to a private design.

Creating an account

Open figma.com in your browser and choose to sign up. You can register with an email and a password you create, or with a Google account. Confirm your email address if asked, pick the role that best describes you (the answer only personalizes suggestions), and you land on the Home screen, also called the file browser.

You can use Figma in a browser tab or install the desktop app from the download page. The desktop app is the same editor in its own window, with proper tabs, and it is slightly nicer for installed fonts and keyboard shortcuts. Both open the same cloud files.

Never share your password with anyone and use a strong, unique one. Figma never needs your password to give a colleague access: you invite people by email or link instead.

The hierarchy of work

Think of Figma as folders inside folders:

How work is organized

Workspace Your organization
Team A group with shared files
Project A folder of related files
File One design document

Files live inside projects

1 / 2
  • A file is a single design document. It has one or more pages.
  • A project is a folder of files, for example "Mobile app" or "Marketing site".
  • A team is a group of people who share projects. Everyone on the team can find the team's files.
  • Drafts are your personal files. Only you see them until you move them into a team project or share them.

Creating and opening a file

On Home, use the New design file button (the wording may change, but it always creates a blank Figma Design file). The file opens in the editor with an empty canvas. Click the file name at the top to rename it right away. Give it something meaningful like "Recipe app v1": future you will thank present you.

To move a draft into a team, drag it onto a project in the sidebar, or use the file's context menu. To find old work, use the search box on Home or the Recents list.

Autosave is always on. Figma saves every change to the cloud as you work, and keeps version history so you can restore an older state. You never press Save.

Plans, seats and what they mean

Figma sells access by plan and by seat type. Exact prices and limits change, so check the pricing page, but the structure is stable:

  • A free Starter plan lets you design and learn with limits on the number of files and pages in a team.
  • Paid plans (such as Professional, Organization and Enterprise) remove limits and add things like shared libraries, advanced permissions and admin controls.
  • A Full seat (sometimes called a Design seat) can edit design files. A Dev seat or view-only access is meant for developers and stakeholders who inspect and comment.

For this course a free account is enough for most chapters. When a lesson uses a feature that normally needs a paid plan (such as publishing a team library), the lesson says so and shows how to practice within one file instead.

Sharing and permissions

Click Share in the top right of the editor to invite people or create a link. Each person or link has a permission level:

Level Can view Can comment Can edit
Can view yes sometimes no
Can edit yes yes yes
Owner yes yes yes, plus manage sharing

You can restrict a link to people in your organization or make it open to anyone who has it. A good habit: share with specific people while a design is private, and use a view-only link for stakeholders.

A stand-in for the permission model

The program below models the table above. It is not Figma's code or API, only a small stand-in that shows how a permission check works.

Python Stand-in: who can do what in a file

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Each action needs a minimum level, and higher levels include everything below. Real Figma has more nuance (link settings, team roles, library rules), but the idea of "at least this level" is the same.

Estimating a team's seats

Teams often budget by counting seats. Here is a tiny calculator that separates people who edit designs from people who only look.

Python Stand-in: counting seat types

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers here are pure illustration, not prices. The point is that most teams have a few designers and many people who only need to view and inspect.

Good file hygiene from day one

  • Name files after the product and the stage: "Checkout redesign - exploration".
  • Keep related files in one project so search and permissions are easy.
  • Use Duplicate (not Save As) to branch an idea.
  • Before sharing widely, check who has access in the Share dialog.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a Figma draft?

    Drafts are personal files; moving them into a team project makes them visible to the team.
  2. 2. Which is the correct nesting from largest to smallest?

    A team has projects, a project has files, and a file has pages.
  3. 3. Do you have to press Save in Figma?

    Figma autosaves to the cloud continuously.
  4. 4. Who is best given view-only access?

    Use the minimum access that still lets a person do their job.

Summary

  • Sign up with email or Google, then use the browser or the desktop app.
  • Work is organized as workspace, team, project, file and page; drafts are private.
  • Plans and seat types decide who can edit; free accounts are enough to learn.
  • Share with the lowest permission that works, and rely on autosave and version history.

Next: Design Basics: Pixels, Units and Grids