Welcome to the ElePass Support

How to Best Use Groups

Groups are the core of what makes your Clients flow so well and stay so organized. There are a lot of different ways to customize your groups – we will touch on just a few use cases to get you started. The most important thing to remember – There is no wrong way to setup your groups!

Example #1 – Simplicity

Let’s say you just created your new client and they are a small business with a small retainer. You have two people on your team that are dedicated to this client with maybe six credentials for this entire client. Let’s keep it simple!

Your first group might be named “General” and you store all of your information in this group. Your two users will have full access to this client – nothing more is needed!

This is the most common approach for groups within ElePass and this works well for the majority of use cases.

Example #2 – The Multi-Project Client

Your long term clients are your most treasured clients – they can also grow in complexity! You work with this client in different areas of their business and each of those areas have different accounts. You work with their IT team, their Marketing team and their Advertising team. You also have an ongoing project with the Marketing team and the IT team to setup a new marketing automation tool. Let’s see it in action!

First, let’s create groups based on our main areas of focus for this client. This is a common approach to ensure that only the right people have access to certain credentials. Our first groups:

  • IT Team
  • Marketing Team
  • Advertising Team

Second, let’s create a new group for our current project. This project connects to three different platforms via API, two internal systems and then a few test credentials. Our next group:

  • Pardot-Internal Integration

Why split them up? Each group has granular permissions and helps separate areas of concern as your team grows/rotates. Do you want your internal Advertisers to have access to the inner-workings of an API integration? No, you don’t!

Last Modified: October 8, 2018