Is it possible to disable Dynamic Translation for some users?

[jonathan_living]

We are looking to deploy Dynamic Translation but some of our users shouldn't be able to use it. We have an internal recovery model for teams that need to use it. Is there a way to disable it for forms and chat per record?

[Community Alums]

Hello Jonathan,

If I break this down into three parts:

1. You would like to restrict the use of dynamic translate per user/group based on an internal recovery model
2. You would like to restrict dynamic translate for specific forms for instance dynamic translate will be available on say Pay Issue Request Form and not Request for Leave Form
3. You would like to restrict dynamic translate for specific chat sessions?

Technically speaking all the above are possible but the above user cases are very specific.

From what I understand on the Dynamic translate, one of the main selling points is the Real Time translation as it is only used if it is needed. 

On the controls as these reside on tables, we could leverage the different restriction like ACLs, User/HR Criteria as the building blocks on the platform are forms, fields, articles, alerts, flows etc. 

[jonathan_living]

Hi Joseph,

Thanks for the response. What we have to avoid is groups using the translation service without having paid for it. There's real potential that we get a huge bill from our provider and not have the funding for it. I don't want to have agents/fulfillers using the service if their group leads haven't agreed to fund it. I've responded to your points below.

1. Correct, if a group hasn't opted to use it then we haven't accounted for their use in our agreement with our translation provider.

2. Our primary use case is fulfillers to be able to translate comments from end users on Incidents and Service Requests for those groups that have opted to use it.

3. Yes, this is key for us. We are able to identify the end user and know if their group can use the translation service so it's really how to tie together the translation ability with this end user.

[Community Alums]

Hello Jonathan,

I have been thinking through this and at the moment I know there are no role-based permissions for the Dynamic translate. However, with a customization - creating a new role that will allow users the ability to use the translate feature can solve this use case. The catch here is that the translate button will appear for all users but will only be actioned if the logged in user has the new custom role.

All these are hypothetical so take it with a pinch of salt. 

@Alex Coope - SN, what do you think?

I am interested in the solution on this so if you come up with a smarter way, do share 🙂

Best regards,

Joseph

[Alex Coope - SN]

@Community Alums,

Indeed, so currently for the visual parts (e.g. the clickable links in the Activity stream / Field attribute on string fields / Clickable links in a portal) aren't designed to honour a role check, so trying to create an ACL would be an unideal design from a UX perspective. Because the best outcome from that would be a user clicks it and gets presented with an error saying that they aren't allowed to use it.

My suggestion (whilst I have a better think - I might need quite a bit of coffee 🙂) would be to raise an "Idea", 

However, as I think more about the ask I start to wonder if it's logically a good idea or not, because the reason it's not like that ootb, is to ensure a consistent experience for all end-users (this is a good UX principle and one that should not be restricted in my opinion). Ultimately, if someone doesn't understand that language, is it a good experience for them if they can't use the tools at their disposal to help and empower them with what they need?

Just my 2 cents