Since calculated features are not executed on the fly i.e. as data is accessed, but as job, they are also not executed in the permission context of the accessing user. When calculated features are executed the Application Server executes them as that user who created or last modified the calculation algorithm i.e. the server impersonates the user who last edited the calculation algorithm when the calculated feature is executed. This has following implications:

•If the user who last edited the calculation algorithm does not have read permissions on one of the source features used in the calculation algorithm the execution of the calculated feature will not be successful.

•A user who does not have read permissions on any source feature of a calculation algorithm might still read the results of the execution of the calculated feature (if defined so by the feature privileges).