Teams and roles

A project has one owner and any number of members. A member is an email address with a role on the project: what that person may do when they open the site with Pixy on it. Nobody accepts anything, the project is simply there in their account the next time they sign in with that address.

Inviting someone

Open the project in your account and use the Members block: the address, the role, Invite. They get a mail with the project in it, and the row appears in the list straight away.

The other door is a shared link. Every address you send a link to carries a role chip beside it, guest means the link and nothing more. Change the chip to a role and that person is a member of the project; change it back to guest and the membership goes. The chips are only drawn for someone who may administer members.

Managers and the owner invite, change roles and remove. A member's own row says Leave.

What each role may do

• Viewer: opens the site with the project's edits on it, reads versions, history and comments, and writes comments to the team. Nothing on the page changes under a viewer.
• Manager: everything a viewer has, plus the work around the design: notes to the AI agent, tasks, and the project's agent keys and pairing. A manager never edits the page. Members, shared links and Live sessions are a manager's and the owner's alone, a writer and an editor design, they don't hand the project out.
• Writer: the content of the page: text, the tag an element wears, the type properties and paddings, images, and pages that don't exist yet. Notes, tasks and agent keys come with it. The drawing tools, the handles and the CSS and HTML panels stay closed.
• Editor: everything a writer has and the whole canvas with it: geometry, layout, colour, drawn elements, the CSS and HTML panels.
• Owner: everything, and the three things that are nobody else's: removing the project, transferring it, and billing.

A role can be changed at any time. If that person has the page open, it re-dresses itself where they stand; dropping someone below manager closes the workspace on them with a word about why.

Roles and plans

A role is a grant on one project. What a person may actually do is that grant or their own plan's ceiling, whichever is lower:

• Free: viewer
• Manager: manager
• Writer: writer
• Pro and Studio: editor

So a Free account invited as an editor acts as a viewer, and the row says so: viewer for now, their plan allows no more. Nothing is rewritten when a plan changes. The grant stays as it was and the ceiling moves, so an upgrade opens the role the same day and a lapsed plan closes it on the next reload.

Your own project is the exception. Every account, on any plan, is god on the project it owns, the free one every account carries. The ceiling is about other people's projects. See pricing for what each plan carries.

Asking for access

Someone signed in to Pixy who presses Connect Pixy on a project they have no standing on lands on Not your project. Ask for access. The owner and every manager get a mail with the address. Nothing is granted by asking; somebody adds them, or nobody does.

What the roles change day to day

Comments. The comment box has two audiences: a note goes to the AI agent and rides into a task, a team comment stays with the people on the project and never leaves the canvas. Viewers write team comments only. A manager can reopen a viewer's comment and send it to the agent, which promotes it to a note in place.

Undo. Undo and redo walk your own steps. They stop at a teammate's step instead of skipping over it to an older one of yours, so nothing you press can pull back somebody else's work. The owner walks anyone's.

Live and multiplayer. A member who binds to the project is in its room with everybody else, named by their email and marked with their role. Hosting a Live session is a manager's right, or the owner's.

Removing someone

Remove on their row ends it: their access to the project, their editor grants, and any page they still have open on it. Removing the project removes every membership with it.

Make owner, on the owner's rows, hands the project over. The former owner stays on the project as an editor. The receiving account's plan has to have room for one more project of its own.