At Gumloop, we believe you should have the utmost control over what users in your organization can see and do in Gumloop. So we take a composable approach. As an admin, you can decide, for instance, whether users can build agents or only interact with them, what models they can use when interacting with or building agents, what knowledge sources are accessible to whom, and much more.

So let’s walk through setting up your organization on Gumloop. What’s important to know is that every user you add to your organization gets assigned a role. This role determines what they can do in Gumloop, and what the agents they interact with or build can do as well.

By default, they’ll be added to the Default Group role. That’s the default name of the default role here in Custom Roles. You can rename this role to whatever you want; I’ll keep it as is.

Now, the first and probably most important step: what access should you give this default role? Let’s click into the role and explore the options, with connectors first. Our default setup is to allow all connectors with their default scopes. Our recommendation is to keep this as is, meaning that if a member of your organization interacts with an agent, that agent has the same access that user has across all connectors. Note that in Gumloop, users must authenticate into every tool the agent uses on their behalf. So leaving this as is says that if that user can read and write in Asana, for instance, the agents they use can do that too.

You may want a different setup. You can restrict connectors in the Default Group by removing connectors, or by scoping down any specific connector.

Moving over to models, you can decide which models should be allowed by default. You can deselect any specific model you don’t want users in this role to have access to. And finally, set credit limits for users in this role if you so choose. If you do, they’ll be capped, with monthly resets on your billing date.

If you need more nuance beyond the default and admin roles, you can create as many roles as you’d like. You can increase credit limits, model selection or app permissions; how you define each custom role is up to you. But note that roles are additive, so adding a user to multiple groups will grant them the most permissive combination of abilities. If you’re working with an identity provider, you can sync these custom roles to the groups you already have there through our SSO setup.

Now, it’s important to differentiate custom roles from teams. Teams are where users collaborate in Gumloop: build agents together, and share skills and knowledge sources. Similarly, you’ll have a default team where everyone lands, and you can assign users to different teams. One approach is to group folks by their functional team, like sales, marketing, finance and so forth. That’s optional, and how you set this up is fully up to you.

And just like that, you’re up to speed on user-level permissions in Gumloop. It’s really that simple. You can read more below, or skip to our step-by-step guide to learn how to navigate your organization settings and make sure your org is set up for success.