| Same Team | Separate Teams | |
| Benefits |
• You can handle additional accounts, which reduces costs (especially with Enterprise plans where you get better rates and volume discounts). • It's easier to deploy company-wide manuals, share knowledge, and roll out across the entire organization. |
• User management becomes easier. • Setting the sharing scope for manuals becomes simpler. |
| Drawbacks | User management becomes complex (since various organizations use it, you need to clearly decide who has administrative privileges. Because privileges have access to all data per the spec). |
• Common manuals and knowledge cannot be shared across organizations (they remain confined to the designated organization). Not suitable for company-wide rollout. • The overall cost becomes higher than when using the same Team. |
Based on the above, if the organizations belong to the same company, use one Team. If the companies are different, it is safer to separate the Teams.