Let's look at your current users and teams and choose the structure that is the best fit for your Enterprise plan.
Relevant for: Enterprise plan
Enterprise plan includes four main roles: Company Admins, Team Admins, Members, and Guests. Review their permissions and learn more about the difference between Company And Team Admins.
*1. Team Admins can add users to their teams only if Company Admins give them this right on a team level.
2. Teams members can add users to their teams only if Company Admins give them this right on a team level.
3. If Team Admins are allowed to add users to their teams, they can change "Team discovery settings", "Sharing settings", and "Content Security".
If Team Admins are NOT allowed to add users to their teams, they can change only the “Content Security” and "Sharing Settings".
4. Team Admins can enable or disable only the group of integrations previously enabled by Company Admins on a subscription level.
Company Admin & Team Admin
Company Admins can see and manage all teams within the subscription as well as create and edit boards. They are critical for setting up permissions, security and sharing settings, provisioning, and plan defaults. We recommend that a subscription has more than one Company Admin in case of an emergency.
Team Admins are members with extended rights to manage their team’s users, access rights settings, and other team properties. They don’t receive any special level of access to other users' content. If there are multiple teams within a subscription, each of them requires at least one Team Admin. Multiple Team Admins can be assigned per team.
Set up your team structure to ensure the security of your content and allow users to collaborate with who they need to. There are three typical team structures you can choose from.
Miro boards are created within teams. By default, your Enterprise plan will have one team. Company Admins can create multiple teams and decide which users should be a part of each team. Within teams, you can create projects that are like folders to organize your boards.
Single team structure
This structure has only one team and all users are a part of this team. Projects are used to organize boards and user groups.
- Small teams with frequent cross-functional collaboration.
- Board content that is allowed to be shared with larger user groups.
- Easier user management (only add users to 1 team).
- Simpler collaboration (no need to share across teams).
- Works well with Just-in-Time Provisioning.
- Content may be less likely to apply to the entire team and can result in ‘messy’ teams for users.
- Switching to another team structure can be difficult as it will require creating new teams and moving users and content to the new teams.
The multi-team structure consists of multiple teams, and each functional group has its own team. Users can be a member of multiple teams, but the majority of work happens within their dedicated team. Projects are used for individual work or subgroups.
- Teams that work in business divisions that operate independently. Cross-functional collaboration is infrequent or unnecessary.
- Board content that needs to be kept private to a smaller group of users.
✏️ You can add multiple Team Admins to new teams. Adding two or more Team Admins provides backup in case one is unavailable.
- Content doesn't appear in the team of irrelevant team members.
- Team Admins can take a high level of ownership when managing their teams.
- Sharing boards across teams is more difficult: members of one Enterprise team will not see boards stored in other Enterprise teams.
All + multi-team structure
This setup is a combination of Single and Multi-team structures:
- One main team with all users, the team may contain company-wide documents and guides.
- Multiple teams for different company functions.
- Larger organizations that need a way to organize teams in groups such as by department and to customize team permissions based on who needs access.
- Companies with a need for both separation of teams and cross-team collaboration.
- Combines the benefits of a private team with the ease of collaboration of a shared one.
- Can work nicely with Just-in-Time Provisioning. Set up JIT so that users could join the “All users” team right away and use it as a hub to discover other teams that they are able to join.
- Provides a space to share templates and boards applicable to everyone (all-hands meetings, etc).
✏️ For additional secuirty and organization, you may consider restricting users from creating projects and boards in the main Company team, except for Team Admins or Company Admins.
- Users may mistakenly use the main team for content storage and collaboration.
- More complex administration required on an Enterprise team level, as well as for all users across functional/departmental teams.
Next step: set up user provisioning and security