Collaborating with your team

How sharing actually works

Collaboration in Pinnora today rests on three things, and all of them are live. Teammates join your organisation. Each project has a visibility setting that controls who in the org can see it. And individual members can be scoped to specific projects, so a person sees only the work they are meant to.

Together those let a team share a project cleanly. The brand kit, the library, and the generations are all visible to the people with access, and the shared credit pool means their work draws from one balance. This is asynchronous collaboration: people work on the same project, see each other's output, and build on it, just not in the same second. It works the way a shared drive does, not the way a live call does.

What is not on by default

Pinnora has code for live co-presence inside a project, the kind with moving cursors and editing locks. Here is the honest part: that layer is off by default in production. It gets switched on per deployment, so it is not something to assume is running. Unless your operator has turned it on for your environment, treat project collaboration as the asynchronous kind above.

So do not promise a teammate they will watch your cursor move in real time. Do promise that you can share a project, control who sees it, and hand work back and forth through the library.

Setting it up

Invites, roles, and per-member project scope are managed from the team settings on your org. Project visibility is set on the project itself. The team and organisation chapters cover the role permissions in detail.