Role-based Access Control

To perform specific functionalities in creating a campaign, we are introducing defined roles for both internal and external users.

Objective

Defining permissions for specific actions.

  1. Campaign Creation

  2. Message Creation

  3. Message Approval based on Incentive type - Points, Coupon or both

  4. Audience Creation

  5. Audience List Upload 

  6. Coupon Creation

  7. Report View

This feature allows you to provide or restrict permissions for a user according to the user role.

Solution

The following table provides different actions for which user role is possible. 

Permission

Description

Campaign Creation

Permission to create a campaign

Message Creation

Permission to create a message

Approve Messages without Incentive

Permission to approve messages that don't have an attached Incentive

Approve Messages with Coupon

Permission to approve only messages with coupons as an incentive

Approve Messages with Points

Permission to approve messages only with points as an incentive

Audience Creation

Permission to create an audience list

Audience List Upload

Permission to create audience list through CSV upload

Coupon Creation

Permission to create coupons

Report View

Permission to view campaign reports


 By default, all these permissions are enabled for a user and can be revoked on request. To revoke any permission for a user(s),  raise a Jira Task ticket.

OU Support

Business need

  1. A company is often set up as different org units or brands within the parent organization - each with its own marketing strategy.

  2. A mechanism to create campaigns and target customers specific to an org unit or brand. For example, customers who purchased earlier and are more relevant.

  3. A mechanism to create campaigns to target customers across different org units or brands.

Objective

Clear boundaries between Org Units when creating a campaign so as to target a customer based on his interaction with the relevant Org Unit.

Solution

When creating a campaign, the user can specify the Org Unit for which the campaign is being created for. The offer that is attached to all messages within a campaign is only applicable in stores that belong to the Org Unit which is tagged with the campaign.

There could be three kinds of users:

  1. User with access to Parent Org and all the Org Units

  2. User with access to multiple Org Units

  3. User with access to only a single Org Unit

A User with access to Parent Org and all Org Units has the option of selecting the Org Unit for which the campaign is applicable to. If the user chooses the Parent Org itself, then campaigns can be created across OUs. For example, customers of OU1 are targeted to shop in stores of OU2 and so on. 

In the image below, the user can select between Reon Data which is the Parent Org and also the Org Units - Expressway, Franchisee, and supermarket.

A user with access to multiple Org Units needs to select one of the Org Units when creating a campaign as shown below.

A user with access to only a single Org Unit will not have to choose any Org Unit while campaign creation and all the campaigns created by the user will be tagged to the Org Unit to which he has the access to.

The campaign listing page will have the Campaign Name and the Org Unit as a label next to the name. This is visible to all users regardless of whether the user has access to the Org Unit or not.