Collaboration
How to Share Electrical Drawings with Customers and Teams Without Losing Control
Customers, designers and project administrators need different forms of access. Controlled sharing lets each person do what their role requires without turning every participant into a project owner.
Sharing is not a single permission. A customer following progress, an engineer assigned to make changes and an administrator responsible for a project folder should not receive the same controls merely because they need access to the same drawing.
01 · Access follows responsibility
Begin by deciding what the recipient needs to accomplish.
The safest access model starts with purpose rather than convenience. If a customer only needs visibility, edit controls create unnecessary risk. If a team member must complete design work, a static PDF may prevent useful collaboration. If someone must organize and delegate work, edit permission alone may be too limited.
Inspect drawings, move between pages, zoom and pan without changing project content.
Work on assigned drawing content while sharing and destructive controls remain restricted.
Administer the permitted folder or drawing, including its structure and access where allowed.
Retain primary responsibility for the project content and the people who may administer it.
02 · Meaningful view-only access
Customers should be able to inspect progress without editing it.
View-only access should not mean a frozen screenshot. A useful reviewer can open the current drawing, move across its pages, zoom and pan, and return to the project dashboard. What remains unavailable is the ability to change symbols, wires, page structure, project information or shared access.
This approach is useful for progress visibility and informal review, but it does not replace controlled issue or approval procedures. The project team should still identify the revision, purpose and status of any drawing submitted for formal acceptance.
Opening a shared drawing does not confirm its technical correctness or transfer engineering responsibility to the viewer.
03 · Assigned design work
Team members need access that matches the work they own.
An organization member with edit access can work on the assigned folder or drawing without automatically receiving authority over the whole organization. Someone who created a permitted folder or drawing may need broader control over that content because they are responsible for its structure and ongoing use.
Suitable for a designer who must work on the drawing but should not administer access.
Suitable for a trusted lead who must organize, rename, share or maintain the permitted content.
View-only recipients should not be able to reshare what they received. Otherwise the original owner loses control over where project access spreads and who remains accountable for revoking it.
04 · Scope and ownership
Management rights should remain limited to the shared boundary.
Granting management access to one folder should not silently make the recipient an administrator for unrelated projects. The system needs to preserve the scope of the grant and distinguish organization roles from item-level permissions.
- Keep project and organization ownership explicit.
- Apply folder access to its contained drawings without exposing unrelated work.
- Allow authorized creators to manage the content they created.
- Prevent view-only recipients from renaming, deleting or resharing.
- Display the access level and who shared the item so recipients understand its origin.
Permissions should be enforced by the backend as well as reflected in the interface. Hiding a menu item is helpful for clarity, but it is not a security boundary by itself.
05 · External invitations
External sharing needs a complete invitation lifecycle.
A recipient outside the organization may not yet have an account. The invitation flow should preserve the intended destination through account creation or sign-in, then apply access only to the verified email address for which the invitation was created.
- Copy: let the sender copy the same pending invitation link when another channel is more appropriate.
- Resend: deliver the existing invitation again without creating confusing duplicate grants.
- Revoke: make a pending or accepted grant unusable when access is no longer required.
- Audit: retain enough context to identify the sender, recipient, scope and access level.
External participants should normally receive view-only access. Edit and management privileges are better reserved for authenticated organization members whose roles and responsibilities can be administered together.
06 · The ElecDraw model
How ElecDraw separates customer visibility from team control.
ElecDraw allows folders and drawings to be shared with organization members using view, edit or manage access. Ownership, organization role and item-level permissions determine whether a person may change project content, create drawings, rename or delete items, or manage access.
Email invitations provide view-only access outside the organization. Recipients can create an account or sign in with the invited email, while senders can copy, resend or revoke a pending invitation. View-only mode preserves page navigation, zooming and inspection while disabling edits and resharing.
These controls support day-to-day collaboration, but each organization should define who may share customer information, what constitutes formal approval, and how access is reviewed and removed when a project ends.
