> ## Documentation Index
> Fetch the complete documentation index at: https://docs.osto.one/llms.txt
> Use this file to discover all available pages before exploring further.

# Objects Management

> Reusable building blocks — domain categories, application groups, port objects, and schedules — that you reference when defining policies.

**Objects** are the reusable building blocks you reference when writing policies. Instead of repeating the same domains, ports, or time windows in every rule, you define them once as an object and reuse them across your policies. Osto ships with a large set of predefined objects, and you can add your own.

> **Path:** Objects

Objects come in four types:

<CardGroup cols={2}>
  <Card title="Domain Category" icon="globe">
    Named groups of domains used by domain-filtering policies.
  </Card>

  <Card title="Application" icon="grid-2">
    Predefined application groups used by app-control policies.
  </Card>

  <Card title="Port" icon="ethernet">
    Protocol/port definitions used by server-access policies.
  </Card>

  <Card title="Schedule" icon="clock">
    Time-based classes that control when a policy applies.
  </Card>
</CardGroup>

## Domain Category

A **domain category** is a named collection of domains. Osto includes 66 **predefined** categories (Web Hosting, Web Analytics, URL Shorteners, Violence, and many more) that domain-filtering policies use to allow or block whole classes of sites at once. You can also create your own.

<Frame caption="Domain Category — predefined categories plus any you add.">
  <img src="https://mintcdn.com/osto/cnHEjTD9QY3tscQi/images/objects/objects-domain-category.jpg?fit=max&auto=format&n=cnHEjTD9QY3tscQi&q=85&s=70b5ec4c6bae91fc3389dabf656713b3" alt="Domain Category page listing predefined domain categories with Name, Type, and Actions columns" width="2940" height="1544" data-path="images/objects/objects-domain-category.jpg" />
</Frame>

The table shows each category's **Name** and **Type** (predefined categories are read-only). Use **Search Domain Category** to find one, or **Add Domain Category** to create a custom one:

* **Name** and an optional **Description**.
* **Add Manually** — type a comma-separated list of domains; wildcards are supported (e.g. `google.com, *.facebook.com`). **Discover Related Domains** helps expand the list.
* **Import Domains** — upload a `.txt` file of domains (a sample file is available to download).

## Application

The **Application** page lists Osto's predefined application classification groups — **Instant Messaging, Web Browser, P2P, VPN,** and **All Apps**. These are the groups your **App Control** policy uses to allow or restrict categories of apps. The list is reference-only (you select these groups from within policies rather than editing them here).

<Frame caption="Application groups — the predefined classifications used by App Control.">
  <img src="https://mintcdn.com/osto/cnHEjTD9QY3tscQi/images/objects/objects-application.jpg?fit=max&auto=format&n=cnHEjTD9QY3tscQi&q=85&s=3ffce390b838a9b81587008a64e59af0" alt="Application page listing predefined application groups with Name and Description" width="2940" height="1544" data-path="images/objects/objects-application.jpg" />
</Frame>

## Port

A **port object** names a protocol and port (or set of ports) so you can reference it in **secure-server access** policies. Osto includes common services (DNS, LDAP, SMB, SYSLOG, IKE, and more).

<Frame caption="Port objects — named protocol/port definitions.">
  <img src="https://mintcdn.com/osto/cnHEjTD9QY3tscQi/images/objects/objects-port.jpg?fit=max&auto=format&n=cnHEjTD9QY3tscQi&q=85&s=f77228f2307d23e15be22684c884479d" alt="Port page listing port objects with Name, Protocol, Type, Ports, and Actions" width="2940" height="1544" data-path="images/objects/objects-port.jpg" />
</Frame>

The table shows each object's **Name**, **Protocol**, **Type**, and **Ports**. To add one, click **Add Port Objects** and provide:

* **Name**.
* **Protocol** — **TCP** or **UDP**.
* **Type** — **Single Port**, **Port Range**, or **Port List** — then the matching port value(s).

## Schedule

A **schedule** controls *when* a policy is in effect. The built-in **Forever** schedule applies a policy at all times; you can add time-bound schedules for policies that should only apply during certain windows. Schedules appear as the **Schedule Class** option in endpoint policies.

<Frame caption="Schedules — control when a policy applies.">
  <img src="https://mintcdn.com/osto/cnHEjTD9QY3tscQi/images/objects/objects-schedule.jpg?fit=max&auto=format&n=cnHEjTD9QY3tscQi&q=85&s=89d0b8a57e91edd260d0fff1470d127e" alt="Schedule page listing schedule objects with Name, Description, Duration, and Actions" width="2940" height="1544" data-path="images/objects/objects-schedule.jpg" />
</Frame>

To add one, click **Add Schedule** and set a **Name**, optional **Description**, and a **Duration**:

* **Forever** — always active.
* **On Time** — active only within a date range and during specific time windows. You set a **From Date** and **To Date**, then add one or more **day + from-time/to-time** entries (use **Add Time Entry** for multiple windows).
