|
| 1 | +--- |
| 2 | +description: Understand the functionality available in the Roo Code Cloud Team plan. |
| 3 | +keywords: |
| 4 | + - team |
| 5 | + - corporate |
| 6 | + - enterprise |
| 7 | + - shared |
| 8 | + - members |
| 9 | + - invite |
| 10 | +image: /img/social-share.jpg |
| 11 | +--- |
| 12 | + |
| 13 | +# Team Plan |
| 14 | + |
| 15 | +The team plan is designed for teams to work together using the Roo Code suite, be it the Extension, Cloud or a combination of both. |
| 16 | + |
| 17 | +It allows for: |
| 18 | +- Centralized billing |
| 19 | +- Team-wide task history and token usage analytics |
| 20 | +- Shared Cloud Agent team |
| 21 | +- Centralized integration with Github and Slack (not one per user) |
| 22 | +- Extension configuration enforcement (providers/models, MCP servers and more) |
| 23 | + |
| 24 | +--- |
| 25 | + |
| 26 | +## Access |
| 27 | + |
| 28 | +You can access Team functionality by starting a free 14-day trial. |
| 29 | + |
| 30 | +If you already have a Roo Code Cloud account, you can [upgrade here](https://app.roocode.com/checkout/team). If you don't sign up from our [pricing page](https://roocode.com/pricing). |
| 31 | + |
| 32 | + |
| 33 | +## Capabilities |
| 34 | + |
| 35 | +Most of the team functionality can be accessed from your [Organization Settings](https://app.roocode.com/) page (from your user avatar menu) |
| 36 | + |
| 37 | +<img src="/img/team-plan/org-settings-menu.png" alt="How to access your organization settings" width="280" /> |
| 38 | + |
| 39 | +From there, you'll be able to access all of the available settings: |
| 40 | + |
| 41 | +<table> |
| 42 | + <thead> |
| 43 | + <tr> |
| 44 | + <th style={{ width: "33%"}}>Setting</th> |
| 45 | + <th style={{ width: "66%"}}>Purpose</th> |
| 46 | + </tr> |
| 47 | + </thead> |
| 48 | + <tbody> |
| 49 | + <tr> |
| 50 | + <td>**Team Members**</td> |
| 51 | + <td> |
| 52 | + Invite, remove and manage permissions for team members (Admin or regular member) |
| 53 | + </td> |
| 54 | + </tr> |
| 55 | + <tr> |
| 56 | + <td>**Organization profile details**</td> |
| 57 | + <td> |
| 58 | + Logo, name, etc |
| 59 | + </td> |
| 60 | + </tr> |
| 61 | + <tr> |
| 62 | + <td>**Integrations**</td> |
| 63 | + <td> |
| 64 | + [Github](./github-integration) and [Slack](./slack-integration), for now |
| 65 | + </td> |
| 66 | + </tr> |
| 67 | + <tr> |
| 68 | + <td>**Cloud Model Providers**</td> |
| 69 | + <td> |
| 70 | + For use with [Cloud Agents](./cloud-agents) |
| 71 | + </td> |
| 72 | + </tr> |
| 73 | + <tr> |
| 74 | + <td>**Extension Task Sync**</td> |
| 75 | + <td> |
| 76 | + Whether to require task syncing, and visibility controls for who can see each others' tasks |
| 77 | + </td> |
| 78 | + </tr> |
| 79 | + <tr> |
| 80 | + <td>**Task Sharing**</td> |
| 81 | + <td> |
| 82 | + Whether per-task sharing is enabled, to whom and link expiration time |
| 83 | + </td> |
| 84 | + </tr> |
| 85 | + <tr> |
| 86 | + <td>**Environment Variables**</td> |
| 87 | + <td> |
| 88 | + Optional values to make available to Cloud Agents during runs, such as connection strings, package manager server URLs, keys, secrets, etc. |
| 89 | + Encrypted in our secure secret store. |
| 90 | + </td> |
| 91 | + </tr> |
| 92 | + <tr> |
| 93 | + <td>**Marketplace MCPs**</td> |
| 94 | + <td> |
| 95 | + Allow/deny-list MCPs from the Roo Code marketplace to make available for team members. |
| 96 | + </td> |
| 97 | + </tr> |
| 98 | + <tr> |
| 99 | + <td>**Custom MCPs**</td> |
| 100 | + <td> |
| 101 | + Custom, vetted MCP servers to make available to all team members. |
| 102 | + </td> |
| 103 | + </tr> |
| 104 | + <tr> |
| 105 | + <td>**Extension Providers**</td> |
| 106 | + <td> |
| 107 | + Allow/deny-list inference Providers to be made available to team members. |
| 108 | + |
| 109 | + Centralized API key management isn't currently supported, but let us know if you need it. |
| 110 | + </td> |
| 111 | + </tr> |
| 112 | + <tr> |
| 113 | + <td>**Organization Connection Policy**</td> |
| 114 | + <td> |
| 115 | + Mechanism to require Roo Code VS Code Extension users to be logged in, so policies can be enforced. |
| 116 | + |
| 117 | + Works via a file to be distributed via our MDM tool. |
| 118 | + </td> |
| 119 | + </tr> |
| 120 | + </tbody> |
| 121 | +</table> |
| 122 | + |
| 123 | +Additional Team plan fuctionality is available in: |
| 124 | +- [Usage Analytics](./analytics.mdx) (showing team-wide activity and per-user filters) |
| 125 | +- Task lists (in the Home and Agent pages, showing team-wide tasks) |
| 126 | + |
| 127 | + |
| 128 | +We're constantly expanding and tweaking team-oriented functionality, so if you need something else, don't hesitate to get in touch via [[email protected]](mailto:[email protected]). |
0 commit comments