What we’ll cover:
- Understanding Chartstring defaults
- How to apply Chartstring limits
- Chartstring Security examples
- Redundant Permissions overview
Applicable Roles:
- FM Global Admin
Before getting started, please note:
- As an FM Global Admin with Chartstring Security permissions, you will need to apply Chartstring Limits for users prior to getting started in order to enhance fund and transaction security. Until this is done, user access will be fully restricted.
- The user will only receive notification when given a role in the Admin Module, not when Chartstring Limits are applied. Once you have applied their access, please notify the user.
Chartstring Defaults
Newly added chartstring limit rows will automatically default to Full Restricted until permissions are set.
Applying Chartstring Limits
To apply chartstring limits and restrict a user's fund total and transaction access, make a selection from the drop-down menu of the desired component. Bear in mind, the more selections that are made, the more restrictive the access will be for the user.
Once selections are made, click Save.
Chartstring Security Examples
In the example below, chartstring selections have only been made for the Fund, Org, and Program components. This means the user can only view transactions and data relating to that combination of Fund, Org, and Program. The user has no restrictions within Flex 1, Flex 2, or Cost Center fields.
Please note: Where an Org has a child organization, the user can see the data relating to the Fund, Program, and any of the stipulated Org’s children.
In the following example, the user can view any transaction or data relating to this combination of Flex 1 and Flex 2 and there are no restrictions on specific Funds, Orgs or Programs.
Redundant Permissions
If you try to enter a setting that's more restrictive than an existing setting, you will be notified that the entry is redundant and unable to save the newly entered chartstring.
In this example, the bottom row allows the user unrestricted access to funds. When the top row is added giving fund restrictions, it is considered redundant and cannot be saved since broader permissions already exist.
