Skip to main content

How to: Edit Auditor Access to Engagements

Learn how to add and remove Armanino users to engagements within Audit Ally.

J
Written by Joanna Pritchard
Updated this week

Engagement access can be updated at any time after an engagement is created. Seniors and above have the ability to add or remove internal auditors as needed, ensuring the right team members have access to the engagement.

Updating Auditor Access

To add auditors to an existing engagement, navigate to the client’s dashboard. From there, you’ll see a list of all engagements associated with that client.

On the far right of the engagement you want to update, select the pen icon. This opens the Edit Engagement modal, where engagement details and access can be updated.

Within the Edit Engagement modal, locate the "Assigned Auditor(s)" field. Click into the text box and begin typing the name of the internal user you want to add. Select the user from the list, and their name will appear in the field.

If a user does not appear when typing their name, this means they have either not accessed Audit Ally before or do not have an active account. In this case, have them refer to the “How to: Access Audit Ally” article for next steps.

Once all relevant auditors have been added, select Save. User access is updated immediately, though no system notification is sent to the newly added users.

Removing Auditor Access

If you need to remove an internal user from an engagement, return to the Edit Engagement modal by selecting the pen icon for the engagement.

In the "Assigned Auditor(s)" field, locate the user you want to remove. Select the “X” next to their name, then click Save. This removes the user’s access to the engagement.

If a user is removed entirely from the Audit Ally platform, they will lose access to all engagements. If a user was removed in error, please contact AuditAllySupport@armanino.com for assistance.

Understanding Auditor Permissions

All assigned auditors have the same level of engagement access. However, specific actions and permissions within the engagement may vary depending on the user’s role.

Did this answer your question?