Settings (Company, Application and Caches)

The Settings section in Administration → Settings holds three pages: Company, where you set your organisation's details and the logo used for branding, Application, a read-only view of the configuration your Weissr environment is running with, and Caches, where you can clear the data Weissr keeps in memory. This page explains what each one does and who can reach it. It is written for administrators.

Where the Settings pages live

Open Administration → Settings. The section opens on Company, and the left sidebar lists the three pages.

📌 Note: The three pages do not share a permission level. Company is available to both Administrator and Capex Management configuration, while Application and Caches require the Administrator permission.

Company

The Company page holds your organisation's details and the logo used for branding. There is one company record for the whole environment, so these settings apply everywhere in Weissr.

Company details

Fill in the form on the left of the page and select Save.

💡 Info: The company details are descriptive. They are stored and shown back on this page, and no other part of Weissr uses them. The logo is the setting on this page that changes what other people see.

Company logo

The right side of the page manages a single logo image.

1. Select the file field, or drag an image file onto it. Only image files are accepted.

2. Select Upload logo.

3. To show the logo in the navigation menu, set Use logo for branding to Yes in the details form and select Save.

Before you upload anything the panel reads No logo uploaded. Once a logo exists, a Delete logo button appears next to the upload control.

📌 Note: Your logo is used in two places, and Use logo for branding controls only one of them. It decides whether the logo appears next to the Weissr logo in the navigation menu. The Capex Management custom report PDF footer uses your logo whichever way that setting is set, and falls back to the standard Weissr logo when no company logo has been uploaded. Deleting the logo therefore changes those report footers too.

Application

The Application page shows the configuration your Weissr environment is currently running with, grouped by where each value came from.

📌 Note: This page is read-only. Nothing on it can be edited and there is no save action. It is there so you and Weissr support can check how your environment is set up. Configuration is changed on the server, so contact Weissr support if something needs to change.

Finding a property

The Search properties and values box at the top filters the page as you type.

• Matching is case-insensitive.

• It searches both the property name and its value, so you can look up a hostname or a port number, not only a name.

• Sources with no remaining matches disappear, leaving only the ones that contain a hit.

Hidden values

Anything that could expose a password or a key is masked before it leaves the server, so it never reaches your browser. You will see a masked value where the property name refers to a password, secret, key, token or credentials. For a web address, only the password inside the address is hidden, so the host and port stay readable.

🔒 A masked value cannot be revealed from this page. If you need one checked, contact Weissr support.

Caches

Weissr keeps frequently used data in memory so it does not have to be read from the database on every request. This makes the application faster. The Caches page lists what is held and lets you clear it.

Clearing a cache

The page groups the caches and lists each one.

• Clear next to a single cache empties that one cache.

• Clear all caches at the top empties all of them.

Both buttons are disabled while a clear is running, and a confirmation message appears when it finishes.

⚠️ Warning: Clear all caches takes effect immediately and does not ask you to confirm. There is no second step and no undo.

When you should clear a cache

Most of the time, you should not. Weissr clears the affected data automatically whenever something changes. Editing a user group clears the user group data, changing a permission clears the permission data, and so on. You do not need to clear anything after changing a setting.

Clear a cache when Weissr support asks you to as part of investigating a case, or when you suspect Weissr is showing out-of-date information after data was changed outside the application, for example by an integration.

Clearing a cache does not delete or damage any of your data. Everything is read back from the database. What it costs is speed: the information has to be rebuilt the next time somebody needs it, so the first users to open the affected pages will wait longer than usual. On a busy environment that is noticeable.

What is held in the caches

The names on the page are technical, and you do not need to interpret them to use it. Broadly, the caches cover three areas:

• Capex Management: capex nodes, meta properties, user settings and the nodes each user is permitted to see.

• Common: users, user groups, permissions, currencies, exchange rates, custom translations and failed sign-in counters.

• Capex Strategy: alternatives and their hierarchy, project settings, node permissions and calculated sensitivity results.

💡 Info: How large each cache can grow and how long it holds its contents are set on the server, not on this page. Contact Weissr support if you think they need tuning for your environment.

Access

The three pages do not share one permission level.

If you hold only Capex Management configuration you will see Company in the sidebar, but not Application or Caches.

👉 Learn more about Permissions

Common questions