Collaborators and guests

Picrowd separates project collaborators from narrower guests, and lets a single record override the project role, so access stays intentional.

Collaborators

Collaborators work inside a project as a Viewer, Editor, or Admin; the owner can hand ownership to another admin. They use the project workspaces according to their role and any workspace-specific access settings. Invite people from Edit Project → Share Privately or from Share Access in the project menu.

Column access per member

A member can be limited to specific columns. Hidden columns disappear from their Table, Cards, Calendar, record cards, activity, AI context, and agent connections alike.

Record roles

A role given on one record overrides the project role for that record. A Viewer on the project can be an Editor of one row, and an Editor can be reduced to Viewer on a sensitive one. Columns must be allowed by both the project and the record.

Guests

Guests should only see what they need. That may mean one shared record, one public record page, a public project link, or one Whiteboard area instead of the full project.

Roles and workspace access

Project roles control broad access. Board, Whiteboard, and Picrowd AI also have their own member lists, so a person can have access to one surface without every surface being equally open. Owners and admins can lock records that must not change, and only they can change a locked record.

Good access habits

  • Use the narrowest access that lets the person do the job
  • Prefer a record role over a project-wide upgrade when only one record is involved
  • Review collaborator lists when a project changes hands
  • Remove or downgrade access when someone no longer needs it
  • Clean shared content before inviting outside people