Preferences
Preferences are the settings that shape how Overseer behaves. They come at three levels - your whole instance, one tenant and your own account. This page lists what each level controls.
What preferences are
Preferences are standing settings. A deployment says what should be true on a computer. A preference says how Overseer itself behaves, such as whether it sends emails after a session or how long a script may run.
Preferences are found under Show more.
They come at three levels:
- System. Applies to everything in your Overseer instance.
- Tenant. Applies to one client. A tenant is the record Overseer keeps for a client.
- User. Applies to your own account and nobody else's.
System and tenant preferences are for Administrators. User preferences are yours to set.
System preferences
| Area | What you can set |
|---|---|
| Emails | Whether Overseer sends emails after detection and after maintenance. They are on unless you turn them off, and turning them off stops them for every client |
| Emails | People who receive a blind copy of every email Overseer sends |
| Emails | The default branding used on emails |
| People | Whether Overseer records who is using each computer at regular intervals, to work out the computer's primary user |
| Computers | Whether a new computer with a freshly installed Windows is treated as a known computer that has been wiped and set up again |
| Computers | Whether every inventory result is kept, or only the latest |
| Computers | Whether a computer's inventory is refreshed automatically when its details become out of date |
| Computers | Whether each tenant may choose to run maintenance automatically on newly reported computers |
| Computers | How many days an offline computer may go without its agent connecting before it counts as stale |
| Scripts | The default time limit, in seconds, for scripts that Overseer runs |
| Integrations | Whether each integration has an audit view |
The default time zone
Your instance has a default time zone, set here. Each tenant can set its own. A schedule's times and a maintenance window are read in the tenant's time zone where one is set, and in the default otherwise.
Tenant preferences
Tenant preferences can be managed from the tenant itself, or from Preferences by choosing the tenant.
| Area | What you can set |
|---|---|
| Computers | Which computers are left out of sessions. Nothing is deployed to an excluded computer, though inventory still runs on it |
| Computers | Whether this tenant and its computers are kept out of deployments and schedules that target every client |
| Computers | The same wiped-computer rule as the system preference, set for this tenant |
| Computers | Whether newly reported computers in this tenant are onboarded |
| People | Whether this tenant's computers are tracked for their primary user. It takes effect only when the system preference is on |
| Maintenance | The client's business hours and time zone |
| Emails | Whether detection and maintenance emails are sent for this tenant |
| Emails | People who receive a blind copy of every email sent for this tenant |
User preferences
| Area | What you can set |
|---|---|
| Colour theme | A light or a dark theme |
| Personal information | Whether personal information on screen, such as the names of clients and people, is hidden behind asterisks |
Masking changes only what your own screen shows. It is useful when other people can see your screen.