-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PAF approval #3151
Comments
There are "PAF Reviewers Roles" that you configure here: https://test-apply.hypha.app/admin/settings/application_projects/projectsettings/2/ They are different from "user roles" (applicant, staff, reviewers etc.) The "Spring" projects is not in contracting from what I can see, it is still in "Waiting for approval". It will not move forward until all "PAF Reviewers Roles" have approved it, just as we decided it should work. |
A separate issue is that it might be cumbersome for staff to track what "PAF Reviewers Roles" has approved and who has not. Now they need to look in the "Activity feed" and figure it out. I imagine they will need to "nag" people from time to time? |
What roles are included on the platform and workflow?
What roles or approvals are needed during contracting?
What roles or approvals are needed during invoicing?
Related |
@fourthletter Note that the "PAF Reviewer Roles" are set up by each organisation however they want. To have none is perfectly ok. They are not mapped to user groups in any way. It is up to the users to pick the roles that is right for them when they approve PAFs. The honour system, plus that it is logged in the activity feed. |
Description
The PAF needs approvals from several user roles before it could be used to write a contract. These user roles include: Finance, and VP OR IT Director. This PAF https://test-apply.hypha.app/apply/projects/81/#activity-feed on the test site received approvals from Finance and staff + approver, but has advance to the next stage for contracting.
This PAF is still in the 'awaiting approval' phase
The text was updated successfully, but these errors were encountered: