User Roles
Roles decide what each person in your organization can see and do, and what their agents can do.
User Roles determine what each added user can see, do, and impact within Gumloop. Upon account creation, every user in your organization will be assigned a User Role.You can create as many roles as needed to account for any nuance in permissions across users. For each role, you’ll determine what folks with that level of permissions can access, such as:
Admins have full control and can access everything from billing information, to SSO configurations, and managing user access. A pre-created Default Group role is the default for non-admin users. Keep in mind: while the role exists by default, it will still need to be configured by an admin on your team. Our recommendation is to set up the Default Group in alignment with what your employees can already do, such that their Gumloop agents can act as extensions of themselves. Allow connectors your employees already have logins and access to (think: email, calendar, common team tools), add models they can already use outside of Gumloop (think: Claude, ChatGPT, etc.), and allow access to knowledge they can already see (think: knowledge sources also available via Drive).Roles can be edited as needed, so know that your scopes can change. As folks use Gumloop more and more, you may decide to turn on additional features and generally adjust these settings at any time.
Need a role that’s somewhere in between Admins and the Default Group? You can create as many unique, custom roles as are needed for your organization. If you want support in thinking through the right setup, reach out to your Gumloop point of contact or support@gumloop.com and we can work together to get you up and running.
Keep in mind: roles are additive. If you add a user to more than one user role, they’ll receive the most permissive combination of the lot.
- What connectors they can use, assuming they the ability to login directly to those tools
- Tools within Connectors, such as what read, write, and edit tool calls they can run
- The models their agents can run on (Opus, Kimi, DeepSeek, etc.)
- Usage limits to ensure credit spend is within scope
- Their access to Gumloop features like the Brain, Gumball, Browser Use, and more.
Admins and the Default Group
Admins have full control and can access everything from billing information, to SSO configurations, and managing user access. A pre-created Default Group role is the default for non-admin users. Keep in mind: while the role exists by default, it will still need to be configured by an admin on your team. Our recommendation is to set up the Default Group in alignment with what your employees can already do, such that their Gumloop agents can act as extensions of themselves. Allow connectors your employees already have logins and access to (think: email, calendar, common team tools), add models they can already use outside of Gumloop (think: Claude, ChatGPT, etc.), and allow access to knowledge they can already see (think: knowledge sources also available via Drive).Roles can be edited as needed, so know that your scopes can change. As folks use Gumloop more and more, you may decide to turn on additional features and generally adjust these settings at any time.
Custom Roles
Need a role that’s somewhere in between Admins and the Default Group? You can create as many unique, custom roles as are needed for your organization. If you want support in thinking through the right setup, reach out to your Gumloop point of contact or support@gumloop.com and we can work together to get you up and running.Keep in mind: roles are additive. If you add a user to more than one user role, they’ll receive the most permissive combination of the lot.