The Rho Partner Portal offers accounting partners specialized roles and permissions, enabling seamless collaboration with clients' accounts. This guide provides a comprehensive overview of the available roles, their core actions, and their required permissions.

Roles for the Accounting Firm's Users

These roles allow accounting firm employees to interact with the Partner Portal and connect clients' accounts.

Partner Manager

Partner Managers can manage the firm's team, send invitations to connect with businesses, and handle user access for connected clients.

Core Actions:

• Manage team access
• Send client connection invitations
• Administer connected business accounts

Note: Multi-factor authentication (two-factor authentication) is required for this role.

Partner User

Partner Users can be added by Partner Managers to interact with connected client accounts but do not have access to the Partner Portal itself. 

Core Actions:

• Limited to interacting with specific client accounts based on permissions set by the Partner Manager. 

Roles for Users Added by the Accounting Firm

These users are added to the connected clients' accounts by the accounting firms

Partner Admin

Partner Admins are super-users with full admin rights. They can make payments, issue cards, configure account settings (including expense policies, approval workflows, accounting rules, and business settings), and set up accounting integrations. They can also invite other users directly or via the Partner connection.

Core Actions:

• Invite users to restricted portal roles
• Manage cards
• Update business settings (except Partner connections)
• Manage accounting integrations
• Perform money movement activities

Permissions:

To be able to support these core abilities, the following permissions have the designated states:

Partner Expense & Accounts Payable Manager

This role supports day-to-day expenses and accounts payable. They can create and pay bills, view transactions, and manage accounting integrations but cannot configure policies or change approval rules. 

Core Actions:

• Create bills
• Manage accounting integrations
• Approve and reject expenses
• No ability to manage team cards or adjust approval settings
• Money movement capabilities without control over approval rules

Permissions:

To achieve these core actions, the following permissions are enabled:

Partner Accountant

Accountants have read-only access to transaction and bill data. They can configure and sync transactions to integrations or generate bank feed tokens, but they do not have card or money movement capabilities.

Core Actions:

• View all transactions and sync them to accounting integrations
• Configure integrations
• No ability to manage cards or create transfers

Permissions:

Managing Team Access to Client Accounts

As a Partner Manager, you control which of your team members have access to each client's Rho account. When sending an invitation to a client through the Partner Portal, you need to select the user groups you want your team members connected to. Clients will see these requested groups in the invitation, and you can only add users to the groups that the client permits.

‍

Revoke Action in the Partner Portal

The Revoke action is used to remove access to a connected client account or to revoke permissions granted to a user. When this action is applied:

• Client Admins and Account Owners are able to revoke connection at any time from (Business Settings> Partner Connection). The revoke action applies to all roles and permissions tied to the client's account. Users added through the partner portal will no longer be able to view, manage, or interact with the client's data.
• Partner Admins are also able to revoke connection to a client’s business. 
• Implications: The user’s history and prior actions (e.g., created bills or approved transactions) remain, but their ability to log in and perform further tasks is disabled.

For Partners and Clients, it is important to use Revoke carefully, ensuring that any ongoing processes or responsibilities are reassigned before removal to avoid disruption. If a revoke action was done in error, a new invitation to connect will need to be sent and Partner users will need to be re-added to the client. 

‍

‍

‍