Locking Workflows
Would anyone be willing to share how they are locking data to end users, but still allowing consolidation users to make adjustments? When implementing OneStream, we created workflows for users to lo...
Forum Discussion
Hello!
We have a ConsolAdj channel under each sub's workflow so we can lock the ADJ channel (and import and forms) but leave the month open and the consolidations team can still post JEs to those entities from their own ConsolidationAdmin.ConsolAdj channel. It's effectively locked for topsides for the sub but still open for consolidations.
Here's how the sub's WF channel is set up:
And for consolidations:
From a user perspective, they don't see anything different on the workflow because they don't have access to that channel:
Hope that helps! Let me know if you have any questions.
Further explanation - we've narrowed down forms security (via Application > Cubes > Data Access tab > Data Cell Conditional Input section) so users are only able to load forms data to very specific intersections for actuals. As a result, we generally don't worry about locking the month to prevent forms loads which is something that might be a bigger issue for you and my ConsolAdj suggestion above likely won't resolve.
In addition to leaving the month unlocked for the Sub's Workflow for Conso adj, how do you manage the Certification step of the Sub ? Is the Sub only certifying their Workflow once Conso finished making adjustments ?
Yes, certification is done only once everyone has completed all their activities for the month.
