Adjusting AHIMA Staff Permissions in Aptify

Created by Kevin Schmidt - HCPro, Modified on Thu, 9 Oct at 3:15 AM by Kevin Schmidt - HCPro

When an AHIMA staff member has restricted permissions in Aptify, they will typically receive an alert to contact system administrator. Follow the steps below to confirm permissions.

Verifying Staff Aptify Permissions

1. In Aptify, go to Users Administration → Users → All Active to open the Wizard for the employee and confirm EndUser is marked , then click Next.

2. Confirm that CRM, Commissions, Education, Fundraising, and LMS are marked and click Next.

3. Confirm Permit is marked at the top and Active User is marked below and click Next.

4. Confirm employee name and click Next. Ignore Copy an existing user's profile unless verification to duplicate is received.

5. Confirm Object Repository Context is set to and Culture is set to EN (en), then click Next.

6. Confirm Aptify Groups dependent on employee job function are marked and Primary Group is set to according to employee department, then click Next.
**TO REPLICATE STAFF LOG-IN: take screenshots of current active Aptify groups for reference in part 2: staff log-in replica

7. Double-click the Employees entity then click on Entity Record to open the linked User record.

8. In the Details tab, confirm the employee permissions are marked (dependent on verified permissions).

9. Save and close employee record then click Finish in the Aptify User Administration Wizard.

Part 2: Staff Log-in Replica

1. Pull up the saved screenshots of staff Aptify groups for reference then in Aptify, go to Users Administration → Users → Not Trusted to run view.

2. Select one of the pre-established user IDs (i.e. ahimaFoundation ; ahimaCustomerService ; MeetingUser ; SalesUser ; ExecutiveUser) and run the Aptify User Administration Wizard.

3. Make note of the generic password saved in the wizard description (step 6 of wizard) and go through all prompts to make edits matching the staff user's settings then click "Finish".

4. Close Aptify then relaunch the application to log-in as the pre-established User ID using the generic password and try to recreate any errors or confirm the staff account is now in good standing.

Attachments (10)