Docs
Troubleshooting

Troubleshooting Tideswell

The six things that go wrong most often, and the order to check them in so you find the cause quickly.

Most reported problems in Tideswell are one of six things, and nearly all of them are a setting rather than a fault. This section is organised by the symptom you actually have.

Start here: the three-layer rule

Before anything else, know that almost every "it is not there" or "I cannot do that" comes down to three layers, checked in this order:

  1. Is the module on? A module switched off makes its pages unreachable rather than hidden, so even a bookmark stops working. See How to switch parts of Tideswell on and off.
  2. Do you hold the permission? Each action has a minimum rank. See How to set who can do what.
  3. In which department? Most permissions are checked against the record's department rather than the workspace, so the same person can do something on one task and not the next.

That third layer is the one people miss, and it explains more reports than the other two combined. How to work out who can do what in your workspace is the full explanation.

Which page do you need?

Two habits that solve most of it

Read the message. Tideswell states reasons rather than failing silently: a greyed-out stage says why on hover, a refused bulk action names how many were refused and why, a skipped automation run names what was missing. The answer is usually on screen already.

Trust a blank over a zero. A dash or a "not recorded" means Tideswell could not read something and declined to guess. A zero means zero. If a figure looks suspiciously round or suspiciously empty, that distinction usually explains it.

On this page