Tenants
A tenant is the record of one of your clients in Overseer. This page explains what a tenant holds, where tenants come from, how they are arranged and what you can do from the Tenants screen.
What a tenant is
A tenant is Overseer's record of one client. Each tenant has its own computers, its own people and its own settings, and Overseer keeps each client's computers, deployments and history apart from every other client's.
Tenants exist for three reasons. They are the boundary that keeps one client's information away from another's. They are a target: a deployment aimed at one client applies to every computer in that tenant. And they are where the settings that differ from client to client are kept, such as business hours, time zone and maintenance windows.
Where tenants come from
- By hand. You create a tenant on the Tenants screen and give it a name.
- From an integration. Where your remote management tool, your PSA or your identity provider is connected, it can supply the list of clients, and Overseer keeps its tenants in step with it.
Where an integration can supply the list, let it. One source for client names means a client is never recorded twice under two spellings, and a new client appears in Overseer without anyone remembering to add it.
Parent and child tenants
A tenant can sit beneath another tenant. This suits a client that is really several organisations, such as a group with separate offices or subsidiaries. Each child is still a tenant in its own right, with its own computers and settings.
The Tenants list
The Tenants screen lists every client you are allowed to see. Each column can be searched, filtered and sorted, so a long list stays usable.
From the list you can create a tenant, open one, or select several and use Batch actions to change the same preference on all of them at once.
Inside a tenant
Opening a tenant shows the tags it carries at the top, followed by everything that belongs to that client.
- Computers. The client's computers, managed one at a time or in bulk.
- Sessions. The maintenance sessions that have run for this client. A maintenance session is one complete ordered pass over one computer.
- Actions. The individual pieces of work done inside those sessions.
- Software. The software on the client's computers, with the option to deploy from the same place.
- Software search. A search for a named piece of software across the client's computers.
- Schedules. The schedules that run recurring detection and maintenance for this client.
- Preferences. Business hours, time zone, and whether deployments aimed at every client apply to this one.
- Name and structure. The tenant's name, its parent tenant and its tags.
What a tenant's settings affect
A tenant's settings reach further than the tenant's own page.
- Scheduled work. A schedule's times are read in the client's time zone where one is set, and each client can have its own maintenance windows.
- Deployments. A deployment aimed at every client reaches a tenant only if that tenant takes part in them.
- Access. People see and do only what their role allows, and each client's computers, deployments and history are kept apart.
- Targeting. A tag on a tenant can be used to aim a deployment at a group of clients.