Hiding OOTB Technical User Contacts from Users

What is the recommend, safe approach to hiding technical user contacts from regular users? Users such as Creatio ALM Integration, Creatio Maintenance, Email Supervisor, Supervisor etc will appear as regular Contacts to users for selection and even editing, but this ranges from frustrating/confusing to users up to being potentially dangerous to the platform stability.

 

I've considered record permissions as potentially the best solution, as that will hide them from the Contacts list, selection in lookups etc, but the risk is that this might cause issues for the platform - can anyone confirm whether they do or not? Another downside would be that data modified by these users would appear weirdly to users, since the lookup references a non-readable Contact in ModifiedOn, though this isn't so major. And another would be that these permissions would be manually maintained, so any new technical user contacts created (e.g. a new integration, or when the platform gets upgraded and new ones are introduced OOTB) would have to be remembered to have their permissions changed.

 

Another option would be to just hide those users from the Contacts list by filtering the list. This has the drawback of hiding those users from system admins, as well as not hiding them for selection from lookups on other Objects (which would require putting that filter into Business Rules on every Object in use - not very practical or maintainable).

 

Does anyone else have any suggestions? Would be good to get some clarity on this from Creatio as well.

Like 5

Like

5 comments

Hello Harvey,

Great question, +1 

Since there are quite a few technical users in the latest versions of OOTB Creatio I would also appreciate a official recommendation on this! :) 

Kind regards,
David

Hello!

Thank you for your request. That’s a good point, and we’ve already created a corresponding ticket for the development team to review and consider implementing feature in our system.

At the moment, it seems to me that the simplest solution would be to add filtering on the page. For example, a filter like “Show technical users,” which would be set to false by default. When enabled, it would display all contacts that have a technical user. Additionally, using business rules, this filter could be hidden from non-admin users.

Regards, 
Orkhan

Orkhan,

Thanks Orkhan. I feel like this is another case which would be aided by having a substantial logical layer between Objects and Page logic in Creatio - having what might essentially be a DB view over the Object (in this case Contact) which can have its own set of filters and calculated fields etc while still being based over Contact so that you could still use lookups to Contact and other Contact-based logic for it.

Orkhan,

 

Orkhan writes:

Hello!

Thank you for your request. That’s a good point, and we’ve already created a corresponding ticket for the development team to review and consider implementing feature in our system.

At the moment, it seems to me that the simplest solution would be to add filtering on the page. For example, a filter like “Show technical users,” which would be set to false by default. When enabled, it would display all contacts that have a technical user. Additionally, using business rules, this filter could be hidden from non-admin users.

Regards, 
Orkhan

MoreLess

Hello Orkhan, 

thank you for your reply! 

In that case, that would mean that those Contacts are still visible through lookups, unless a seperate filter is configured manually for every "Contact" Dropdown field, correct? 

Could you please elaborate regarding the approach of removing the record permissions these Contacts for normal business users? Does this come with any drawbacks? It seems like the most elegant and persistent solution to me if performed during initial system setup, but I might be missing something?

Kind regards,
David

+1 here 

Show all comments