Is there a way by which we can freeze Clarity so that no user can do any changes to any projects? especially cost plans and actuals.
They should be able to see/navigate through all pages as usual but no changes to be allowed for certain time window.
Fortunately in our case the concern was only related to freezing costplan updates so we used Freeze Date under Entity-> Plan Defaults to set it to way into future so that updates to plans are frozen until that date.
You could take a backup of the database at a specific time and do your analysis in a non-production system
Rights are typically used for this, but it is all or nothing and there is no time frame option.
A process good put the projects in read only mode or lock the attributes.
As urmas mentions, there is not a simple way to do selective lock out. You could work with altering access rights or create a Process Definition, but it may be involved and may not get you what you exactly want.
You mention you don't want actuals posted, and no updates to the planned costs.
This will be hard to do in a live system.
If you want a true 'snapshot' for analysis, I think making a backup copy may be the simple answer.
There isn't a way to really do this and also cater for things like the auto-rights that users get for things, coupled with not wanting to probably launch so many process instances to lock attributes and such to simulate similarly.
It does seem like an appropriate extension of this idea: Maintenance Mode Option
It's not exactly the same, but it's in the same thought space, so you may wish to create your own explicitly described idea or to vote/comment on the existing one.
We do this by having security groups that contain the write access for Cost Plans or whatever need, that we inactivate when we want to "lockout users", so that the rights are not applied and users are left only with rights granted from active groups (the view access, for example)
When using methods like this (altering user security permissions) please be aware of one thing in particular; in general Clarity will check instance level rights each and every time something is accessed. So adjusting those permissions will have an immediate effect.
For users having any global permissions, these are usually cached inside the user's session data, and changes will not be picked up until the user logs in again under a new session. Any time they are accessing the old/existing session, they will likely still be able to do the things that have been locked out in this way.
Not to say that addressing this by altering security permissions is wrong or anything, just that if considering these approaches you should be aware of the pros and cons of doing so, as it might not be guaranteed to be applied fully and immediately under these circumstances.
In our case they are global permissions (editing financial plans), and they're done on a monthly basis for a span of a few days. I completely agree, there are cons associated with this approach, but, if it works for your organization, may be better than the alternative approaches.
Retrieving data ...