It depends (but I guess for most real-world situations the answer is no, you risk to run into trouble).
A general-purpose audit trail may collect data which, depending on the details, might be affected by laws of data security and privacy of the jurisdiction where your application will be used. If those laws will force you to keep the data only accessible for privileged personal, or if those laws will force you to anonymize that data, or if they force you to delete them after a certain period of you might run into trouble if it is also used for controlling other business logic.
Another thing to consider is if the audit data is stored in a form which can be directly used for your business, or if it is stored as something like a weakly structured log file. The latter is likely when the audit trail was originally not meant to be used for business logic. If that is the case, you will have to parse the log file and reconstruct things like the user name from it. Such an approach can easily lead to a brittle and overcomplicated solution.
So if none of those reasons don't apply to your system, and you are confident they won't apply within a reasonable time period, then you may take that route.
Otherwise, it is probably simpler and more maintainable to build a "business-specific" trail which stores exactly the information you need to control your business logic, in exactly the form you are going to use it, with the access rights and life time your system requires.