Settings- Team Member

Permission Setting for all features

• Steps for giving permission to a user:

1. Sign in as Super Admin.
2. Go to "Settings" page.
3. Then go to "Team member".
4. Search the name of User, to whome you want to give the permissions.
5. Select the setting icon under the "Action" column.
6. Enable/Disable the Feature by selecting them in the "Features Permission" section.
7. For some features, you also have to enable some "Actions Permission".
8. Hit Save after giving the permissions.
9. THE USER HAVE TO RE-LOGIN TO SEE THE NEW PERMITTED PAGES
10. Go through the following section, to accordingly give the "Actions Permission" for the corresponding "Features Permission".

FEATURE/PAGE - ACTION MAPPING

Basically permissions to users are provided in 3 levels:

1. Feature Level
2. Action Level
3. Event Level

Now only giving features access to individuals will not guarantee its working. The feature might also require us to provide some action/ event permissions along with the feature permissions for the Feature to be completely enabled for an individual.

This document contains what action level permissions should be provided to each feature for that feature to be enabled completely for an individual.

Now actions as we can see while editing settings for an individual can be provided for create / update / delete.

Following features should have the respective action permissions provided. Actions that must be provided for every feature has been mentioned also what kind of actions (create/update/delete) should be allowed are also written.

All features along with their ACTION and EVENTS permissions are as follows: 

CHATS :
    ACTIONS :-
    1-LiveChatKpi ( create )
    2-cannedResponse ( by default given )
    EVENTS :-
    1-supervise:- to enable supervise functionalty  ( role--> superviser )
    2-takeover:- to enable takeover functionalty ( use:- once the chat is supervised )
    3-stateChange:- to enable changing of state 

CHAT HISTORY : 
    ACTIONS :-
    1-chatLogsHistory - READ is by default given
    chatLogsHistory - UPDATE ( For the feature:-     
                                blockStatus,reviewstatus,markIncorrectReview )
    EVENTS :-
    1-reviewChat:- to enable reviewing functionalty of chats 
    2-whatsappFileUpload :- to enable whatsapp file uploading functionality 


USERS (customers) : 
    No action permission needed


ANALYTICS  SECTION :
    ACTIONS :-
    1- ChatLog Analytics:  ( No action permission needed)
    2- Usage Analytics : ( No action permission needed)
    3- Event Analytics : ( No action permission needed)
    4- Query Analytics:  ( insight -> create,
                     usagesAnalytics- create [for Word Cloud]] )
    5- Agent Monitoring:  ( No action permission needed)
    6- Session Flow: ( No action permission needed)
    7- Feedback: ( No action permission needed)
    8- KPIs : ( LiveChatKpi - create)


CONSOLE:
    ACTIONS :-
    1- API Logs - ( No action permission needed)
    2- Reports -  ( No action permission needed)

BOT BUILDER :
    ACTIONS :-
    1- Workflows ( workflow- create , update, delete )
    2- Intents ( intent - create , update, delete )
            ( utterance -create , update, delete )
    3- Entities ( entity - create , update, delete )
    4- Bot Message ( botMessage- create , update, delete )
    5- Events ( event- create , update, delete )
    6- Bot Params- ( workflow- create , update, delete )
    7- Brand Function ( workflow- create , update, delete )
    8-Model Management ( intent - create , update, delete )

MEMBERS :
    ACTIONS :-
    1-Agents ( No action permission needed for viewing
    teamManagement- create- for deleting and inviting agent)
    2- Groups ( No action permission needed for viewing
                (LiveChatMgmt- create, , update, delete - for editing Groups)
    3-Canned Responses ( No action permission needed for viewing
    (cannedResponse- create, , update, delete - for editing Groups)
    4- Tags  ( No action permission needed for viewing
                (LiveChatMgmt- create, , update, delete - for editing Tags)
    5-Configuration ( No action permission needed )

SETTINGS :
    ACTIONS :-
    1- Downtime ( No action permission needed )
    2- Profile ( No action permission needed )
    3- Team Member (teamManagement -create, , update)
    4- ML Configuration ( intent - create , update, delete )

WHATSAPP TEMPLATE
    ACTIONS :-
    1-Template Master ( No action permission needed )
    2-Sender ( No action permission needed )
    3- Broadcast History ( No action permission needed )

---

The user have to Re-login to see the new permitted pages.

---

• Technical Aspects:

1. If the above functionalty is not working, then redeploy the "User Management" for that Brand and env ,and make sure that "User Management" branch is "master".
2. For "Roll-Out" of new features, add those feature into, "globalPermission" object at the path-> "user_management/src/models/Permission.model.js". After that, redeploy the User Management for every brand and env.