Is there a way to give users in my organization different permissions and privileges?

Splash for Business is built for team management, allowing you to set up various groups separately from one another — think departments, teams, or campaigns — enabling you to create different permissions and visibilities within teams and across them.

Our most advanced clients reconstruct their company's organizational chart in Splash, setting the stage for detailed sophisticated reporting and user controls.

By understanding the basics of group management, you and your Splash Customer Success Manager will be able to collaborate on your ideal setup.


Group Types 

Splash offers two main group types — Collaborative and Managerial — and two types of users within a group — Standard User and Group Manager.

When a group is Collaborative, it means that all users within that group see each other’s events, lists, and contacts. This is by far the most popular group type because, by their nature, events require a team effort.

When a group is made Managerial, that means its members are solo collaborators, seeing and owning only their own events, contacts, and lists. However, if a group member is given the Group Manager title, he/she is able to see and access all events, lists, and contacts within the group, regardless of the owner.


Group & User Permissions

By creating groups — or better yet, multiple groups — within in your organization, you are able to build very nuanced user permission sets.

In other words, not only can assets (such as themes or email templates) be shared with groups, but your Customer Success Manager can help you target groups, sub-groups, “super” groups, managers, non-managers, etc, with special privileges or restrictions.

There's an endless number of variations of permissions an organization can use to perfectly tailor its team setting to precisely what's needed.

Below are a couple of common examples:

Example #1

You are running a global team, with regional Splash groups in the Americas, APAC, and EMEA. Within each of your regional groups are smaller groups that work within a country (e.g. The UK team sits beneath EMEA and the Mexico team sits beneath The Americas).

You have developed a beautiful event page template that you have translated into 12 different languages.

 By having your team segmented into groups and subgroups, you are able to ensure that:

  1. The right team will have access to the right template — and not all the templates.

  2. That any new member you add to the regional or country group will automatically have that template, so you do not have to remember to share the template with the individual.


Example #2

You are in charge of a large-scale user groups program that has over one-hundred user groups, each of which is tied to a city. Each city’s user group leader needs to be able to create and manage event processes autonomously, but, additionally, you also need to ensure that your user group leaders: 

  1. Are unable to see/export the email addresses of their attendees
  2. Only have access to your team’s branded email and event page templates
  3. Have very rigorous restrictions over their ability to edit event page content
  4. Only see events and contacts associated with their city group

As the director of the entire user groups program, you need visibility into every single event, contact, and list in your organization, as well as master editing rights over all pages.

How is this done? Groups!

Using Splash’s group management tool, you’re able to easily target all “sub-groups” in your program (the user groups) to have a restrictive editing/management experience, ensuring design and process consistency across an entire platform.

There are dozens upon dozen of permissions/restrictions that can be applied: everything from limiting the design experience , hiding/showing features, masking guest email addresses, and more.

 

Tiering Groups & Group Structure

Splash’s group management system is governed by a very simple concept: you see and have access to all events, contacts, and lists that exist in the groups below you (subgroups), but you do not have visibility upwards.

Using a parent-child or group-subgroup relationship, as well as the Group Manager permission within a group, you are able to create either simple or complex organizational structures, featuring precise permission sets and various levels of visibility.

Some organizations need multiple complex group structures (so, lots groups and subgroups), while for others, a single collaborative group is all that’s needed.

 Here are three very common approaches to group setup & structure:

  • Simple Team - This setup is usually comprised of a single group where each of its members have access to each other’s events, lists, and contacts. All group members have the same set of permissions, features, and event page theme library.

  • Multi-regional - This setup is characterized by the presence of an overseeing “Top Level” group, sometimes referred to as a “Super” Group or “Parent” Group, that has multiple subgroups (and sub-subgroups) that roll up to it.

    Most commonly the structure would be:

    Super Group >> Regions >> Sub-Regions >> Stores/Location

    Within each group would be managers who are able to see the events that belong to all the groups they are belong to and the groups below them.

    If you belong to, let’s say, the Atlantic Region then you would see everything in all the sub-regions (i.e. Tristate Area, Chesapeake Bay) and their stores/locations that are tiered below you — but you wouldn’t see stuff that belongs to the group above you (Super Group), nor would you see data from the Pacific Coast or Midwest groups.

  • Multiple Teams - Certain companies have several totally separate, multi-tiered departments using Splash. Others have a single department using Splash, but campaigns during the year (e.g. CES, SXSW) that exist separately from their typical event calendar and/or are executed by different personnel.

    By creating different Super Groups, you are able to have multiple, elaborately tiered group setups, all existing separately from each other, but unified in the same organization.

 

Was this article helpful?
0 out of 1 found this helpful