Overview
The Org Structure settings page is where you model your organization as a top-level agency (your TopCo) with one or more branches underneath it, so that users, documents, licenses, and compliance records all attach to the right legal entity. From a single screen you review the full hierarchy, add a new branch, rename one, take over branches a market created in your account, and start a merge when two branches end up sharing an NPN.
What is Org Structure (Settings)?
Org Structure (Settings) is where you declare who you are as a downstream organization: which entity sits at the top, which branches sit beneath it, and which of those branches you actively manage versus which ones a carrier or MGA stood up on your behalf. Getting this tree right keeps licenses, documents, users, and policy data attached to the correct branch instead of being dumped onto a single catch-all entity.
Who uses it. Agency administrators, principals, and licensing managers at downstream organizations (retail agencies, brokerages, wholesalers, and TPAs) who own how the organization is represented to carriers and MGAs, and who decide which branch holds which licenses, employs which producers, and signs which appointments.
Capabilities the page unlocks:
See your TopCo and every branch in one expandable tree, with the legal name, branch name, and NPN visible at a glance.
Tell apart branches you set up yourself from branches a market created for you, so you know which ones you can edit directly.
Add a new branch under your TopCo when you open a new office, acquire an agency, or split out a line of business.
Rename a branch without disturbing its NPN, members, or compliance history.
Take over a branch a carrier or MGA created in your account so you can manage its users and documents directly.
Open the Merge Duplicate NPN workflow when two branches turn out to represent the same legal entity.
Accessing Org Structure
Org Structure is a section inside the global Settings modal, which opens on top of whatever page you are currently on.
From anywhere in the app, open Left sidebar (bottom) → Settings. The Settings modal opens.
In the left-hand list, under the Organization group, click Org Structure (the network icon, subtitle "Manage your organization structure and hierarchy").
The Org Structure panel loads inside the modal. The page you were on stays open behind the modal and is restored when you close it.
If your plan does not include Org Structure management, the panel is replaced by an upgrade prompt instead of the tree.
What's visible on the page
Element | Description |
Organization Structure banner | Header at the top of the panel reading "You can manage your organization relationship structure here. This allows you to define the relationship between your organization and its branches." |
Merge Duplicate NPN button | Secondary button in the top-right. Routes you to the Branch Management workflow used to consolidate two or more branches that share an NPN. Shown only to users with branch-management permission. |
Add New Agency button | Primary button in the top-right. Opens the Add New Agency slide-over. Shown only to users with permission to update the org structure. |
Organization tree | An expandable accordion with your TopCo at the top and your branches listed beneath it. Click the TopCo row to expand or collapse the list of branches. A branch-less org shows No Branches in place of the list. |
If the structure cannot load, the panel shows a No data available message reading "Unable to load organization structure. Please try refreshing the page."
What each tree row shows
Element | Description |
Building icon | Highlighted (primary blue) for the TopCo, muted gray for branches. |
Legal name | The legal name of the entity, shown as the largest line in each row. |
TopCo badge | Blue badge marking the top-level entity at the root of the tree. |
Branch badge | Gray badge marking a child entity under the TopCo. |
External badge | Yellow badge that appears next to a branch created by an outside organization (typically a carrier or MGA). Click it to see which organization created the branch and which user submitted it. |
Branch name | The branch-specific display name, shown immediately under the legal name. |
NPN line | Shows NPN: followed by the number with a green checkmark when the branch has an NPN on file, and a copy icon to copy it. Shows No NPN assigned when none is recorded. |
Convert to Internal action | Inline button on the right side of any externally-created branch. Lets you take over the branch. |
Click a branch row to open the Update Branch slide-over and rename it. The TopCo row toggles the tree open and closed rather than opening an editor. Editing a branch requires update permission on the org structure.
Adding a New Agency
When you'd do this. You opened a new office, acquired another agency, or split a line of business onto its own legal entity, and you want that branch to start carrying its own licenses, documents, members, and policies inside Turris.
Click Add New Agency in the top-right of the Org Structure panel.
The Add New Agency slide-over opens with the subtitle "Add a new branch agency under your organization".
Decide whether the new branch needs an NPN using the Require Agency NPN? toggle at the top of the form. Leave it on (the default) when the branch carries licenses. Switch it off for a sole-proprietor branch in a state where sole proprietors are not required to have an NPN.
Fill in the identity fields:
Field | Required | Description |
Agency NPN | Yes when Require Agency NPN? is on | The branch's National Producer Number. Digits only. Entering it auto-populates Agency Name from the NIPR record. Example: |
Agency Name | Yes | The legal name of the agency, 2 to 100 characters. Locked and auto-filled when an NPN is entered, or when the lookup returns "not found". Example: |
Branch Name | Yes | The display name for this specific branch, 2 to 100 characters. Used across the app to tell apart branches that share a legal name. Example: |
Entity Type | Yes | Legal classification of the entity. Pick from the dropdown (LLC, Corporation, and so on). |
Doing Business As | No | Trade or DBA name. Example: |
Website | No | Public website URL. Must start with |
Phone Number | No | Branch phone number in the format |
Fax | No | Branch fax number in the format |
Scroll to the Address section and complete the Legal Address:
Field | Required | Description |
First Line | Yes | Street address line 1. Example: |
Second Line | No | Suite, unit, or floor. |
City | Yes | City name. |
State | Yes | Pick from the US states dropdown. |
Zip | Yes | Postal code. Example: |
Handle the mailing address. The Mailing address same as legal address? toggle starts off, so the Mailing Address fields (same shape as the legal address) are shown and required by default. Turn the toggle on to reuse the legal address and hide the mailing fields.
Click Add Agency at the bottom of the slide-over.
A success alert reads "Agency created successfully" and the new branch appears in the organization tree.
Tip: When you do not yet know the agency's NPN, switch Require Agency NPN? off so you can type the legal name manually. Add the branch again with the correct NPN once it is issued, then merge the two if a duplicate results.
Note: The Add New Agency button is hidden if your account lacks permission to update the org structure, and the whole panel shows an upgrade prompt if your plan does not include Org Structure management.
Updating a Branch
When you'd do this. A branch's display name has changed (a rebrand, an office relocation, or an internal reorganization) and you want the new name to appear everywhere Turris references that branch.
In the organization tree, click the branch row you want to update.
The Update Branch slide-over opens with the subtitle "Update details for [Legal Name]".
Edit the Branch Name field. It is required, must be 2 to 100 characters, and is the only field you can change here.
Field | Required | Description |
Branch Name | Yes | The branch's display name, 2 to 100 characters. Example: |
If the branch has an NPN, a Current NPN: box appears below the field for reference. The NPN is not editable here.
Click Update.
A success alert reads "Branch updated successfully" and the new branch name appears in the tree.
Note: A branch's NPN cannot be changed after creation. The Update Branch panel states "NPN cannot be modified after creation. Contact support if you need to change the NPN."
Converting an External Branch to Internal
When you'd do this. A carrier or MGA created a branch in your account during onboarding (for example, to attach an appointment to a specific office), the branch carries a yellow External badge, and you want to take ownership so your team can edit it, assign users to it, and upload documents against it directly.
Find the branch with the yellow External badge in the organization tree.
Click the Convert to Internal button on the right side of that branch's row.
A confirmation modal opens with the heading Convert to Internal Organization and the message "Are you sure you want to convert "[Legal Name]" from an external organization to an internal one? This will allow you to manage this organization directly within your compliance system."
Click Convert to Internal to confirm, or Cancel to back out.
A success alert reads "Branch converted to internal successfully".
A follow-up modal titled Branch Converted Successfully reminds you that some member roles were updated automatically (Pending Admin became Admin, Pending Legal became Legal). Click Close to dismiss it.
The External badge is removed and you can now edit the branch like any other internally-managed one.
Warning: Conversion automatically promotes any Pending Admin members to Admin and any Pending Legal members to Legal on the converted branch. Open the Users settings page after every conversion and confirm each member holds the correct role for your organization.
Merging Duplicate NPN
When you'd do this. You spot two or more branches in your tree that represent the same legal entity (most often after onboarding from multiple carriers or MGAs that each created their own version of a branch), and you want to collapse them into one so reporting, documents, and licenses stop being split.
Click Merge Duplicate NPN in the top-right of the Org Structure panel.
You are routed to the Branch Management workflow, a dedicated page outside the Settings modal.
Follow the on-screen workflow to review the candidate branches and complete the merge.
Visual Indicators
Color or Icon | Label | Meaning | What to do about it |
Blue badge | TopCo | The top-level entity in your organization, at the root of the tree. | Keep its legal name and NPN current. This is the identity your markets see first. |
Gray badge | Branch | A child entity under your TopCo. | Click the row to update the branch name. Use Convert to Internal if it also carries the External badge. |
Yellow badge | External | The branch was created by an outside organization, typically a carrier or MGA partner. | Click the badge to confirm which organization and user created it. Convert it to internal when you want to manage it yourself. |
Green checkmark | NPN recorded | The branch has an NPN on file, so Turris can use it for compliance lookups. | Nothing required. |
Gray text | No NPN assigned | The branch was added without an NPN. Common for sole-proprietor branches in states that do not require one. | Add the NPN later if regulations require it. There is no way to add an NPN to an existing branch from this page; contact support if the change is needed. |
Highlighted building icon | TopCo row | Marks the top of the hierarchy. | Visual cue only. |
Muted building icon | Branch row | Marks a child entity. | Visual cue only. |
Frequently Asked Questions
Why don't I see the Add New Agency button? The button is only shown to users with permission to update the org structure. If you do not see it, ask an administrator in your organization to update your role on the Users settings page.
Why is the whole Org Structure panel showing an upgrade prompt? Org Structure management is a premium feature. If your plan does not include it, the panel is replaced with an upgrade prompt. Contact your Turris account manager to enable the feature.
Why can't the NPN on a branch be edited? NPNs are tied to regulatory filings and license records, so they are locked after creation. If the NPN is wrong, contact support so the correction can be reviewed and applied without breaking compliance history.
What does the yellow External badge mean? The branch was created by a carrier or MGA partner you work with, before you took ownership of it inside Turris. You can still view the branch, but some edits are blocked until you convert it to an internal branch.
Should I convert every External branch to internal? Convert the branches you actively manage. Leave a branch external when a partner is responsible for maintaining it on your behalf. Conversion is one-way from this page.
Why was a member's role updated automatically after I converted a branch? Pending roles such as Pending Admin and Pending Legal become full Admin and Legal roles when the branch becomes internally managed, because those pending states are only valid for external branches. Always review the Users settings page after a conversion to make sure the resulting roles are correct.
Can I delete a branch from this page? No. Branches cannot be deleted here. If a branch was created in error, contact support so the change can be reviewed safely before removal.
Can a branch have two NPNs? No. Each branch has at most one NPN. When two branches end up with the same NPN, use Merge Duplicate NPN to consolidate them.
Best Practices
Add every branch your organization operates. A complete tree makes user assignment, document storage, license tracking, and reporting accurate for every line of business.
Use a specific Branch Name. The branch name is the line that tells apart branches sharing the same legal name across the app. "Acme Denver" beats "Acme Branch 3".
Provide the NPN when you have one. Recording the NPN unlocks compliance lookups and prevents partners from creating a duplicate branch later.
Review External branches as soon as they appear. When a carrier or MGA creates a branch in your account, decide quickly whether to keep it external or convert it. Long-running externals mean documents and users land on the wrong entity.
Audit members after every conversion. Pending roles become full roles when an external branch is converted. Open the Users settings page each time and confirm each member's access level matches your intent.
Consolidate duplicates with Merge Duplicate NPN. Two branches sharing one NPN cause confusing licensing and reporting. Run the merge workflow as soon as you spot a duplicate.
Keep TopCo details accurate. The TopCo row represents your whole organization to every market. Its legal name and NPN feed onboarding packets, data rooms, and contract signatures, so treat any change there with care.
Related Pages
Contacts (Settings): Keep one organization-wide directory of the people your agencies rely on when working with their markets.
Documents (Settings): Keep every compliance document (E&O, Cyber, Crime & Fidelity, W9) for your organization in one place.
Billing: Invoices: Search the full history of every Stripe invoice issued to your organization.
Settings: Personal Notifications: Decide how Turris alerts you about activity across the agencies and agents you manage.
Payment Methods (Settings): Save and manage the cards used to pay Turris invoices and future charges.
Users (Settings): Control who can sign into Turris, which agency each person belongs to, and what they can do.
Need Help?
If you have questions about Org Structure or encounter any issues, contact our support team at support@turris.com.