When you're deep in the process of building new integrations or upgrading existing ones, it's easy to lose sight of the "less exciting" parts. Totally understandable. Things like user management or setting up account hierarchy aren’t flashy, but they’re foundational to long-term success. To help you stay on track, here are a few best practices for managing your integrator.io account.
Use a General Email Alias as the IO Account Owner
One of the most effective things you can do is make sure your IO account owner is set to a general email alias. Something like celigo@yourcompany.com that multiple team members can access.
This doesn't mean you can't use your personal email to log in. You can still add yourself (and others) as users and access the account with your own credentials. The IO account owner would act as the "master key," and having it set to a shared alias is a smart layer of protection.
Why This Matters
Losing access to the IO account owner is more common than you might expect, and it's never a fun situation. If the owner account is tied to a single individual and they forget to transfer ownership before moving on, it can create a major roadblock.
Here are a few common scenarios that I have seen cause this problem:
- The user leaves the company suddenly
- The user is on extended leave (e.g. medical, parental, sabbatical)
- The user is out of the office during a situation that requires IO owner permissions to solve
- They retire
In all of these cases, if ownership isn't properly transferred, your team could end up locked out of critical administrative functions. By using a shared email alias that multiple trusted team members can access, you avoid this risk entirely.
Ready to make the switch? Once your shared alias is set up, follow these steps to transfer ownership. It’s a simple change that helps future-proof your account and ensures smoother team management.
Be Intentional with User Roles and Permissions
Once your account ownership is set up properly, the next step is managing user access. Not everyone needs full control over every part of your account, and that's where permission levels come in.
Here's a quick breakdown of your options:
- Admin: Full access to manage settings, users, and integrations (everything except transferring ownership).
- Manage: Can create and update flows, troubleshoot errors, and handle integration settings—but can't modify account-wide settings or user roles.
- Monitor: Can view flows, run them, and retry errors, but can't make changes.
- Custom: A flexible option where you can mix monitor and manage permissions on specific integrations—great for contractors or team members with focused responsibilities.
Pro tip: Use MFA or SSO wherever possible, especially for admins, to add an extra layer of security.
Additional Recommendations
Make it a habit to review user access regularly (quarterly is a good starting point). Remove inactive users, validate roles, and ensure everyone has the right level of access.
Finally, keep some light documentation around your account hierarchy. Include who has access to the IO owner account, who has admin rights, and what naming conventions or access policies your team follows. It's a simple step that pays off when onboarding new team members or cleaning things up later on.
Getting these foundational pieces in place early can save you time and headaches later, especially as your integration landscape grows!