Infrequently, our integration with Intacct may change, either to add new features or update existing ones. Sometimes this may involve a change to the permissions we require in order to access your data.

Generally we aim to require the least access we can have to your data so as to ensure as secure a connection as possible, which means that as new features are released we may not have the permissions active that we need to enable them. In cases like these, this guide will help you find and update the permissions that your Intacct instance has granted us so that you can use our system to the fullest.

Important: In order to change user permissions, you will have to be logged into Intacct with an Administrator-level account. Additionally, Intacct is currently phasing in a new user interface. The permissions screen is mostly the same, but how you access it will be slightly different based on the interface you have enabled. We have included information for both the old and new interface below:

Classic User Interface:

Click on 'Company' in the header bar (1) and then on 'Roles' in the tab window that appears (2)

Find the Role in the list that your Web Services User is using. Typically, this will be something like Beanworks API, however older integrations with us may have a different name. If you’re having trouble finding the correct Role, please contact customer support for assistance. Once you’ve found it, click the 'Edit' link beside it.

On the screen that appears, click the 'View Subscriptions' link. You may be asked if it is okay to leave the page, click 'Leave' if it does.

You will now be at the Permissions screen. 

Once you have access to the Permissions screen, you can access the permissions for each Application by clicking on the 'Permissions' link in that Application’s row. The permissions setting screen consists of rows of Permission checkboxes. The table below covers which permissions we require as well as which Application/Module they belong to.

Several of the lists are required for a base integration with us, and those are denoted by checkmarks in the Required column. These must be enabled. For those lists that are not required, they can be enabled if you use them in your current Intacct instance, or left disabled if you don’t need them. Either way, having them enabled but not using them in Beanworks will not pose a problem, so it’s typically simpler to enable everything.

Some lists are available in more than one Application. In that case, you only need to have the permission enabled in one of the Applications for the list to be usable in Beanworks. For example, the 'Customers' list is part of the Projects Application and the Accounts Receivable Application, however you only need to be subscribed to one of these Applications to use the 'Customers' list.

Required Permissions:

Beta User Interface:

The Beta User Interface is quite similar, except for the first step as the tab bar has been replaced by dropdown menus. Click first on the 'Applications' button (1), then on the 'Company' category (2), then select the 'Admin' tab (3) and finally click the 'Roles' link (4)

As in the Classic User Interface, find the Role that your Web Services User is using, which should be Beanworks API, and click the 'Edit' link beside it.

Click the 'View Subscriptions' link in the screen that appears. As in the Classic User Interface you may be asked if it is okay to leave. It is.

You will now be at the Permissions screen.

Once you have access to the Permissions screen, you can access the permissions for each Application by clicking on the 'Permissions' link in that Application’s row. The permissions setting screen consists of rows of Permission checkboxes. The table below covers which permissions we require as well as which Application/Module they belong to.

Several of the lists are required for a base integration with us, and those are denoted by checkmarks in the Required column. These must be enabled. For those lists that are not required, they can be enabled if you use them in your current Intacct instance, or left disabled if you don’t need them. Either way, having them enabled but not using them in Beanworks will not pose a problem, so it’s typically simpler to enable everything.

Some lists are available in more than one Application. In that case, you only need to have the permission enabled in one of the Applications for the list to be usable in Beanworks. For example, the 'Customers' list is part of the Projects Application and the Accounts Receivable Application, however you only need to be subscribed to one of these Applications to use the 'Customers' list.

Required Permissions:

Did this answer your question?