What is Permission Role?


💡 When inviting team members to start using Reap Card or Reap Pay, you might want to assign different user permission for them considering their unique work function, location, seniority, etc. By assigning them to respective Permission Roles, your team member will be able to perform daily tasks with their own Reap team member account, without costing extra time from admin or compromising sensitive company information.

We would like to give you a brief idea of each role and their common use cases, and some common use cases for each permission role.

Admin has the highest permission and they can execute all tasks. They can add physical or virtual cards for team members, add team members to any Group and view all transactions in the company's Reap account.

Group Owner is designed for department heads or regional managers. For example, as a Marketing Director, you could invite marketing team members to the Marketing group at Reap. As the owner of the group, you can create and assign credit cards for your team member, and review transactions done by the marketing team.

Employee permission allows a team member to settle business expenses with their employee credit card. Team members with this role permission can check and review their card balance and transaction history by logging in to the Reap dashboard.

View Only is made for team members who need to review transaction records only (e.g. accounting team). This user level allows the team member to handle credit card repayment, view all team members' credit cards, and approve transactions. Team members with View Only role permission couldn't own an employee card as they normally don't have the need to make transactions on behalf of the company.

To view detailed permissions for each role, please refer to the below articles:

Team Permissions User Level Comparisons - Reap Card

Team Permissions User Level Comparisons - Reap Pay