Settings
The Settings section (/settings, System → Settings) holds Orbita's system-wide parameters: general environment settings, locales, mail, incoming mail (IMAP), the Telegram bot, LDAP/Active Directory connections, entity metadata migration, and installing ready-made presets.
The section is available to administrators and holders of the admin.settings permission ("System settings & license", see Admin sections access).
Changes take effect only after clicking Save Changes in the top-right corner — it becomes active as soon as anything is edited on any tab.
Tabs
| Tab | Purpose |
|---|---|
| General | Core system parameters: URL, language, time zone, date/time format, file upload limit |
| Locales | Which interface languages are available to users, and in what order |
| The SMTP server for outgoing mail (notifications, emails) | |
| IMAP | Connecting a mailbox to receive incoming messages |
| Telegram | Connecting a Telegram bot — both as a source of incoming messages and as a notification channel |
| LDAP | Connecting to Active Directory / OpenLDAP for employee login |
| Migration | Entity metadata transfer and importing data from JSON |
| Presets | Installing ready-made entity sets (presets) on top of the current system |
Locales
The Locales tab manages the list of interface languages visible to users of this installation (tenant):
- tick which of the system-supported locales are available to users;
- drag to set their order — it defines the order in the language switcher;
- at least one locale must stay enabled.
Users pick their language from this set in their profile; the Default language on the General tab applies to new users and must belong to the selected set. Localizable values (entity names, menu items, portal texts) are edited in the enabled locales.
General
| Field | Description |
|---|---|
| System URL | The main address Orbita runs on (used, for example, in links inside emails) |
| Default Language | The interface language for new users |
| Time Zone | The default time zone |
| Date Format | The date display template |
| Time Format | 24-hour or 12-hour |
| Maximum Upload File Size, MB | The size limit for a single attachment |
Mail (SMTP)
Settings for the server Orbita uses to send emails (notifications, invitations, password resets, etc.):
| Field | Description |
|---|---|
| Host | The SMTP server address |
| Port | The connection port (usually 587 or 465) |
| Encryption | The connection's encryption type |
| Login / Password | The mailbox credentials |
| From Address / From Name | The sender address and name the recipient will see |
At the bottom of the tab is a field for a test email and a Send Test button: the email is sent using the current (even unsaved) parameters, letting you verify the setup before saving.
IMAP (incoming mail)
Settings for the mailbox Orbita polls to receive incoming messages:
| Field | Description |
|---|---|
| Host | The IMAP server address |
| Port | The connection port (usually 993) |
| Encryption | The connection's encryption type |
| Verify Certificate (SSL) | Toggle for validating the server's SSL certificate |
| Login / Password | The mailbox credentials |
Control buttons:
- Test Connection — a trial connection to the server using the current (saved) parameters, without fetching emails
- Fetch Mail Now — starts collecting new emails immediately, without waiting for the scheduled automatic check
Both buttons are disabled if there are unsaved changes — settings must be saved first.
Telegram
| Field | Description |
|---|---|
Bot Name (t.me/...) | The bot's name, used to display a link to it (filled in automatically after a successful token check) |
| Bot Token | The token issued by Telegram when the bot was created via @BotFather |
Control buttons:
- Verify Token — calls the Telegram API to confirm the token is valid and pulls in the bot's name
- Set Webhook — registers Orbita's address with Telegram so messages to the bot are delivered instantly (without this, background long polling can be used instead). This button is also disabled when there are unsaved changes
Messages sent to the bot land in Incoming Messages under the Telegram channel.
LDAP / Active Directory
Lets you connect employee login through a corporate directory:
| Field | Description |
|---|---|
| Enable LDAP | The feature's master toggle |
| Directory Type | Active Directory or OpenLDAP — selecting one fills in the typical attribute values below |
| Host / Port | The directory server's address and port |
| Encryption | STARTTLS, LDAPS (SSL), or none |
| Verify Certificate (SSL) | Certificate validation |
| Base DN | The root node for user search |
| Bind DN / Password | The account used to connect to the directory |
| Account Suffix | Appended to the login during authentication (e.g., @corp.local) |
| User Attributes | Mapping of directory fields: login, email, first name, last name, display name, middle name, group |
| Default Org Unit | Where to place new employees found in the directory |
| Auto-create Users | Toggle for auto-provisioning on first login |
The Test Connection button tests the connection parameters. The Manage Mappings link leads to the section for mapping LDAP groups to roles/permissions in Orbita.
Migration
A utility tab for transferring data between environments:
- Entity Metadata Transfer — export/import of a selected entity's structure (fields)
- Data Import — loading records for a selected entity from a JSON file
You must select an entity from the list first, otherwise file actions are disabled.
Presets
Ready-made sets of entities and settings (for example, a typical Service Desk) that can be installed in one action. Already-installed presets are marked Installed and can't be installed again; new ones can be checked and applied via Apply Selected Presets.
TIP
Presets are built-in packages: the same mechanism is used to move your own solutions between installations and ship versioned updates. See what each preset contains in Use Cases, e.g. Service Desk (IT Support).
License (on-premise)
On self-hosted installations there is a License page (/license) next to Settings — it shows the license state and accepts the .lic license file from your vendor.
The page displays: license type and edition, holder, validity period, the user limit and current usage. Possible states:
| State | Meaning |
|---|---|
| Valid | The license is active; an expiry warning appears in advance |
| Grace period | Expired, but the system stays fully functional for the grace window — time to renew |
| Read-only | Grace elapsed (or the license was revoked) — data is readable, changes are blocked until a valid license is uploaded |
| No license | A fresh installation runs fully functional for a starting window (30 days), then switches to read-only |
To apply a license, upload the .lic file on this page — the state refreshes immediately, no restart needed. The SaaS edition does not use this page.
Platform-level features
Some capabilities are toggled by the platform operator rather than tenant settings. For example, the business processes module can be disabled globally or per tenant — the corresponding sections simply disappear from the menu.