-
Notifications
You must be signed in to change notification settings - Fork 3
Permissions and Roles
Pepe Bawagan edited this page Jan 13, 2015
·
3 revisions
1. CREATE_REQUESTS
- duhh
2. VALIDATE_REQUESTS
- can be assigned as an assessing agency whose job is to check whether the reason for the request is valid
3. EDIT_REQUESTS
- completion of all information required for implementing agency to implement. more often than not, implementing agency is identical to assessing agency.
4. IMPLEMENT_REQUESTS
- can be assigned as an implementing agency
5. SIGNOFF
- the declaration that the entity performing this action considers the request in its current form suited for implementation, ready for review for the next entity.
- Request is only submitted to DBM when OCD, AGENCY, and OP have all signed off.
-
todo
an entity can retract its signoff any time before saro has been issued, and it will also retract all other signoffs done after it. The system will require a remark for the retraction, and notifies all parties whose signoffs have been automatically retracted of the reason that the retractor specified in its remark. - Think of this as “ready” for TF2.
6. ASSIGN_FUNDING
- can assign a SARO to a particular request
Permission | LGU | OCD | OP | DPWH | DBM | NGA |
---|---|---|---|---|---|---|
CREATE_REQUESTS | X | X | X | X | ||
VALIDATE_REQUESTS | X | |||||
EDIT_REQUESTS | X | X | ||||
IMPLEMENT_REQUESTS | X | X | X | |||
SIGNOFF | X | X | X | X | ||
ASSIGN_FUNDING | X |