Organizations and Locations

On this page

Organizations and locations each form a tree: an organization can have a parent organization, and a location can have a parent location. Together with persons and groups, they make up the Organization Management section of the Web App's sidebar, which lists Organizations, Locations, Persons, and Groups. See Persons and Groups.

Organizations and locations in the Web App

What you can see and change

Organizations and locations each have their own permissions to view, edit, and delete records. Adding a record is governed by the same permission as viewing it. See Permissions Reference.

Create and move organizations and locations

In a new 2026.1 database created with the Default Workflow, the workflow provides the following actions. See Default Workflow Configuration.

  • New Organization creates an organization, and New Sub-Organization creates one below an existing organization in its tree. Their captions are Organization and Sub-Organization.
  • New Location and New Sub-Location do the same for locations.
  • Move to... moves a record under the parent that you specify on its form. Move to Top Level removes the record's parent, so that it becomes a top-level record.
  • An organization's moves are recorded as "Organization moved" and "Organization moved to top level".

To create an organization or location:

  1. In the sidebar, under Organization Management, click Organizations or Locations.
  2. Click New, and then click the create action. The menu lists the create actions of the list's records. It shows Loading... while it fetches them, and No Actions when the records have none. Create actions that are grouped appear under their group as a submenu.
  3. Complete and submit the action's form.

To move an organization or location:

  1. In the Organizations or Locations list, select the record. Actions is unavailable until a record is selected.
  2. Click Actions, point to Actions and then to Relationships, and click Move to... or Move to Top Level.
  3. For Move to..., specify the new parent on the form, then submit it.

The trees

  • Each organization and each location has a path: the names of its branch of the tree, joined by backslashes. The path is read-only: Alloy Navigator maintains it.
  • A change that would make a path longer than 2048 characters is refused.
  • When a record is moved to a new parent, the records below it move with it. Their own parents stay the same, and their paths are rebuilt.

Statuses, types, and categories

Alloy Navigator itself defines one status for organizations and one for locations, Inactive, and one location type, Office. These values cannot be deleted, though they can still be renamed. Every other status, type, and category of these records comes from the workflow configuration.

In a new 2026.1 database created with the Default Workflow, the following values are also available. See Default Workflow Configuration. An upgraded database need not have this content, and an administrator may have changed it.

  • Organizations and locations both have the status Active.
  • Organization types include Corporation, Government, and Non-Profit.
  • Organization categories are Company, Branch, Department, and Vendor.
  • Location types are Room, Closet, Kitchen, Workplace, and Unspecified, beside Office.

Such a database starts with one organization, Alloy Software, Inc., and no locations.

The internal organization

An organization can be marked internal, which means that it is part of the company running Alloy Navigator. You cannot edit the mark directly.

  • At most one top-level organization carries the mark. Every organization in its tree is internal, and every other organization is not.
  • When the mark is set on a top-level organization, its tree is marked internal and the mark is cleared from every other organization, so marking a second top-level organization unmarks the first.
  • When the mark is set on an organization that is not at the top level, it has no effect of its own: the organization takes the value of its top-level organization.

In a new 2026.1 database created with the Default Workflow, Copy Organization sets the mark from a field on its form, and the forms of API Organization Creation and API Organization Update carry it. The directory connectors set the mark on every organization they create. New Organization, New Sub-Organization, and the move actions do not set it.

Organization records

Besides its place in the tree, an organization has a category, a location, a manager, who is a person, and contact details: phone, fax, email, web page, and two address lines. It also has a status, a type, an ID, and a workspace. An administrator can add fields to organizations.

The top of the organization form shows the organization's name, with a copy-link control, and its status. The form's tabs are General, Activity, Custom Data, Related Objects, Configuration Items, SLA, Tickets, Persons, Notes, History, and Attachments.

An SLA that an organization receives covers only the persons whose own organization it is: the SLA of a parent organization does not reach the persons of its sub-organizations. An organization can receive a given service through only one SLA; a second one is refused with the message "An organization can receive a particular service only through one SLA." See Services and SLAs.

Location records

Besides its place in the tree, a location has a name, which it must have, a free-text address, a free-text time zone, a manager, who is a person, a type, a status, and an ID. An administrator can add fields to locations.

The top of the location form shows the location's name, with a copy-link control, and its status. The form's tabs are General, Activity, Custom Data, Related Objects, Configuration Items, Notes, History, and Attachments.

How the records refer to each other

Each of these references points to one record:

Record Refers to Meaning
Person Organization The person's organization.
Person Location The person's location.
Person Person The person's manager.
Person Work calendar The person's work calendar.
Organization Organization Its parent in the organization tree.
Organization Location The organization's location.
Organization Person The organization's manager.
Location Location Its parent in the location tree.
Location Person The location's manager.
Group Person The group's manager.
User account Person The person the account belongs to. Every account has one.
Announcement Person The announcement's owner.
Announcement Service The service the announcement belongs to.
Knowledge base article Person The article's author, and its owner.
Knowledge base article Service The service the article belongs to.
Knowledge base category Knowledge base category Its parent in the category tree.

Two relations link many records to many: group membership, between groups and persons, and article categorization, between knowledge base articles and knowledge base categories.

Delete an organization, location, or person

An organization or location cannot be deleted while another record refers to it, for example a person whose organization or location it is, or a child organization or location below it in the tree. The record's relationship links, attachment links, tags, and flags do not block the deletion: they are removed with the record.

To delete records from a list:

  1. Select the records and open Actions.
  2. Click Delete and confirm when asked. Delete is unavailable when Alloy Navigator reports that the selection cannot be deleted.

  3. If Alloy Navigator does not allow the deletion, no confirmation is asked, and the message "You do not have enough permissions to delete this item." appears.

  4. Otherwise, you confirm the deletion, and the selected records are deleted one at a time. When the deletion succeeds, the list is refreshed. A record that another record still refers to is refused with the message "Unable to delete/modify object because it is referenced by other database object(s). To delete/modify the object, you need to remove these dependencies first." The message does not name the referring record, the records after the refused one are not deleted, and the list is not refreshed.

A person cannot be deleted while an account belongs to the person: the account must be removed first. See Accounts. Removing an account also removes its role memberships and its sessions. When a person is deleted:

  • Manager references to the person are cleared.
  • The person's own data is deleted with the person: logins, e-mail addresses, devices, group memberships, ratings, calendars, snippets, settings, personal views, dashboards, license allocations, and flags.
  • Shared views and widgets of the person are kept and no longer belong to anyone.
  • Stock movement history keeps the person's name.

In a new 2026.1 database created with the Default Workflow, a person can be taken out of use instead with Mark Inactive, which is in the General group of the person's actions; your security role decides whether it is offered to you. It sets the person's status to Inactive and leaves the records that refer to the person in place. Mark Active reverses it. A person at the Inactive status cannot sign in.