Why share a project?
When several teams handle the same assemblies, separate lists and messages can create conflicting information. A shared project gives participants a common reference for status, deliveries and progress.
Identify the participants
Project managers, workshop operators, logistics coordinators, receiving teams, galvanizers and erectors may need project access. Their needs differ: identify the data and actions relevant to each role.
Work with another company
Sharing can support collaboration with companies involved in the same flow, for example between the workshop, galvanizer and construction site. Define the partner’s scope before giving access.
Match access to responsibilities
Some participants need to consult information; others need to scan, receive or update a workflow stage. Organize access according to the roles and permissions available in your project.
Make shared information useful on site
A shared project should help a user find the correct assembly and the next relevant action. Check that operators can recognize the objects and stages involved in their work.
Keep information consistent
Shared records help teams coordinate handovers and prepare deliveries using the same project information. Their usefulness depends on participants recording the actions they actually perform.
Set up sharing
- Identify the organizations and people involved.
- Define each participant’s role.
- Assign the appropriate scope of access.
- Check what each participant can see and do.
- Review access as the project progresses.
Connect sharing to scans and workflows
A partner may need to confirm a delivery, scan an assembly or review an incoming load. Connect these actions to the relevant workflow so that the handover remains traceable.
Good practice
Share with the people who need access, keep responsibilities clear and use the project as the common source of operational information. Explain the expected action at each handover.
Common mistakes
Avoid broad access without a defined role, unnecessary information and parallel lists that contradict the shared project. Review access when a participant’s involvement changes.
Build a common working reference
Project sharing is useful when each participant can consult or record the information needed for their part of the job. Keep the arrangement aligned with the real movement of assemblies.
Frequently asked questions
Who may need access to a shared project?
Workshop, logistics, site and external partner teams may need access, according to their involvement in the job.
Can sharing involve another company?
Yes, sharing can support project partners according to the access rights and organization defined for the project.
Is sharing only for viewing information?
It can also support operational actions such as scans or receiving, depending on the participant’s role and permissions.
Related guides
See Fabbim in your workflow
Discuss IFC/Tekla import, part identification, and tracking fabrication, galvanizing and deliveries with our team.