We are introducing a new and an all powerful successor to the our role based access controls (RBAC) in WebEngage – its enterprise grade variant based on object based access controls (OBAC). Enterprises that use WebEngage across geographical boundaries, or have multiple lines of businesses (LOBs) or those who have their operating teams split by Brands or Functions have often asked us about separation of their customer data in a manner that each of these teams ONLY see and act on customer data that is relevant to them. Today, we oblige. Say hello to WebEngage Teams!
With Teams, you define data boundaries for your organisation. Think of Teams as a persistent filter that defines which users data a team member can see while using different sections of the WebEngage Dashboard.

For example, you could create a Team called “India Premium” that only includes users where Country is India and their Tier is Premium. Once you assign this Team to a marketer, their ENTIRE WebEngage Dashboard experience changes. They’ll only see users, segments, campaigns, analytics, that fall within that boundary definition.


















