Setting up an API security group and an API user in Sage 100 Contractor

Security groups let you control users’ ability to open windows as well as perform specific actions within a window. The 7-2-1 Security Groups window in Sage 100 Contractor contains a grid with numbered rows on the left and eight columns:

  • Group# (User input is required to save the record.)
  • Group Name (User input is required to save the record.)
  • Save
  • Delete
  • Void
  • Chg Period
  • Print Checks
  • Notes

When you set up user groups, you type a group number and group name. Then you determine whether or not that group will have rights to Save, Delete, and Void records, as well as to change the accounting period and print checks. You can use the Notes column to add any pertinent information about each group.

You need to create an API security group that is named exactly API, add at least one user to the API security group, and set rights to save, void, and so on.

Important! If you use security groups for the tasks performed by the employee in Sage 100 Contractor, make sure the API security group has access to 3-Accounts Receivable, 3-5 Jobs (Accounts Receivable), 3-6 Receivable Clients, 4-Accounts Payable, 4-4 Vendors (Accounts Payable), 5-Payroll, and 5-2-1 Employees.

Then you have to assign a user to the API security group using 7-2-2 User List.

The 7-2-2 User List window controls major features dealing with users and program security.

Restricting employee access to Sage 100 Contractor

You can use one of the two following scenarios as an alternate way to provide the access to send information to Sage 100 Contractor from Act!.

Scenario 1: Have a system administrator enter the API user and password on a workstation

If you would like the user to be able to select a salesperson when creating clients in Sage 100 Contractor, but not give the user the ability to log into Sage Sage 100 Contractor, use this method.

A single API user/password can be entered by a system administrator on one or more workstations, allowing the user to create vendors, clients, and jobs without gaining these additional permissions when logging into Sage 100 Contractor. Essentially, this means users cannot log into Sage 100 Contractor using the API credentials, but can send information to Sage 100 Contractor.

Individual workstation users will not be able to log into Sage 100 Contractor and access employees.

Scenario 2: Restrict menu level security access to 5-2-1 Employees so employee cannot select a salesperson

If you would like to give each user their own username and password for the API, but not allow the user to select a salesperson when creating clients in Sage 100 Contractor, use this method.

You can choose to restrict menu level security access in Sage 100 Contractor to 5-2-1 Employees for an Act! user that has access to the API user login and password.

Important! Users will not be able to select a salesperson if you restrict access to 5-2-1 Employees in Sage 100 Contractor.