Best Practices for setting up a Team
Every design team works differently; this leads to many questions about how to best set up your team in Framer. Should you create a new Framer team for each department or product team? Where should your shared files and components live?
In this article, we highlight a few best practices for getting your team organized in Framer.
Things to consider
When setting up your team structure, it is important to remember that user permissions start at the team level. This means that team projects and private team packages are only accessible to the editors in that team, and they can not currently be shared across multiple teams (this feature is coming soon).
For example, if we wanted to install the private Framer color palette in a project, we have to make sure:
- We have editor permissions in the Framer team where our color palette package lives.
- Our project is located in the Framer team. Team packages are only accessible if the project belongs to that team, and cannot be accessed if your project is in your personal drafts.
Additionally, it’s important to consider that all editors within a team will have the ability to edit all projects within any folder in that team. In the previous project example, when we move the project into the Framer team, all editors in that team now have edit access.
So some important questions to ask when deciding on the optimal setup for your team: Who will be frequently collaborating on projects? Who will need to use the same component packages for prototyping?
If you work with external collaborators that need access to specific projects within your team, you can invite them as a Project Editor. You can do this by opening the project that the collaborator needs access to, opening the invite panel, and sending them an invite with edit access.
Inviting someone as a Project Editor allows them to collaborate on a specific project (or set of projects) without giving them full access to all the files in your team. If you would like to remove a Project Editor from your team, you can do so by changing their permissions in the Members tab of your Team Dashboard. If you would like to upgrade a Project Editor to have full Editor access to all projects in your team, remove them from your team and then re-invite them from the Team Dashboard with Edit access.
Keep it simple
In general, we recommend starting with as few teams as possible for your company. Each team created in Framer is associated with its own subscription, so fewer teams means more visibility, easier access controls, and fewer invoices.
For example, at Framer, we have one team for the company and use folders to organize our work across teams.
If your situation is more complex and you have teams that work on completely separate projects or products, setting up multiple teams may actually be a better solution for you. You can always contact us to discuss your company setup, and we can provide a tailored recommendation.
Use folders for sub teams
Folders are an easy way to organize your work. You can structure your folders based on specific teams, efforts, or functions within your company.
For example, at Framer we have a folder for all the various focus areas in the company.
The benefit of this approach is that all of our employees can access our private Framer team packages in their projects (like the color palette mentioned before), and it’s still easy to navigate and find work based on the folder names.
It’s worth noting that you also have the ability to search projects at a team and folder level, which also assists with quickly finding what you’re looking for.
Your company may have a different way of organizing work, and the benefit of folders is that they’re flexible and forgiving. It’s much easier to test different folder structures than to create multiple teams and have to move projects across teams.
Team packages access
As mentioned above, it’s important to remember that team packages are tied to a single Framer team (the ability to control package access across multiple teams is coming soon).
Packages allow you to easily share components across your team, so you can be sure your entire team is prototyping with the most up to date assets.
A package can include anything from a full design library, to shared colors, to a fully interactive set of components. The way you decide to set up your packages will vary greatly depending on your use case and current way of structuring your design system.
Currently, Packages can only be published and updated from the desktop app. Once they are published, anyone on your team can easily install them in both the web and desktop applications. When you have components you are ready to publish and share, you can specify the team you want to publish to.
Note: Only Editors that belong to the team where you publish will be able to access your packages; that’s why it’s recommended to keep all of the users who frequently share libraries and assets centralized in as few teams as possible.