Guide

Bring other people in

One workspace, four roles, one shared pot of credits.

Editing the same file at the same time is still being tested and is off by default. Paid plans are not open for card payment yet, so team seats are arranged by asking us.

What you need first

Decide what each person actually needs before you invite them.

  • Email addresses for the people joining.
  • What each of them needs to do — build, review, or just look.
  • Who besides you should be able to delete things.

01 · Pick the role, not the person

Give the smallest role that lets someone do their job. It is easy to raise later and awkward to lower.

  • Owner — everything, including billing and deletion
  • Admin — manages people and settings
  • Editor — creates and edits projects
  • Viewer — reads the workspace and permitted projects

02 · Invite by email

Add each person from the workspace screen with the role you chose. They get their own account rather than sharing yours, which is what makes it possible to see who changed what.

03 · Know how credits are shared

Credits belong to the workspace, not to each person. Anyone with Editor or above spends from the same pot. The Team plan is 200 credits a month at ₩66,000, and Pro is 100 at ₩34,900.

04 · Keep more than one owner

The last owner cannot be removed or demoted — otherwise a workspace could be left with nobody able to manage it. Add a second owner before anyone goes on holiday.

05 · Agree who touches what

Two people asking for changes to the same page at the same time will fight over it. Split by page or by feature. Presence shows who else is in the project right now.

You are done whenEveryone has their own account with the right role, there are two owners, and everyone knows which part is theirs.

If you get stuck

Someone used up the credits. They are shared, so this happens. Give people who only need to look the Viewer role — it cannot start a paid run.

Can two of us edit at once? Presence works, so you can see who is in the project. Simultaneous editing of the same file is still in testing and off by default.

Someone left the company. Remove them from the workspace. If they had access to project secrets, replace those keys too — removing an account does not un-know a key they have already seen.

Read next

Something here not working? Check the FAQ first — then write to us and we will answer.