Hide guidelines in users

@lubos i want to keep hidden in some users because we charge them for training .

I’m also looking for a way to hide guidelines for users. In my Settings menu (Cloud version), I don’t see any “Show guidelines” option under Themes or anywhere else.

Is there a way to disable the help text panels for all users? If not, is this something that can be enabled by support?

Thanks!

You don’t need do degrade product functionality to ensure there is value in training.

Even with good documentation users still benefit from training. Sure they can just ask you when you are with them but for all the rest the time they will be more frustrated with the product even if eventually asking you for many queries.

3 Likes

@Patch @lubos in my case showing guide lines to users without administrator permission is not good you should give administrator right to show or hide guide lines if this can implemented so will be good for us thanks. hoping positive response thanks.

@lubos Training is 40% part of our business if guidelines are going to user without administrator permission so we have loss of that 40 %.

I decided to reply. I respectfully disagree. Hiding the guidelines from regular users doesn’t protect training revenue — it just creates frustration. Even with good documentation that users can freely solicit, most users still benefit from proper training. They learn faster, avoid mistakes, and ask smarter questions.

Being transparent actually helps your business grow: more happy users → more people who eventually need paid training or support. In accounting that is even more valuable.

Customers shouldn’t be locked out of basic help. Openness builds trust and usually brings more business, not less. So you will not only retain these 40% but possibly grow your business because you are being honest, transparent and helpful. This will also build trust in your support and training.

2 Likes

@eko Thank you for your thoughts. We understand your perspective, but let us explain why this is different for our situation.

1. Language barrier
Our users do not speak English. The guidelines are in English, so they provide zero value to them. They don’t understand the help text — it only causes confusion and frustration, not clarity.

2. User behavior
When our users see guidelines, they try to experiment and change settings. This creates problems and mistakes. We have to spend time fixing things instead of helping them with their actual work.

3. We are not asking to remove guidelines
We are asking for optional control — a simple permission setting that lets administrators decide who sees guidelines.

For example:

  • Users who understand English → guidelines on

  • Users who don’t understand English → guidelines off

  • Administrators → full control

This is not about locking customers out of help. It’s about giving businesses the flexibility to manage their users based on their real needs.

We hope you can understand why optional control benefits everyone. Thank you.

1 Like

I don’t think this will help, because this guideline is also available in a desktop version.

It’s also in the support button at the top. If any of your trainees are curious, they can search for the application and get all the information.

It’s better to be transparent and add value to your client, this will improve your image.

All the best,

2 Likes

Thank you for your comment. You are right — guidelines are also available in the desktop version and through the support button. Curious users can always search and find information elsewhere.

However, our point is not to block all information completely. We know users can find answers if they search. Our goal is to reduce unnecessary confusion and experimentation within our own instance.

Our users face two challenges:

  1. Language — They do not speak English, so the guidelines are useless to them

  2. Behavior — When they see options, they try to click and change settings, which creates mistakes we have to fix

We are not asking to remove guidelines from the software. We are asking for optional control — a simple permission setting that lets administrators decide who sees guidelines.

We believe transparency is important. We also believe businesses should have flexibility to manage their users based on their real needs — like language barriers and user permissions.

Thank you for your thoughts. All the best.

Fair point.

The format and approach to guideline was completely changed several years ago to enable multi language support. If that has only been partially implemented, then adding multi-language guide support is a reasonable request.

And how do you learn?

I learn by experimenting and correcting my mistakes. Sure some will need your help while they learn, that’s why they pay you.

User experimenting and learning is not a bad thing. The end result is more educated users who value their accounting tool even more.

You’re absolutely right.

User experimentation is not a bad thing in fact, it’s one of the most effective ways people learn. When users feel safe to click, explore, and make mistakes, they become more confident and capable. That ultimately leads to higher satisfaction and retention.

If the current interface doesn’t clearly communicate how settings work or if multi-language support is incomplete then users may

  1. Get frustrated when clicks don’t do what they expect
  2. Assume something is broken
  3. Need more support than necessary