Enabling in-app Navigation for SharpenDB

This article covers the steps that a Sharpen Care Team member (with Database write-access) can perform, in order to enable customer administrators to be able to access SharpenDB from the “configuration” drop-down menu in Sharpen Admin.

Step 1 - Identify the crm-companyID value of the account you’re looking to make an update for:

Open

• This is an important value (10022 in the screenshot above) as we’ll use it to locate some User Group configuration info for the appropriate customer organization.

  • The crm-companyID also tells us what database to run our updates against (IZ0 or IZ1, depending on the customer).

Step 2 - Locate the “Administrators” default User Group that exists for every customer account:

Open

• The specific table to check is the fathomrb.userGroups table (filtered on the “crm-companyID” value that we see associated to a certain environment

  • Make note of the “userGroupID” value, as this is the final record-specific value we need to make our permission update

Step 3 - Locate the correct configuration info for the “Administrators” User Group

• Change your database navigation from fathomrb.userGroups → fathomrb.UserGroupsConfig

  • Filter on the “userGroupID” value we pulled from the “UserGroups” table (in this case, 109)

Step 4 - Modify the “SharpenDB” column value to grant navigation permissions

• For the “UserGroupID” we’re looking to modify, you can either scan to the appropriate column entry for “sharpendb” and make a manual toggle change (from 0 → 1 to enable the permission), or you can run the following command (making sure to update your UserGroupID value accordingly):

  • UPDATE `userGroupsConfig` SET `sharpendb` = '1' WHERE `userGroupsConfig`.`userGroupConfigID` = 109;

Step 5 - Cleanup items and verification testing

Following your change, make sure to post the activity to the appropriate channel in Slack - so that other internal teammates at Sharpen are aware of the database activity.

You can confirm that the change had the desired effect by either telling the customer to refresh their browser tab (to pull in the updated permission flag) or you can login with a service account tied to the “Administrator” User Group and verify that the “SharpenDB” entry shows up in the config drop-down menu: