This page explains how to set up Relationships between Organizations in ALTA's AMS — specifically how one organization (e.g., a branch or subsidiary) is linked to a parent organization. It is essential reading for staff who manage organization records and need to maintain accurate structural hierarchies.
Relationships – Branch-Structure Parent. The default Relationship Type for Organizations is Branch to Structure Parent. This is the equivalent of the Subsidiary-Parent Organization Relationship in the prior AMS product, GoMembers.
Made with DASH A.i.This section is intended to briefly summarize the purpose of the page. Based on the content below, here is a working description:
Setting Relationships for Organizations allows ALTA staff to formally link one organization to another within the AMS — for example, connecting a branch chapter to its parent/national organization. This ensures the hierarchy is reflected correctly across member records and reporting.
If this section is left blank in the SOP, consider adding a one- or two-sentence summary so staff can quickly confirm they've landed on the right page before reading further.
Made with DASH A.i.This section should capture the governing rules for how organization relationships may be set. Based on the page content, the following rule is established:
In practice, before creating a relationship, confirm which organization is the "child" (Branch) and which is the "parent" (Structure Parent) to avoid linking records in the wrong direction. Additional business rules — such as whether one organization can have multiple parents — should be documented here as they are identified.
Made with DASH A.i.This section is currently empty. Below is grounded, practical guidance based on the documented behavior:
Coming from GoMembers? The Branch–Structure Parent relationship is the direct equivalent of the Subsidiary–Parent relationship you used previously. The concept is the same; only the terminology has changed in the new AMS.
When searching for a parent organization to link to, make sure the parent org record already exists in the system before attempting to create the relationship — otherwise the lookup will return no results.
Double-check the direction of the relationship before saving. Accidentally setting a parent org as the "branch" of one of its own subsidiaries can create circular or incorrect hierarchy data.
Made with DASH A.i.This section documents the core procedure for setting an organization relationship.
Relationships – Branch–Structure Parent The default Relationship Type when linking two organizations is Branch to Structure Parent. This is the AMS equivalent of the Subsidiary–Parent Organization Relationship from the prior AMS product, GoMembers.
The step-by-step screenshot walkthrough for this process should be added here. Each major click or field entry benefits from an annotated screenshot to reduce staff error.
Made with DASH A.i.This section is currently blank. It can be used to capture edge cases, exceptions, or historical context not covered elsewhere.
In practice, this is a good place to note:
As staff encounter edge cases, this section should be updated so institutional knowledge is not lost.
Made with DASH A.i.This section is currently empty. Suggested keywords based on page content (for search and discoverability):
Organization Records · Relationships · Branch · Structure Parent · Subsidiary · Parent Organization · GoMembers · Hierarchy · AMS · Org Linking
Populating keywords helps staff find this SOP via internal search. Add any alternate terms your team commonly uses.
Made with DASH A.i.This section is currently empty. Once identified, related SOPs to link here might include:
Link related SOPs here so staff can follow a logical workflow without having to search from scratch.
0 files attached to this page