For the complete documentation index, see llms.txt. This page is also available as Markdown.

Permissions - Lead Access Levels

In SprintHub, we offer three access levels to ensure that customer service management is secure and efficient:

1 - Account access

To access conversations on WhatsApp, Instagram, and Facebook, the user needs to have specific permissions on the account. If the user does not have these permissions, they will not be able to view the conversations.

It is possible to define who has account access through the department. Click Edit Department, where you will have the option to choose accounts:

In Accounts, you can define which accounts that specific department has access to.

You can use it to separate the marketing department that works with Facebook and Instagram from support that works with WhatsApp, for example.

2 - Department access

Users who belong to the same department have the ability to see each other's tickets.

So, for example, anyone in the support department will be able to see all the other tickets from people in support; the same applies to sales, finance, etc.

However, they can choose to filter the tickets to view only those that belong to them, providing a more organized and focused work environment.

There is a practice used in some instances, which is not recommended; see below:

3 - Lead access

It is possible to change the employee responsible for a lead, restricting access to this ticket exclusively to the new responsible person. This change can be made in two ways:

  • Manual: Allows an administrator or a user with the appropriate permissions to make the change directly.

  • Automation: Uses predefined rules to automatically change the lead owner, ensuring that tickets are distributed efficiently and according to the team's needs.

If you want to see an example of an automation that changes access permissions, click the link below:

Conclusion

These access levels were developed to offer flexibility and security, meeting the diverse needs of support teams and ensuring an efficient workflow in SprintHub. If you still have questions, watch the video below to understand better:

Last updated

Was this helpful?