Providing permission to perform action on an electronic ticket

A system for providing permission to a user to execute an action on a workflow driven ticket received by the user on a user interface, the system comprising:

• an authorization engine operable for:
• receiving a action type identifier to be performed on a ticket and at least one correlated object needed for performing the action;
• based on the action type, determining a universal permission tuple, and a dependency map;
• determining necessary permissions for the user to perform the action of the workflow driven ticket by constructing a ticket based permission tuple by mapping the dependency map to the universal permission tuple and supplementing a role based permission tuple with the ticket based permission tuple;
• a ticket metadata repository for storing the universal permission tuples and the role based permission tuples.

An article of manufacture, comprising a tangible storage medium comprising machine readable instructions which when executed by a machine cause the machine to perform a method of providing permission to a user to perform an action on a workflow driven ticket, the method comprising:

• accessing the ticket to determine an action type to be performed on the ticket, and a correlated object associated with the ticket;
• determining a role based permission tuple based upon a role of the user;
• generating a universal permission tuple based upon the action type, the universal permission tuple having one or more object types and corresponding operations to be performed on the object types associated with the ticket;
• based upon the correlated object, generating a dependency map identifying one or more auxiliary objects related to the correlated object;
• mapping the dependency map to the universal permission tuple, to construct a ticket based permission tuple, the ticket based permission tuple comprising a particularized permission tuple including an instance of at least one of the one or more object types of the universal permission tuple and the corresponding operation;
• supplementing the role based permission tuple with the ticket based permission tuple, to provide the permission required to execute the action;
• and
• based upon an execution of the action, partially revoking the permission by removing the ticket based permission tuple.