Symptoms

SharePoint 2013 Super User and Super Reader system roles 

Diagnoses

Our SharePoint administrator has discovered that the Super User and Super Reader accounts have been updated to the K2 system account that was used to install the SharePoint App. He believes that this is having an impact on our SharePoint enviroment for SharePoint global distributed caching sub-system. Because it can’t utilize dedicated system accounts and instead uses k2service account.

We need to understand:
1) Was this an intentional change by the installation?
2) Is there a reason that this change would have occurred (is it needed during installation)?
3) Will there be an impact to our K2 SharePoint functionality if this account is replaced with the SharePoint service accounts that are configured for these roles? 

Resolution 

1) Was this an intentional change by the installation?

This behavior is a legacy implementation in the release of K2 for Sharepoint 2013 version 4.6.7 and 4.6.8 that had been removed from the 4.6.9 release such that a clean 4.6.9 install against a Sharepoint 2013 farm will not make this change. That being said, if this change had occurred in version 4.6.7/4.6.8 please manually update these accounts to the ones needed. Future updates/installing starting with version 4.6.9 will no longer make this change.

https://technet.microsoft.com/en-us/library/ff758656.aspx

2) Is there a reason that this change would have occurred (is it needed during installation)?

Starting with 4.6.9, we no longer make use of this implementation as such it will no longer be needed during K2 for Sharepoint apps installation.

3) Will there be an impact to our K2 SharePoint functionality if this account is replaced with the SharePoint service accounts that are configured for these roles?

There will not be any impact on the K2 for Sharepoint functionality.

The service account can also be removed from the policy enabling Full Access to farm content. This was also a change made by the legacy implementation in version 4.6.7 and 4.6.8 and is no longer necessary starting with 4.6.9.

When adding the K2 for Sharepoint 2013 apps to a site and trusting the app, the app is given Full Control on that site to perform functionalities such as Creating Subsite, Updating Subsite, Creating Groups, etc. similar to:

http://help.k2.com/kb001443