Hi Everyone,
I am fairly new to Tessitura, so please forgive me if I'm asking this in the wrong forum or if it is actually documented somewhere. I did do a search and reviewed the documentation, but could not find an answer.
We would like to limit the ability to close a batch. For example, we want someone to be able to do gift entry, but rather than having that person close the batch themselves, we want a manager to do that. So far, I've only found the Conts Batch Posting security object, which allows me to control batch posting privileges. But I haven't found any way to lock down the ability to close a batch.
Do any of you know if there is a way to do that? I appreciate your help!
Thanks,David
David -
You have to give whomever you want to close the batch Manager rights in the security module to the login group that is being used to create the batch.
Hope that makes sense!
Heather
Thanks Heather! What we want to be able to do is allow a person to create a batch and create donation transactions within the batch, but disable their ability to both close and post the batch. I found a way to shut down access to posting a batch (i.e. eliminating access to the Conts Batch Posting security object), but have found no way to disable the ability to close a batch. So far, I haven't found a security object that relates to batch closing. (I tested it out and the security group that had no access to Conts Batch Posting was still able to close their batch.)
The Manager rights you are referring to will give a manager the ability to close a batch for another user, but we want to eliminate close batch permissions for the actual user who created the batch (i.e. so a manager has the opportunity to check their work before the closing takes place).
I hope that explains more clearly what I'm looking to do.
Thanks again,David
Hi David -
Sorry I misread the question! You are right that Conts Batch Posting only controls the posting of a batch, not the closing...
I'm not sure if there is an actual security level for the closing of batches now that you ask. I assume that you don't feel confident in doing this simply through business policy and training. You didn't say if you were working with controlled batches or uncontrolled ones which makes a difference in the 'closing' of batches. With uncontrolled batches the closing of a batch really doesn't do much to Tessitura internally (i.e. the transactions are always live) and once a batch is closed a manager CAN always take ownership of it and reopen it until it is posted. If you are talking about controlled batches then that is a horse of a different color.
Oops. That sentence above should read 'once a batch is HELD a manager CAN always take ownership of it and reopen it until it is posted...' not closed. Sorry!
Thanks Heather. My apologies, I should have specified the type of batch. This is in relation to controlled batches. We may end up having to handle this through policy and training if this capability doesn't exist, but the preference would be to limit who has access to close a controlled batch, particularly since a closed controlled batch cannot be reopened (from what I currently understand). If a controlled batch is closed with errors, it would seem much more difficult to clean up after it is closed than catching those errors before the batch is closed.