Organizations are top-level entities containing multiple teams. An organization introduces additional customization and enables more optimal workflows for multiple teams with different projects, while still being part of the same top-level organization.
How are organizations enabled?
Once you are part of an organization, you will see the organization logo for each team under the organization that you’re part of.
Why use an organization?
When you are part of an organization consisting of multiple teams working on different products, it may make more sense to have these teams split up over multiple teams under a single organization.
For instance, by having product teams split amongst different teams, they can configure their teams accordingly and obtain a more streamlined workflow within Framer.
Centralized billing and settings
Even though organizations allow for multiple nested teams, billing still happens on the organization level meaning a single payment method for all teams.
Organizations are a great solution when you’re part of a company with multiple teams or entities working on different products and there's a need to have billing, permissions, and a member overview centralized.
Project visibility and privacy
Having one organization with separate teams for each product team or department ensures that both Framer projects and team-based features such as Packages, Team Fonts, Shared Colors, Folders, and more, are relevant and shown only to the team you are part of.
This guarantees that each team can be focussed on their own products, while also ensuring that confidential projects and assets are only shared to the team that should have access to them.
Within a team, the team administrator is able to configure which features and permissions are enabled for the collaborators by using the Team Settings.
Administrators of any team within an organization also have access to the Organization Settings. These settings, as with the Team Settings, can be found by clicking the "more settings" icon
••• next to the team name.
Within the settings of your organization, all team admins can configure the organization.
Inviting members to the organization
Under the Invite section, the administrator can invite new members with any role to any of the organization’s teams. Members can be part of multiple teams. This requires multiple invites for each team.
Tip: invite users in bulk by comma-separating them:
Viewing members in an organization
To find out what role and membership someone has within any team, select the Members section. Here you can search for any organization by name or email and filter for roles.
More information about a user’s role and team membership can be found by clicking on the member. This presents a detailed overview of each team the person is a member of and which role (viewer, editor, or admin) they have in the corresponding team.
Removing a member can be done from each individual team settings. Learn more about using the team settings in this article.
Setting organization permissions
One of the main benefits of organizations are that permissions can be set on a global level, from the Permissions section within the organization settings.
Organization permissions cause 1. newly created teams within the organization to default to the organization settings, and 2. if an option has been changed on the organizational level, changes will propagate throughout all team settings.
These top-level permissions can also be locked. This means that all permissions you set for the organization will be fixed for all teams within it.
When locking permissions on an organizational level, each team’s individual permissions overview will have the settings fixed and disabled, indicating to the reader that the permissions are locked by the organization.
If you do not lock the permissions, any changes on the organizational level will still impact teams within it, but these settings may then be overridden on the team level.
If anything about organizations is still unclear, please reach out to your Account Manager and we will be happy to explain more.