Why use custom roles?

If you’re running research or managing a team that conducts research and using Ethnio, the default roles (Admin, Team Member, Collaborator) will get you started, but they won’t reflect how your team actually works.  

Custom roles fix that. They let you shape Ethnio around your org instead of forcing your org into generic labels. All plans can create unlimited custom roles in Ethnio.

🎯 1. Match roles to how your team actually operates

Out of the box, Ethnio gives you a few standard roles. But most research teams don’t talk in those terms. You might have:

• Research Coordinators (RCs)
• UX Researchers (UXRs)
• Researchers
• Research Assistants (RAs)
• Designers
• PMs
• Vendors or agencies
• Stakeholders who just need visibility

Custom roles let you rename and define roles in language your team already understands.

Ethnio explicitly supports this. Roles are just bundles of permissions, and you can create as many as you want to match real workflows like “Research Assistant” or “Recruiter.” (https://help.ethn.io/article/1140-roles)

Why this matters:

• Reduces confusion when onboarding new team members
• Makes permissions feel intuitive, not technical
• Aligns Ethnio with how your org already thinks about responsibilities

🧠 2. Centralize permission management (and stop the chaos)

Without custom roles, you end up managing permissions from the people page by selecting collaborators, then batch editing all collaborators. That doesn't need to change, but custom roles makes it cleaner:

• You define permissions once
• Assign people to that role
• Update the role and everyone updates instantly
• You can still edit individual permissions with custom roles

This is exactly how popular tools like Figma and Github operate. Roles act as reusable permission bundles that can be updated centrally instead of repeatedly per user.

In Ethnio, this means:

• Change study creation rules once for all RCs
• Update incentive limits for an agency instantly
• Adjust Pool access without chasing individuals

No more:

“Wait, who has access to what again?”

⚙️ 3. Build guardrails without slowing people down

Custom roles let you strike the balance between:

• Empowering teams to move fast
• Preventing mistakes that cost time or money

From the create custom role flow in Ethnio, you can:

• Allow study creation but require templates (guard rails)
• Restrict access to certain participants or segments
• Control who can view vs edit sensitive data (PII)
• Set limits on incentives and spend

Practical example:

Give Designers the ability to launch studies

but require they start from approved templates

That’s scale without chaos.

🧩 4. Separate roles from seats and stay flexible

This trips people up, but it’s powerful once you get it.

• Roles are shortcuts for permissions and unlimited
• Seats are how many people you can assign and limited by your plan

You can create as many custom roles as you want, even if they all map back to the same base type.

Example:

• 10 Team Member seats
• 5 different custom roles based on Team Member:
  • RC
  • Researcher
  • Program Manager

This gives you organizational clarity without cost overhead.

🎨 5. Make roles instantly recognizable

Custom roles aren’t just functional, they’re visual:

• Icons
• Colors
• Descriptions

That might sound minor, but in a busy Re Ops environment, it matters.

It helps teams:

• Quickly scan who does what
• Understand access levels at a glance
• Reduce back and forth about permissions

🚀 6. Scale your research program

As your program grows, complexity increases:

• More stakeholders
• More requests for studies
• More studies
• More compliance requirements
• More risk

Custom roles let you design your system once and scale it cleanly. Instead of constantly rethinking permissions, you:

1. Define roles early
2. Assign people to them
3. Evolve roles as your program matures

🧪 Example: A modern Research Ops setup

Here’s what this looks like in practice:

Roles you might create:

• 🧑‍🔬 Program Manager with full study access and full incentives
• 📅 Research Coordinator focused on scheduling and participant management
• 🎯 Designer who can connect calendar, review participants, but cannot see PII or create studies
• 👀 Stakeholder Viewer with read only access and no PII
• 🌍 Vendor Recruiter with limited Pool and no incentives

Each role:

• Has clear permissions
• Uses the right seat type
• Can be updated centrally

Bottom line

Custom roles are how you:

• 🧠 Align Ethnio with your real org structure
• ⚙️ Manage permissions once instead of endlessly
• 🛡️ Add guardrails without blocking progress
• 📈 Scale Research Ops cleanly

If you’re still relying on default roles, you’re doing extra work you don’t need to do.

Set up custom roles once, and your future self and your team will thank you.