Skip to main content
Answer

Project Transactions visiblity and access

  • August 22, 2025
  • 4 replies
  • 80 views

Forum|alt.badge.img

Hi, I’m not the most versed with the Project module, but I have a customer who uses projects and has some restriction groups configured to limit access to projects, mostly along branch lines, they have several branches. That part seems to be working, users are only seeing projects that they are assigned to in the restriction group (via project groups).  What he is reporting however is that on the Project Transaction screen, users can see and call up transactions tied to projects that they don’t have access to otherwise.  And his biggest issue is that they can actually Release these transactions as well.  

 

It also looks like they are using that Project Transaction Visibility by Account group and again, that part is working in that it is blocking access to some transaction lines, but he’s saying even with that, it still allows the user to call up the transaction and release it.   I haven’t gone through a full test on this, although I did confirm that I can see the transactions tied to projects that my user can’t see on the Projects screen.  Has anyone seen or encountered this and if so, is there anything that can be done to prevent either seeing these transactions all together or being able to release them?  He does want the user to be able to release those transactions for projects he does have access to, so it doesn’t seem I can simply do something user role access wise to block the release function.  It sounds like something customization wise might have to be done.  Thanks!

Best answer by aaghaei

@rskieresz88 

I think there is a conceptual misunderstanding. The project Transactions are created inside a batch. Each line of the batch can be associated with any project. So, in a PM Batch (if I am understanding correctly that you are creating batch in Project transactions screen) you can have verity of projects. When you go to Release Project Transactions, you actually see the Batches not the transactions. So, considering the Batch itself doesn’t have a project then it is not possible to filter out the batches by projects. Additionally, a PM batch can only have one status. Then it is expected from the system to release some of the transactions and not release some considering the header only has a single status field. I don’t think this is technically possible, at least with the current design.

If you want to customize the Release screen, you will need to append the query, so the query doesn’t only look at the PM Batches but also at the transactions inside the batches and validates the transactions against the user permission and if a user has access to ALL of the projects inside the batch, displays the given batch. This customization for sure will have a performance degradation.

 

4 replies

Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • August 22, 2025

Just a follow up on this, I did just find a post regarding the Restrict Employee check box on projects and saying it includes project transactions. While it sounds somewhat promising, I’m not sure if it would solve the issue at hand here.  On checking on the system, projects don’t seem to have that checked, but also in checking some completed projects, I don’t see any employees listed on the employee tab either.  And even if we were to use this, it sounds like it would limit who can create project transactions for the project, but does that mean it also blocks existing transactions from other branches’ projects from being seen/called up and/or released by anyone like it appears to allow now?  Not sure.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • September 26, 2025

Hi ​@rskieresz88 were you able to find a solution? Thank you!


Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • October 9, 2025

@Chris Hackett I have a bit more clarification on this after some testing and further input from the customer.  I am still seeing an issue and I believe I will open a ticket with support, but in a nutshell, once I was able to do some testing, the project transaction visibility seems to be working in that if I have restriction groups applied to project groups and have project groups assigned to projects, if I am not in the required group for the project, I can see the project transaction itself, but it is blocking me from seeing any lines for a project that I don’t have access to which is good.  Also, when in the project transaction screen, the release button is active but when I try to release, it does show an error in essence saying that I don’t have access to all the lines on the transaction, so I can’t release it, also good.  

 

The one issue we are seeing however, is that if I go into the process screen Release Transactions, that restricted transaction shows and if I select it and process it, it does release the transaction.  I would have expected it to error with the same type message I was seeing in the Project Transaction screen itself when I tried to release it.  That’s the issue the customer is seeing which he clarified just the other day.  Not sure if anyone has encountered that scenario and has any thoughts.  Seems like a bit of a bug to me.  I’m thinking there’s nothing I can really change or do with the process screen to resolve this.  The system seems to be working correctly otherwise.  


aaghaei
Captain II
Forum|alt.badge.img+10
  • Captain II
  • Answer
  • October 10, 2025

@rskieresz88 

I think there is a conceptual misunderstanding. The project Transactions are created inside a batch. Each line of the batch can be associated with any project. So, in a PM Batch (if I am understanding correctly that you are creating batch in Project transactions screen) you can have verity of projects. When you go to Release Project Transactions, you actually see the Batches not the transactions. So, considering the Batch itself doesn’t have a project then it is not possible to filter out the batches by projects. Additionally, a PM batch can only have one status. Then it is expected from the system to release some of the transactions and not release some considering the header only has a single status field. I don’t think this is technically possible, at least with the current design.

If you want to customize the Release screen, you will need to append the query, so the query doesn’t only look at the PM Batches but also at the transactions inside the batches and validates the transactions against the user permission and if a user has access to ALL of the projects inside the batch, displays the given batch. This customization for sure will have a performance degradation.