For view-only, users can view, but not edit, all main end-user modules including Investor, Scorecard, Workbook, Forms, Dashboards, To-Do and Processes and Workflows in the Guide pane. The following view-only limits apply:
Users cannot submit forms, update scorecards, create or modify objects through wizards, update workbooks, etc.
Users are subject to regular security settings, and thus may be further restricted from reading specific objects, modules, etc.
Users will always behave as if they are denied permissions for the following three workflow security modules:
1. Start Workflow Instance
- Users cannot manually start workflows using the Start Workflow dialog box.
- If users are the alert owners of alerts whose outcome is Start workflow, then the alert triggering will fail. The error message written to the log for an alert owner that actually has deny for Start Workflow will also covers this case.
- If users are defined as the Workflow System Execution Permissions users for an Embedded workflow, then it is as if there is no Workflow System Execution Permissions user and the Embedded Workflow will not be able to start.
2. Manage Workflow Instances
- The only workflow instances that these users can see in the Workflow Instances dialog box are instances for which they are defined as Manager.
3. Permit Workflow to Access all Entities & Data
- If these users are defined as the Workflow System Execution Permissions user of a workflow instance (which is either manually started by some other user or triggered by an Alert of which this user is not the owner), then they require specific permission for each entity or data that workflow system execution must access or update. They are viewed as if they have been denied blanket permission to access and update all entities & data granted by this security module.