BuildPunch logo

Team and permissions

BuildPunch permissions decide what each person can see and do, per project and per invite: six system roles, custom roles you build from individual permissions, per-folder document access, and a guest scope for people outside your company. It is for any GC who wants the owner in the project without the owner seeing the sub's pricing. It replaces the everything-or-nothing sharing you get from a folder in cloud storage.

Roles

  • Six system roles out of the box: admin, project manager, executive, superintendent-style field access, subcontractor, viewer, and client.
  • Custom roles: copy a system role, then add or remove individual permissions — no code, no support ticket.
  • Per-folder document access, granted and revoked per person, so a contracts folder is not visible to the whole job.

Guests default to safe

When you invite someone whose email is outside your company domain, the invite defaults to a client-safe scope: they see published daily reports and only the punch items you explicitly mark shared, and drawings and documents are limited or hidden. Presets cover client, subcontractor, and full access, and you can tune photo, punch, and document visibility per invite.

Same-domain teammates get full access without you having to configure anything.

Which plans include it

Roles and guest scoping on every company plan; custom roles and folder access are for teams that need them.

More features

Start free — no credit card

More from BuildPunch