In this guide, we’ll introduce the three user roles available in Receipt AI and what each role can do — from individual submission to full account administration. Use the quick links below to jump to the section you need:
You can add or edit a team member’s role on the Team page.
1. Member
The Member role is designed for employees or team members who primarily need to submit and manage their own expenses.
Best for
Regular employees or team members.
Can
- Upload receipts
- Create folders and assign receipts to folders
- View, edit, and delete their own receipts
Cannot
- Edit or delete folders
- Access accounting settings
- Access receipts from other users
Ideal for users who need to submit and manage their own expenses.
2. Accountant
The Accountant role is designed for finance teams or external accountants who need broad access to receipts and accounting structure — without account ownership.
Best for
Bookkeepers, finance staff, or external accountants.
Can
- Upload receipts
- View and manage all users’ receipts
- Manage folders
- Manage the chart of accounts
Cannot
- Add or manage team members
- Manage billing or subscription settings
- Change account ownership
Ideal for users responsible for managing financial data and organizing company expenses.
3. Owner
The Owner role is the account administrator with full control over settings, billing, and team access.
Best for
Business owners or account administrators.
Can
- Upload receipts
- View and manage all users’ receipts
- Manage folders
- Manage the chart of accounts
- Add and manage team members
- Manage billing and subscription settings
Note: Each account can have only one Owner.
Ideal for users who need full control over the account and team management.
Click the three dots on a member’s card to edit their role.
Plan Availability
Team Roles are available exclusively on Business Basic Plan and above. Pro Plan will continue to have single-user access without role management.
Tip: If you need multi-user collaboration, upgrade to Business Basic or above to unlock role-based access.