Best practices for permission sets
Last Update: Sep 2024 • Est. Read Time: 2 MINYour users will only have access to what they are granted access to via permission sets. For example, even if you don't want all of your team members to assist customers directly, you can still ensure that they have access to all the other areas of Kustomer they'd need to assist your customer service team.
In this article
User and Team Management
We recommend that you set both Users and Teams to Read/View access within User Management. Doing this will allow your users to:
- Assign a Conversation to another user or team.
- Have conversations routed to them if Routing is configured.
- Switch between their assigned teams to access their queues.
- View reports that are related to other users or teams.
- Build a workflow that assigns conversations to a specific user or team.
- Know which user wrote an outbound message or last updated a certain settings item, etc.
- Mention a user or team in a note.
If Teams > Read/View access is not given to a user, they will not be granted permissions that are assigned to them via Team permissions.
Important: Users and teams will also need access to the corresponding product area. For example, to build a workflow, a user will need Read/View access within User Management and Create access to Workflows.
Amazon Connect
Organizations with an Amazon Connect integration must ensure that users will have access to all incoming calls. It is recommended that all users and teams that respond to customer queries using Amazon Connect have the following access settings:
- Read/View & Create on all customers.
- Read/View & Create & Update on all conversations.
- Edit on the AssignedUsers Conversation field permission.
Shopify Actions
Organizations using the Shopify app integration may want to ensure that users can return and cancel orders directly within Kustomer. To do so, we recommend you give users the following Shopify access:
- All Access to Shopify actions
- Select the Run all actions (Return & Cancel) check box
Additional Recommendations
Below is a list of additional recommended permissions that will allow users in your organization to access product areas that will enable them to get the most from Kustomer.
Area | Recommended Access | Allows users to | |
Klass Management | Klasses | Read/View | View custom attributes and KObject data. This is also required if users need access to view reports that show custom attribute or KObject data. |
Klass Views | Read/View | View Klass Views in the timeline. | |
Content Management | Shortcuts | Read/View | Use shortcuts and shortcut categories in conversations. |
Templates | Read/View | Use email templates in conversations. | |
Snippets | Read/View | Use snippets and snippet categories in conversations. | |
Tags | Read/View | Use tags in conversations. | |
Create | Create tags while in a conversation. | ||
Searches | Read/View & Update | View and edit saved searches, as well as access reports that run searches. | |
Global Searches turned on (Optional) | Search globally within the organization. | ||
System Settings | Conversation Status | Read/View | Use custom snooze and sub-statuses in conversations. |
Queues & Routing | Read/View & Update | Have queued items routed to them and set their routing status. Note: User should also have Read/View access to Teams. | |
Workflows | Read/View (Optional) | See which workflow updated a conversation. | |
Business Rules | Read/View (Optional) | See which business rule updated a conversation. | |
SLAs | Read/View (Optional) | See the name of the SLA that is assigned to a conversation. | |
Satisfaction | Read/View (Optional) | See how a customer responded to CSAT surveys in their timeline. |