SUPPORT
Knowledge Baseβ€ΊSharing & Collaborationβ€ΊShare Levels Explained

Share Levels Explained

Updated 8/26/2026 Β· 112 views

Last updated: May 2026

When you share a project you make three choices: how much they can see (the share scope), what they can do (the capability), and which role they hold (which controls role-based visibility). This article explains all three.

1. Share scope β€” how much they can see

Doclio offers six scopes, chosen in the Share dialog:

ScopeAccess
Entire WorkspaceAll current and future projects in your workspace. Best for permanent internal staff.
Entire ProjectAll drawings and actions in one project.
Group OnlyLimited to one group (discipline) β€” e.g. only the Structural drawings.
By TagAll drawings carrying one or more selected tags.
Single DrawingOne specific drawing only.
Multiple DrawingsA hand-picked set of specific drawings.

2. Capability β€” what they can do

Each share carries one of four capability tiers:

CapabilityCan do
ViewRead-only access β€” open drawings, read annotations and reports.
CommentEverything View can do, plus add comments.
ContributeEverything Comment can do, plus add annotations and attachments.
EditFull editing access, including editing and deleting others' content.

3. Role β€” which annotations and reports they see

When you share, you assign the person a project role. Every project starts with five editable roles β€” Team, Client, Designer, Consultant, Contractor β€” which you can rename, add to, or delete in Project Settings β†’ People & Sharing.

Roles drive role-based visibility: you can map an annotation type (or a report) to specific roles. For example, map the "Defect" type to Contractor and Team only, and a Client with the Client role won't see defect annotations at all. See Roles and Capabilities for the full matrix.

Per-annotation visibility: Visible vs Private

Separately, every individual annotation has a visibility setting:

  • Visible β€” shown to shared users, then further filtered by their role (see above).
  • Private β€” visible only to the person who created it and the project owner.

(Older projects may show a legacy "Team" value; it now behaves the same as "Visible".)

Expiry and re-sharing

  • Expiry: a share can be set to never expire, or to lapse after 7, 30, or 90 days.
  • Can re-share: toggle whether the recipient is allowed to share their access onward.
Share Level and Permission

Entire Workspace vs a single project; View vs edit permission

Share roles

Team, Client, Designer, Consultant, and Contractor share roles

Was this article helpful?