Guide to connected projects
Who will be able to use this feature
Will require both parties to have a paid plan
Only admins will be able to set up a connected project
Admins from both parties will need to approve the connection
The following guide explains how connected projects will work when it launches in the first half of 2025.
Connected projects will let two separate teams or organizations—like an agency and a client—work together in a shared project using billable seats from their own plans.
This makes it easy to design together, share resources, and hand off files smoothly—without paying for extra seats.
How connected projects will work
A connected project gets created in one team or organization and then shared with another.
- The party which creates the project and sends a request to connect is the host.
- The party which receives the request to join the connected project is the external team.
Note: There can only be one host and one external team per project, and each party must use different business domains.
Who will manage the connected project
Admins from both parties will be able to view the connected project in their own Admin settings. Since the project originates in the host’s team or organization, the host will have more control over the settings and permissions of the project.
| Host admins | External admins | |
|---|---|---|
|
View the connected project in Admin |
✓ | ✓ |
|
View members of the connected project |
Can view all members of the project | Can only view people from their own team |
|
Manage security and privacy features for the project |
✓ | X |
|
Allow people from the external team to use the host’s libraries |
✓ | X |
|
Manage AI feature availability |
✓ | X |
|
Manage who has access to the connected project |
Can manage access for everyone | Can only manage access for people from the their own team |
| ✓ | ✓ | |
|
Manage the project after it is disconnected, including sharing a copy or transferring it |
✓ | X |
Note: The host’s plan will determine which features are available in the connected project.
If the host is on the Enterprise plan, and the external team is on the Professional plan, all features of the Enterprise plan are available to everyone in the project. This includes features like the number of variable modes, approved libraries, and security settings like requiring password protection on publicly shared files.
The reverse is also true. If the host is on the Professional plan and the external team is on the Enterprise plan, the connected project will be limited to the functionality of the Professional plan for both parties.
Note: Both parties will be able to create, move, or import files into a connected project. However, only people from the host team or organization can remove files from it.
How seats will work in connected projects
People will be able to work in a connected project based on the seat they have in their own team or organization. The host won’t be billed for users in the external team, and vice versa. Any seat upgrade requests will continue to be routed to the user’s own admins.
If a user from the external team is invited to edit files outside of the connected project in the host team or organization, they will need a seat on the host’s plan.
Note: If a user is invited to the project and doesn’t currently have an account with either the host or the external team, they will be added to the host’s plan with a View seat. If they require a paid seat, their upgrade request will be routed to a host admin.
How many connected projects will you be able to have?
Your plan determines the number of connected projects you will be able to have in your team or organization at one time.
| Plan | Number of connected projects |
|---|---|
| Professional | 3 |
| Organization | 6 |
| Enterprise | 15 |
The number of connected projects is inclusive of:
- All connected projects in your team or organization, whether you are the host or the external team.
- Any pending invites to connect where you are the host.
When you disconnect a project, it will no longer count towards your connected project count.
How libraries will be managed in connected projects
Host admins will be able to curate which of the host’s libraries are available to use in the connected project. Allowing access to a library grants members of the connected project view-only access to the library’s source file.
Connect a project to an external team
A project is connected when the external team accepts an invite from the host. Here’s how the process will work:
- A host admin creates a project, or chooses an existing project to connect. This can be any project in their team or organization.
- They create a request to connect from the project page in the file browser, or from Admin. To send the request, they’ll need the URL of the external team and a contact person’s email address.
- Admins of the external team get notified about the request to connect, and can approve or decline the connection.
- Once accepted, the contact person on the external team is added to the project. This person can invite more people from the external team to the project.
- People on the external team can start working in the connected project by switching to the host’s team or organization in the file browser sidebar.
Disconnect a connected project
When a project comes to an end, an admin from either party will be able to disconnect the project. When a project is disconnected, it remains in the ownership of the host. The external team will lose access to all the files in the project.
Host admins will be asked if they would like to share the project with the external team. They can:
- Do nothing. The external team will lose access to the project once it is disconnected.
- Share a copy of the project. The host keeps the original project and sends a copy to the external team.
Tip: You can always share a copy of the project—or transfer it completely—at a later date.