Temporary access rights automation in Dynamics Ax 2012

Finance and Operations/AX Developer Forum
1

I want to develop feature in Ax 2012 to assign and remove temporary user rights access.
Below are my requirements.

  1. new menu items (WSFD/System administration/Common/Users/Users):
    • Dialog name - Assign temporary role
    • Fields - User, Role, From date, to date
    • From date, to date - maximum 6 months
    • Description (enum - debugging, scripting, maintenance, substitution, missing user rights, other)
  • Temporary role log (WSFD/System administration/Common/Users/Users)
    (display log based on user)
    * Create New form and table
    * Buttons - Activate, deactivate
    * Filter - Active, inactive
    * Fields: User ID, User name, User role, From date, To date, Reason, Description, Active
  1. new menu items (WSFD/System administration/Periodic/Users):
  • Temporary role activate/deactivate
    (batch job which will run once per day after midnight. This job will automatically activate or deactivate user rights based on the specified ‘from’ and ‘to’ dates.)
  1. new menu items (WSFD/System administration/Inquiries/Users):
  • Temporary role log - display log for all users

img1
img11361×878 218 KB

2

Any inputs to implement this feature are appreciated.
Specifically related to batch job and how to maintain temporary user access rights table.

3

Hi Omkar,

That’s a solid requirement and a common need in AX 2012 when dealing with temporary or elevated access. While there’s nothing out-of-the-box, it’s definitely doable with a mix of custom tables, forms, and a batch job.

  • Create a table to store temporary role assignments (User, Role, From/To dates, Reason, Status).

  • Add a form to manage these records (assign, update, deactivate) and link it under System Admin so it feels native.

  • Set up a nightly batch job to activate/deactivate roles automatically based on dates.

  • Keep a log table for auditing who had access, when, and why.

We’ve seen similar setups work well for customers, one case was during audits, and the automated activation/deactivation saved a lot of admin effort. The primary goal is to maintain a clean and separate batch logic from core security data.

If you try this and hit roadblocks, feel free to reach out, I’d be glad to share more details at hardik.gupta@allgrowtech.com