Organization Units (Org Units) can be hierarchical so that they can be setup to mirror your organization's structure. All users should be assigned one or more organization unit within Unimarket so their spend can be allocated to the correct org unit. The org units are created, assigned approval chains, and assigned to users from these tabs.
Add New Organization Unit
- Go to Administration module > Administration > Organisations
- Select Add Organization Unit from the Actions menu on the right.
- If the org unit you are adding is a top tier org unit (e.g. your Community name) then leave the Parent field blank, if this is an org unit that sits below another, add the relevant parent org unit in the Parent field.
- Give the org unit a name (e.g. IT or Finance) and then select Add or if you want to add more select Add More.
Download and Import Org Units
If you prefer to export (download) your org units to edit them or add new ones, you can do that by selecting Download Org Units from the Actions menu on the right. The org unit information will be exported via a standard CSV file.
The columns in the file are as follows:
|Name||Text||Y||255||The name of the organisation unit.|
|Parent||Text||N||255||Must reference the name of another organisation unit. Leaving this blank will make this a top-level organisation unit.|
Once you have the file you can edit or add to the org units as needed. Once you are happy with the spreadsheet, select Upload Org Units from the Actions menu to load them back into Unimarket.
|Note: All existing organisation units will be deleted and replaced with the content of the new upload file.|
Assigning Users to Org Units
To assign users to the org unit, go to the org unit and navigate to the Users tab, click on Add User and begin typing the user's name, once you have found the correct user click on their name to add them to the Users to Add field, you can add multiple users in one go.
|Note: Only Org Units that have a parent can have users added to them, so top tier Org Units cannot be assigned users.|
Users may also have a self approval level which defines the spend level (i.e. $200) that they have authority to spend without the need for workflow to a delegated approver. If Self Approval is left blank then all the user's requisitions will be sent for delegated approval, see Edit User above.
Restrict Account Codes by Organization Unit
In many cases, a community will want to limit the account codes users can see when checking out a requisition. Once this feature is activated for your community, you may select specific account codes or a range of account codes that the members of each Org Unit are able to access. This allows admins to limit the visibility of account codes available to only some departments.
To configure an org unit for specific account codes, click on the relevant org unit and navigate to the Account Codes tab.
Uncheck the option for Allow All Account Codes and then click on Add Account Code Pattern. The options to modify the account codes available for members of the Org Unit will appear. You may set exact values, ranges of values or allow any (wildcard) for each part of the account code format. For ranges, letters are sorted alphabetically and numbers are sorted smallest to largest (e.g. A < B or 500 < 600).
Once satisfied with your newly created rule, click Add or Add More if you would like to add additional rules. You can then view any rules you have set up. You may set up as many as you like.
For picklist account codes (where users select from a supplied list of accounts), only the accounts the user's org unit has access to will appear. For regular expression account (where users must manually enter an account code), any account code outside of their allowed range will result in an error explaining they do not have access to the entered account code.
Organization Unit based Sharing - allows users to access orders within the same Organization Unit.