> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Organization and Teams
Organizations and Teams are available only on the **Pro plan** and above.
## At a Glance
**Think of Gumloop like Google Workspace:**
Your company's account that manages billing, users, and security
Your private space for building and running agents and flows. Only you can access it.
A shared space where multiple people can view, edit, and run flows & agents together
Everyone in your organization shares the same credit pool. Start with your personal space for most work, and create teams when you need true collaboration.
***
## Personal vs Team
Most flows & agents should live in your personal space. Create teams only when collaboration is essential.
| | **Personal** (Recommended) | **Team** |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| **Who can see agents & flows?** | Only you by default. You can [share with specific users](/core-concepts/share_permissions) as Editors, Viewers, or Use Only. | All team members by default, with options to share more broadly |
| **Who can edit agents & flows?** | Only you by default. You can share with others as Editors. | All team members (as Editors by default) |
| **Who can run agents & flows?** | You directly; others you've shared with (based on their role) or via shared interfaces | All team members; others via sharing or interfaces |
| **Best for** | Most agents and flows, development, testing, production | True collaboration where multiple people maintain the same agents and flows |
| **Available on** | All plans (Free and above) | Pro plan and above |
Every user gets a personal space automatically when they sign up. **This is where most of your work should happen.**
* **Fast and flexible**: Build without worrying about breaking others' work
* **Secure by default**: Your agents, flows, and data stay private
* **Production-ready**: Run production agents and flows that you maintain
* **Safe experimentation**: Test ideas without affecting your team
Your personal space is private by default, but you can share any agent or flow with specific users by email. Choose their role: **Editor** (full access), **Viewer** (read-only), or for agents, **Use Only** (chat only). You can also set General Access to share with your entire organization. Learn more about [share permissions](/core-concepts/share_permissions).
Teams let multiple members work on the same agents and flows together. **Use these when true collaboration is essential.**
* **Multiple editors**: Several people actively maintain the same agent or flow
* **Shared ownership**: Team members get Editor access by default
* **Team apps**: Everyone uses the same connected integrations
* **Department resources**: Agents and flows used across an entire team
All team members get Editor access to team agents and flows by default. You can further share with users outside the team using the Share dialog, or broaden access via General Access settings. Use teams intentionally, not by default.
***
## Understanding Organizations
An **Organization** is your company's top-level account. It's the umbrella that holds everything together.
All users share one credit pool. When anyone runs an agent or flow, whether in their personal space or a team, it deducts from the organization's credits.
There's no separate billing per team or per user. One unified account.
* Anyone with your company email domain automatically joins your organization (if [domain whitelisting](https://docs.gumloop.com/core-concepts/organization_user_roles) is enabled)
* **Invite users by email** — invited users appear with a "Pending" status until they accept
* Organization admins can **resend** or **revoke** pending invitations
* Add, remove, and manage user permissions across all teams
* Set which team new members join by default
Gumloop's roles are **additive**, so a user can hold multiple roles at once (for example, `{Member, Analytics, Templates}`). Use the **Manage Roles** sheet on the members page to add or remove individual roles instead of promoting or demoting users.
[Learn more about user roles and permissions →](/core-concepts/organization_user_roles)
* Control security settings across all teams
* Manage data retention policies
* Set organization-wide defaults
* Monitor usage across all teams
[View Organization Settings →](https://www.gumloop.com/settings/organization/general)
***
## Creating a Team
There are two ways to create a team.
### Option 1: From the Sidebar
On the [Home page](https://www.gumloop.com/hub), find the **Teams** section in the sidebar and click the **+** icon.
Give your team a name, choose a logo, and pick a brand color. Then click **Create**.
### Option 2: From Organization Settings
Go to [Settings → Teams](https://www.gumloop.com/settings/organization/teams) and click the **Create** button.
***
## Adding Team Members
Once you've created a team, there are three ways to add members.
### Option 1: Invite to Team from the Sidebar (Quickest)
On the [Home page](https://www.gumloop.com/hub), **right-click** on your team in the sidebar and select **Invite to Team**. This opens the invite dialog directly, letting you add members without navigating to settings.
Enter the email address of the person you want to invite. They'll receive an invite and will be added automatically once they accept.
### Option 2: From Team Settings
On the [Home page](https://www.gumloop.com/hub), **right-click** on your team in the sidebar and select **Settings**.
Click the **Add Member** button and enter their email address. They'll receive an invite and will be added automatically once they accept.
### Option 3: From Organization Settings
1. Go to [Settings → Teams](https://www.gumloop.com/settings/organization/teams)
2. Click on the team you want to manage
3. Click **Add Member** in the Team Members section
***
## Connecting Team Apps
Team apps are shared integrations and API keys that all team members can use when running agents and flows. There are two ways to connect apps for a team.
### Option 1: Right-Click from the Sidebar
On the [Home page](https://www.gumloop.com/hub), **right-click** on your team in the sidebar and select **Settings**.
Then navigate to the **Apps** tab.
Click **Connect New App** to add a new integration.
### Option 2: From Organization Settings
1. Go to [Settings → Teams](https://www.gumloop.com/settings/organization/teams)
2. Click on the team, then select **Connectors** in the sidebar
3. Click **Connect New App**
Team apps are available to all team members. For personal integrations that only you use, connect them from your personal [Connectors page](https://www.gumloop.com/personal/connectors) instead.
***
## Moving Agents & Flows Between Teams
You can move agents and flows between your personal space and teams:
1. Go to the [Home page](https://www.gumloop.com/hub)
2. Click the three dots (⋮) next to the agent or flow
3. Select **Move to Team**
4. Choose the destination team
You can always move them back if needed. Once in a team, all members can edit them until you move them elsewhere.
***
## Setting a Default Team
Organization admins can choose which team new members automatically join from the [Teams settings page](https://www.gumloop.com/settings/organization/teams).
When someone with your company email signs up:
1. They automatically join your organization
2. They get their personal space
3. They get access to the default team
4. They can request access to other teams
***
## Common Questions
What others can do depends on their **access level**, which you control through the Share dialog:
* **No access / not shared**: They can see a preview but cannot interact. They can request access from the owner.
* **Use Only** (agents only): They can chat with the agent but cannot view its configuration.
* **Viewer**: They can view the agent or flow but cannot edit it. They can make a copy to their own space.
* **Editor**: They can view and edit the agent or flow.
You can also set **General Access** to give your entire team, organization, or anyone with the link a specific role. For public links (Anyone), unauthenticated users are capped at Viewer access.
Want someone to just use your automation without seeing how it works? Share the agent with **Use Only** access or share it as an interface.
**Always start in your personal space.** Move to a team only if multiple people need to actively edit the same agent or flow.
**Keep in personal space if:**
* You're the primary maintainer
* It's still in development or testing
* Others just need to run it (share via interface)
**Move to a team if:**
* Multiple people actively edit the same agent or flow
* The team collectively maintains it
* You need shared team apps
* Team members need to cover for each other
**Your organization pays for everything.** Whether an agent or flow runs from your personal space or a team, it uses your organization's credit pool. Teams only affect who can access and edit agents and flows, not billing.
***
## Related Documentation
Set up personal and team apps
How credits work across teams
Organization and team permissions