LCS - Kuali Permissions Tips and Tricks
While building an application in Kuali Build, there were items that didn't seem obvious and/or weren't explained in the Kuali documentation.
Permissions to view documents
- To allow submitters/authenticated users to see their own documents and where they are in the process flow:
- Under Form Settings at the bottom, set up conditional permissions.
- Ensure that the submitter can only View since the submitter shouldn't be able to edit their form anywhere in the workflow (see screenshot above)
- Once the Conditional Permission is saved it looks like the screenshot below and can be edited under Form Settings
- Depending on the submitter's role (Kuali's term is policy) ensure the submitter has access to the documents via Access the document list radio button. (In this example, the submitter is going to be an authenticated user).
- Each application in Kuali comes with three policies already created; Application Administrators (aka developers), All Anonymous Users (aka public, non-NetID users) and All Authenticated Users (all NetID users). Most often you will want additional policies for people to have access to some of these permissions and/or have access to the application. Therefore, application administrators can Add New Policies, assigning them to Groups, Roles or Affiliations (from Manifest) and then assign appropriate permissions.
- Under Form Settings at the bottom, set up conditional permissions.
Kuali documention on Permissions
Kuali documentation on Conditional Permissions
Additional Kuali-related kb articles
LCS - Kuali Forms Tips and Tricks
LCS - Kuali Workflow Tips and Tricks
LCS - Kuali - How and When to Use Blueprints vs. Groups vs. Roles