Kuali Financials leverages a document hierarchy which facilitates permission inheritance. For example:
Financial Processing Document Type is a child of Kuali Financials Transaction Document Type and Financial Processing Document Type has children documents; Internal Billing, Disbursement Voucher, Cash Receipt, Distribution of Income and Expense, and a few more.
Permissions can be set at any level of the hierarchy and are inherited by the children, permissions granted at the document level overwrite any that are assigned at the hierarchy.
Let's say that you want every one who is a KFS System User to be able to initiate all Financial Processing (FP) documents, but you only want Accounts Payable to be able to initate Disbursement Vouchers (DV).
You would assign the "Initiate FP Document" permission to the KFS System User Role which would allow users assigned to this role to initiate all documents that are children of the Financial Processing. You would assign the "Initiate DV Document" permission to the Accounts Payable Processor role. Because an initiate permission is assigned to a document, it no longer inherits the initiate permission from the Financial Processing document.
New Document Types can be created to group documents together in order to assign permissions at a higher document level.
Document hierarchy and document configuration can be viewed using the Routing and Identity Management Document Type Hierarchy in the Rice portal. This special view combines KIM data with the Kuali Financials Document Type Hierarchy. It visually displays the parent and child relationships between Kuali Financials document types and the route nodes that are associated with each.