Skip to main content

Following the settings visible in the Console

Follow the settings shown in the Console using product language.

When to use this​

  • Use it when you need to validate the environment's functional state.
  • Use it when reviewing the options visible to administrators.
  • Use it to answer users' questions about area availability.

Before you start​

  • Have an environment administration role.
  • Know which setting or area needs checking.
  • Avoid changing settings without understanding the impact on users.

Step by step​

  1. Open Environment administration.
  2. Review the areas and settings the interface presents.
  3. Read the descriptions and warnings before changing anything.
  4. Compare the current state against what users expect.
  5. When there is a change, review its impact and confirm only if needed.
  6. Tell affected users when the change alters how they use the product.

What happens next​

  • The environment stays aligned with expected use.
  • Significant changes remain traceable.
  • Users get communication in product language.

Common errors​

  • Changing a setting without reviewing the impact.
  • Using language the user cannot relate to the interface.
  • Investigating data access as though it were a global setting.

Good practice​

  • Treat settings as changes with product impact.
  • Use simple checklists for recurring validations.
  • Document decisions that are visible to users.

Next steps​