Unprotecting multiple non-freeform sheets

Hi Simon,

Are you sure you attached the correct image? If you did then I'll have our engineers check it out, otherwise can you please upload the image you meant to upload. You can also use the upload images button in the Add Comment toolbar to put images into your topics/comments, rather than attaching them too mate.

Either way, I'm assuming you got the following message:

And you got this message even though your colleague is getting a protected sheets warning...

This is one of the confusing things about Modano when you first start using it - Modano protects the sheets which contain module components (i.e. non-freeform sheets) so that the modules meta data (which is stored in a very hidden sheet called 'ModanoMeta') remains consistent with the Excel content, even after workbooks are opened on computers without the Modano Excel add-in installed. Users without the Modano Excel add-in can still use open and use the workbook, editing anything on freeform sheets and assumptions within module components, but they cannot edit non-assumptions content (e.g. formulas) within module components. If they could, you would give a modular workbook to an Excel user without Modano installed, and they'd change formulas independently of their modules, which would be a disaster.

The result of this is that Excel users without the Modano add-in installed will see sheets containing module components as protected, while Excel users with Modano installed will see tham as unprotected. If you want to distribute modular workbooks to non-Modano users, and allow them to edit non-assumptions content within module components, you will need to release the Excel workbook. But bear in mind that this is a one-way street - i.e. you can't thereafter enjoy the benefits of modules, categories, automated time series, etc., within that workbook as it will be a static Excel file.

Hi Jeffrey - It varies depending on the type of model:

• For transaction/deals models, the model is commonly released towards the end of the project, often prior to the model audit taking place and/or when tight deadlines require ‘hacking’ content in ways which are not supported within modules (e.g. inconsistent formulas within blocks of categories, etc.).
• For rolling budgeting & planning models, it’s less likely that clients will be unwilling to purchase a Modano subscription, as it saves them a lot of money, but if they choose not to buy then yes, you would maintain a ‘master’ copy and they would receive a released static Excel file. The downside of this approach is that they are likely to make assumptions and formula changes to their file which you will be forced to duplicate in the master workbook, which is usually more costly for them than purchasing a subscription.

Bear in mind that clients can still open modular workbooks just like any other Excel file, and change assumptions and use the model perfectly normally. They can also change any content at all within sheets that do not contain module components –  i.e. freeform sheets – so you always have the option of including these if clients want to be able to customise content (such as dashboards) without paying for a Modano subscription.

Hence, we always discuss the pros and cons of clients not purchasing a Modano subscription, and always make it clear to them that they’ll never be in a worse position (in terms of time, cost, risk and quality) from using Modano than they would be had they used static Excel files and manual creation/editing.

The client doesn’t need the software until you hand over the model, and if they're really unsure about purchasing a Modano subscription we encourage them to try it for a month - which doesn't cost much at all - and see what they think after they've experienced the time and cost savings.

The appealing thing about the Modano proposition for your clients is that you can sell it as follows:

"We can manually build you a model from scratch for $XXX, or use Modano and do it for $XXX/2. Then, once you get the model, you can use Modano yourself for a small monthly fee per user to automate the ongoing repetitive tasks that many advisory firms firms charge hundreds of dollars per hour for, such as model roll-forward and extension, categories addition and the addition of modules such as valuations and dashboards. You don’t need to buy a Modano subscription, because the model we’ll give you will be a 100% normal Excel workbook, but there are significant time, cost and risk benefits from keeping the workbook dynamic so we’d recommend doing so."

Another client-empowerment selling point is the fact the Modano practical training exercises are all completely free and systemised via the Modano website, so they can choose whatever level of involvement they want without you guys having to run expensive, low-margin training sessions for them.

Most of our consultants usually offer 3 implementation options:

1. 100% Outsource: Build the model for the client and then handover, after which they use it and reach out whenever they want changes made.
2. Co-Build: Work with the client’s modeler to build the model so s/he understands how it’s been built and works, after which s/he owns the model and only reaches out when needing complex support or additional resources.
3. Do-It-Yourself: The client purchases a Modano subscription, does all the training, and pays for support only if they need it – i.e. they’re in complete control the whole time.

We thought clients would all go for the do-it-yourself option, but surprisingly we've found that many would rather lean on support quite heavily, particularly during the initial model scoping and build stages.

Hi Billy,

This may be a Community Edition limitation due to file size as Simon notes, or it could be something else.

Your approach of saving multiple versions of files is exactly what we recommend, although there is always the Recover Files tool (Modano tab, Help menu, Recover Files) if things go really bad.

If you're still having issues please submit a support request via the Support section of your account (www.modano.com/account/support). If it's a technical issue you will not consume any support credit time doing this.

Thanks, M.