do we need this?

list They might get confused with the +payout button at the top of the dashboard

there are more statuses for expenses

not sure if we should call this admin, as they can have a custom role as well. I think we should just call out that budget owners/ petty cash users will have access to their own expenses only

should this be a watch out section. I dont think we mention this kind of a statement anywhere even though permissions apply to other sections on the product as well.

permissions

Making expenses is only via the mobile app now by scanning QR or entering UPI ID. But please check with KD if we want to add these details as its not compliant with NPCI at the moment

and you can view the expenses, verify attachments and download reports of petty expenses

expenses

*set up, modify or remove workflows

Can we add a watch out here - 1. if user being removed has reportees - call out that any approval requests raised by reportees might be blocked and reportees will be left manager-less. 2. if user being removed has pending entities to approve or is a part of workflow - that approvals of entities might get blocked.

Can we call this something else? Don't think this call out needs this level of importance

this interaction is different with T&D

access is based on permissions of their user role not the group they are a part. What are we trying to highlight here?

We can remove this. This will be possible only with custom fields. This won't be a merchant setting in V1 or the near future.

You can call out that they will be able to download team and department based reports

You should lead with this and team& department based workflows.

In V1, only admin and owner have access to add data, all other users will have access to their own data. If they are a part of workflows, they will have access to the data they need to approve/ previously approved or rejected.

this sounds a bit vague. Can we add some example if it helps? Did not understand the tracking task part of it.

instead of this level of detail here, should we just mention that once group types are created, you can add groups and assign add team members to the groups?

Think the value prop can be better here - 1. Data privacy 2. Team/ department based workflows - approvals from head of teams/ departments and reporting managers

Can we club the examples with the cases above? Case 1: The individual payout's amount in a batch. Example....... Case 2: The sum of all the payout amounts in a batch. Example.......

Remove, this is not making sense

Lets add starting and ending ranges as the same as how it comes up in workflow. 0-10,000 10,000 - 50,000 50,000 & above

Add one section for users to understand how to fill the templates

recommend .xlsx as it has validations and it would help reduce errors

can we have .xlsx templates first?

25,000 should be the limit

Add - 1. once the file is processed, you will be able see the accepted rows and invalid rows. - Accepted rows - against which payouts will be created - invalid rows - rows that were rejected (use a better word) due to some errors. You can download the batch report from the left pane where you can see the reason for invalidation.

and create the batch

Could we add a tip here that xlsx is recommended which can help then create an error free sheet easily as we have in sheet validations

Point 3 should be click on '+bulk payout' button

invite a team member

hover over the pending invite you'd want to resend, click on resend

1. Confirm the removal of the team member and they will no longer have access to your RazorpayX account.

a team member from your RazorpayX account

You can

add a link to create new role section

Change

team member

Modify team member's role

Move this to the end of Edit user role section

If the team member's role is already a part of approval workflow, make sure to add the team member's newly assigned role to the approval workflow for them to be able to continue approve or reject payouts.

pending invitation

Remove/delete

Remove

An invite will be sent to the team member via email

1. Once the role is selected, you can preview the permissions associated with the role and enter the email address of the team member.
2. Finally click on ‘send invite’.

select an existing role

Remove

team member

Add team members, create, edit roles & permissions

Remove

Once the role is successfully created, you can invite a new team member to the role or update the role of an existing team member to the newly created role.

Remove

permissions

Remove or add as a separate point with the choose from template sub-point above

This should come first as point 3 and then branch it out into two sub-points. One for using an exiting role as a template and the other for starting from scratch.

Roles provided by us/ preset templates

Remove the hyperlink