People on a project
Who belongs on a Bucky project — team, partners, stakeholders, and viewers — and when they join across the development.
A project can name many people. Only some of them get a Bucky login. Mixing those types is the usual source of “who do we add?” confusion.
Use this page to choose the right type. For the first-week sequence, see First week with your team.
The four types
| Type | What they are | Login? | When to use |
|---|---|---|---|
| Team | Collaborators on this project | Yes | They will work in Bucky — run analysis, edit, or administer the project. |
| Partners | Companies aligned to the project | No | An architect, builder, or other firm you may hire. Linking them does not grant access. |
| Stakeholders | People or organizations you are tracking | No | A planner, lender, neighbour, or other contact you need on the record. |
| Share / viewer | Someone who should see the workspace | Viewer login, or a share link | A client or principal who needs the live project, not a seat to run it. |
Organization members are a fifth concept, and they are not a project type. A company-account seat does not by itself put someone on a project.
Marketplace services are how you later find people to build. That is not “adding a party” on day one.
Team (login access)
Team members appear on the project Team tab. Roles:
| Role in Bucky | What it means |
|---|---|
| Owner | Full control of the project, including who else is on it. |
| Admin | Can manage the project and its people. |
Service Provider (contributor) | Can work on the project — analysis, notes, files — but is not an owner. |
| Viewer | Can see the project workspace. Cannot edit. |
Add a colleague to the team only if they will work in Bucky. If they only need to read the site, invite them as a viewer or send a share link.
Partners (companies, no login)
Partner companies are external firms on the project. Linking a company does not grant login access. Use this when you want the relationship on the project — an architect or builder you may hire — without giving them a workspace yet.
Give that firm a seat later only if they need to work in the project.
Stakeholders (tracked contacts, no login)
Stakeholders are people or organizations you track for due diligence. They do not get a login. Parcel owners can appear here when Bucky already knows them.
Use stakeholders for a planner, lender, neighbour, or anyone you need on the record without inviting them into Bucky.
Share links and viewer invites
Two ways to let someone see the work without making them an operator:
- Viewer invite — they sign in and open the project as a viewer.
- Share link — they open a view of the project from a link.
Inviting a viewer or creating a share link is included with Professional. You can still create and analyze the first project on a Personal plan; add sharing when a client or colleague needs to see the live workspace.
Organization members vs project members
| Organization member | Project member | |
|---|---|---|
| Scope | The company account | One project |
| Grants | A seat in the firm | Access to that project |
| Typical use | Admins and staff of your company | The people on a specific site |
Adding someone to the company does not put them on every project. Adding someone to a project does not make them an organization admin.
What not to do on day one
- Do not invite the whole office.
- Do not give a login to every name on the deal.
- Do not treat marketplace discovery as a required first step.
Start with one champion and one project. Then decide who needs a seat. The first-week guide walks that path.
Across the development
Parties are not a day-one roster. They attach to the same project as the work moves:
| Stage | What you do in Bucky | Who you add |
|---|---|---|
| Screen | Scout addresses, compare options, kill weak sites. | Champion only. |
| Go / no-go | Save the project. Read zoning and feasibility with citations. | Viewer or share link for a client or principal who needs the live read. |
| Definition | Scenarios, envelope, program, assumptions. | Team members who will work in Bucky. Owner as a stakeholder. |
| Entitlement | Approval path, cited memos, open questions for the next hearing. | Planner, neighbours, council contacts as stakeholders. Do not give the city a login. |
| Team formation | Link firms you may hire. Find services when you are ready to build. | Partner companies (no login). A workspace only if they will work in the file. |
| Toward shovel-ready | The project stays the record of facts, assumptions, and decisions. | No new roster. Construction execution is not Bucky. |
Bucky is the pre-development record. It does not replace a construction PM system once you are on site.
Last updated on