Teams, roles and clients

Who sees what, and how to bring a client in.

Projects live in a workspace: your personal one, or a team for your studio. Everyone in a team sees all of the team's projects; a project can also add single people — a client, a freelancer — who see only that project.

Roles

Owners and admins manage people and settings, including the project's agent keys. A role is changed from its own menu on the People page or the project's People tab.

The team page and each project's People tab end with a Log: who added or removed whom, changed a role, handed a project on or moved it, made or revoked an agent key, deleted a project. Owners and admins see it.

Clients

A client gets a cut-down view: only the projects they were added to, their own feedback and the review flow. They comment on their live site and confirm fixes without touching code — no developer in the middle.

On the site, a client's bar is for commenting and checking: the pages, comments, every width and device, and the keys — only the designer's inspectors are left out. They see the threads they started and the ones given to them, with every answer, and no one else's — on the site and in the cabinet alike; who a comment is for is left to the studio.

To bring a client in, add their email in the project's People tab as Client, then send them the site's link from Open site with Notemend. They sign in once on their browser and the bar is theirs. Or make an Invite link in the People tab: whoever opens it and signs in joins the project as a client; turn the link off and nobody new joins.

A client's copy of a week: the project's Report (the button on the project page) lists what was fixed and confirmed in the last 7, 14, 30 or 90 days, ready to print or save as PDF.

What a client sees

The team's threads are the team's own: a client sees the threads they wrote, the ones given to them or mentioning them, and every thread in the project's Clients space — the Space pick on a thread in the cabinet, Move to clients in a card's ⋯ on the site. The database keeps it, not just the screen. What a client writes the whole project sees, and they can reply in any thread shared with them.

A client's comment goes to a person, never straight to the agent: the project's lead — Client comments go to in the People tab, the owner until set — or whoever else of the team they pick. The team decides what goes on to the agent.

Handing over and deleting

The owner of a project hands it on from the project's Settings tab: Transfer ownership lists the people in it who have signed in, and the old owner stays as an admin. A team is handed on the same way at the foot of the team page. Delete this project, for its owner or the team's owner and admins, asks for the project's name and takes every thread, reply and screenshot with it, for everyone — there is no undo. Deleting a team, for its owner, takes all of its projects.

Guests

For a client who should not need an account at all, make a Guest link in the project's People tab. Whoever opens it gives a name and comments on the site as a client of that one project. A guest's thread does not reach the coding agent until someone from the studio gives it to Claude in the cabinet — the agent never acts on a stranger's words unread. Turning the link off lets nobody new in; guests already in keep what they wrote.