Interakt lets you invite as many members as you need onboard.
In this module, we’re going to see:
• How To Add Team Members And Assign Permissions To Them?
• How To Change Permissions For Each Role In Your Team?
How To Add Team Members And Assign Permissions To Them?
• To add a team member, head to the settings dashboard and click on ‘Team Settings’. Note that you would be able to do this only if your assigned role on Interakt is that of an Owner. We will explain below how role assignment works.
• In this dashboard, you can see the details of all the existing team members on board your Interakt account along with the role assigned to each member.
You can then click on ‘+Add Member’ to add a new team member on Interakt.
• You will then get this box to fill in details of your team member. Along with the contact details, you will also need to assign a role to every member. There are 3 roles on Interakt, they are – Owner, Admin and Teammate. You can see the permissions for each of these roles in the Access Permissions page.
Once you fill in all the details and click on ‘Add Member’, your teammate will receive an email invite with the login credentials to join your account on Interakt.
• You also have the option to manage your team members – you can choose to edit their details or remove them from your Interakt account by clicking on delete.
How To Change Permissions For Each Role In Your Team?
• In the Access Permissions Page, you will see permissions assigned to every role.
Any member assigned the role of an Owner has access to all the features by default. This cannot be changed.
For the other 2 roles which are Admin and Teammate, you can use these toggles to provide or block access to a particular feature. By default, members assigned as Admin or Teammate won’t be able to access the Team Settings and Access Permissions pages.
Which means that you can change these permissions only if the role assigned to you is that of an Owner.
So, for example, if you want to restrict access to the ‘Export Users’ feature to all members whose role is Admin, you can toggle off the switch beside ‘Allow to Export Users’. Once that is done, all members in your team having the role as Admin will not be able to Export Users from the All Users page.
Similarly you can restrict access to some other features like Adding Users, Bulk Tagging Users from the All Users page, Access to Billing Section, Access to your organization’s API key and access to the WhatsApp Business Setup for your profile.
In this way, you can create a 3 level hierarchy for permissions in your organization, which can thereby help you keep your Interakt account more secure.
While, Interakt allows users to change the permissions of other users based on the role assigned to them. There is another section referred to as Global within permission settings.
The permission changes applied to this section supersede the changes that would have happened. Let us understand this from an example.
Currently under global permissions, users can enable “Hide user contact number”.
By default the customer phone number is visible for all Interakt users to see and this is Dis-abled.
When enabled, what this does is that it ensures that the customer phone number is masked for the roles mentioned as per the permissions defined.
The “superceeding effect” defined above is as follows.
1. Inbox: The customer phone number will be masked as shown below where only the country code is visible. This masking will be across User card details, chat list and the chat header.
Note: This masking does not in anyway impact the ability of an Interakt user to converse with an end customer using Inbox.
2. Notifications: The module is hidden for the users for whom the end customer contact number is masked. This is irrespective of whatever roles are assigned in the other section as per permissions settings. If the phone number masking is switched on, the notification module won’t be available for those users.
Note: It is only that the module will not be available for the specified user. The On-going or One time campaigns set already for the org will continue to happen and the org owners continue to have the ability to set up campaigns via. The module.
3. Templates: The module is hidden for the users for whom the end customer contact number is masked. This is irrespective of whatever roles are assigned in the other section as per permissions settings. If the phone number masking is switched on, the template module won’t be available for those users.
Note: It is only that the module will not be available for the specified user. The templates created already for the org will continue to be available for users to use via. inbox and the org owners continue to have the ability to create and submit templates via. the module.
4. All users: The module is hidden for the users for whom the end customer contact number is masked. This is irrespective of whatever roles are assigned in the other section as per permissions settings. If the phone number masking is switched on, the All users module won’t be available for those users.
5. Analytics: The module is hidden for the users for whom the end customer contact number is masked. This is irrespective of whatever roles are assigned in the other section as per permissions settings. If the phone number masking is switched on, the All users module won’t be available for those users.
The below screenshot of inbox depicts how post the modules are hidden it looks like for the users for whom the customer contact is masked.
The “Hide user contact number” helps orgs manage the Personally identifiable information (PII) by restricting customer contact number.
