You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The regular expense flow is designed for submitters who request money from Collectives. Still, Fiscal Hosts also need to submit expenses to Collectives for vendors to get paid, among other administrative expense actions.
For them, it should be easier to submit an expense, and they do not need any hand-holding or UI aids. They should have a streamlined process to perform this core action within the context of an admin.
Solution
Implement an alternative expense submission process from the "Hosted Collectives" section and the other "Actions" to perform on a Collective.
This expense submission flow process for Fiscal Hosts is in the form of a dialog modal, and it is divided in two different steps:
Step 1: Expense type
Collective you are requesting money from (Preselected with the Collective that was being managed)
Select type of expense
Select expense recipient
Select Payment method
Step 2: Expense details
Expense title
Expense category
Expense tags
Expense currency
Expense items
Expense summary
Step 3: Expense's section
After clicking "submit" the user navigates to the expenses section, with the newly created expense opened as
Overview
The regular expense flow is designed for submitters who request money from Collectives. Still, Fiscal Hosts also need to submit expenses to Collectives for vendors to get paid, among other administrative expense actions.
For them, it should be easier to submit an expense, and they do not need any hand-holding or UI aids. They should have a streamlined process to perform this core action within the context of an admin.
Solution
This expense submission flow process for Fiscal Hosts is in the form of a dialog modal, and it is divided in two different steps:
Step 1: Expense type
Step 2: Expense details
Step 3: Expense's section
https://www.loom.com/share/9810297ee01a4722a931daee3d3179f4?sid=6abe8c42-6e97-43f7-9f28-35721b732160
The text was updated successfully, but these errors were encountered: