# Departmental Sub-Org Setup

- Link: https://www.agilicus.com/anyx-guide/departmental-sub-org-setup/
- Published: 2025-03-16T16:29:14+00:00
- Author: Don Bowman

1. [Home](https://www.agilicus.com/)
 2. Departmental Sub-Org Setup

![Departmental Sub-Org Setup in AnyX: Visual representation of a hierarchical organizational
structure showing the parent organization at the top, branching down to various 
departments (e.g., Sales, Marketing, Engineering) as sub-organizations. Each department
can have its own members, resources, and policies, enabling decentralized management
within a larger enterprise using AnyX.](https://www.agilicus.com/www/426fe689-department.
svg)

## Departmental Sub-Org Setup

Example methods of managing departmental needs with respect to budget/invoice, administrative
privilege, and uses who may span departments.

[CONTACT](https://www.agilicus.com/contact-us/)

## Departmental Sub-Org Setup

Your company has multiple independent departments. Each have their own users and
administrative needs. Some users may work for multiple departments. In this document
we discuss 4 setup techniques in Agilicus AnyX, and the pro/con of each.

All 4 methods achieve the same objective, and are equally secure.

Resources and connectors cannot be shared across Orgs, meaning if you have a single
Resource you want multiple departments to use, you must either use a hierarchical
model (where all users needing the share resource are in the same org, and optionally
in a child), or, you must dual-configure the resource (e.g. 2 connectors lead to
it, and, the resource is created in each Org where users might require it).

### Method #1: Sibling

In this model, there are 3 Orgs created. The parent (“My Company”) has only the 
global admin(s): it has no resources, no connectors. There is 1 (or more) global
admin users in the parent org, but no end-users, no departmental admins.

![departmental sub-org-method-1_ sibling](https://www.agilicus.com/www/09beb556-
departmental-sub-org-method-1_-sibling.svg)

![image](https://www.agilicus.com/www/8a139aad-image-1024x796.png)

The end users will all use the same profile URL (https://profile.__MYDOMAIN__). 
They will each see a custom view, only their resources. Users in both orgs will 
see navigation folders.

This method is best suited to a non-overlapping set of users and resources, perhaps
split geographically or by division.

### Method #2: Parent-Child

In this model there are 2 Orgs created. The parent (“My Company”) has all of the
common users and resources (as well as global admins). A ‘Child’ org is setup for
each team with its own admin/resource needs.

![departmental sub-org-method 2_ parent-child](https://www.agilicus.com/www/9100051a-
departmental-sub-org-method-2_-parent-child.svg)

The end users will all use the same profile URL (https://profile.__MYDOMAIN__). 
They will each see a custom view, only their resources. Users in both orgs will 
see navigation folders.

This method is best suited where most users have something shared, and some users
have things not shared.

### Method #3: Peer

In this model, 2 top-level Orgs are created. There is nothing shared between them.

![departmental sub-org-method 3_ peer](https://www.agilicus.com/www/b5777a59-departmental-
sub-org-method-3_-peer.svg)

In this model, end users each have their own profile URL (https://profile.team-1.
__MYDOMAIN__ and https://profile.team-2.__MYDOMAIN__). There is no ability to have
shared resources: if a resource is needed by both teams, it must have 2 connectors
setup, and, be configured in each org.

This peer model facilitates invoicing to separate corporations (e.g. different tax
numbers, addresses).

### Method #4: 1 Org with Permission Management

In this model there is only 1 global admin, no departmental admins. User permission
is managed to ensure that each user gets access to only their department’s resources.

![Departmental Sub-Org Setup: Single Org Method - Visual representation of a single
organization structure with clearly defined departments or sub-organizations. Illustrates
the hierarchy and relationships between different departments within a unified organizational
framework. Ideal for understanding sub-org implementation strategies.](https://www.
agilicus.com/www/caad5c5b-departmental-sub-org-method-4_-single-org.svg)

![Departmental Sub-Organization Setup in AnyX. Structure your organization in AnyX
to reflect departments or teams, enabling granular access control and resource management.
The diagram illustrates a hierarchical structure with a parent organization at the
top, followed by sub-organizations representing different departments (e.g., Marketing,
Sales, Engineering). Each sub-organization contains users and resources, ensuring
proper access permissions and segregation of duties. Optimize your AnyX configuration
for enhanced security and streamlined operations.](https://www.agilicus.com/www/
2880cde5-image.png)

This model is more work to administer, and has some risks of mis-configuration. 
However, it is simpler to operate, simpler to audit.

## Pro / Con

Sibling

Parent-Child

Peer

Permission

Per-Org Invoice

✅

✅

✅

Single-Navigation URL

✅

✅

✅

✅

Delegated Admin All

✅

✅

Delegated Admin Child

✅

✅

✅

Single Merged Invoice

✅

✅

Shared resource/connector

✅

✅

## Migration Notes

If you have a single org with all users in it, and wish to migrate to one of these
models, consider the following steps:

 1. Create new orgs as needed (except for model #4).
 2. Create new connectors in new orgs
 3. Create new resources in new orgs
 4. Create user groups in new orgs
 5. Create users into new orgs
 6. Delete users from orgs they no longer need.

![image](https://www.agilicus.com/www/f3c1db5b-image-1024x691.png)

To create a new org, use Organisation/New menu (Model #1/Model #2). Give this a 
name of e.g. the department.

For Model #3 (Peer), you would need to run through the [Signup](https://www.agilicus.com/anyx-guide/signup/)
process again.

For Model #4, Orgs are not used and can be ignored.

![image](https://www.agilicus.com/www/1b0148a3-image-1024x732.png)

Consider who will have administrative abilities in each of the new Orgs. You can
add them directly to the administrative permissions as at the right, or, create 
a group (e.g. ‘org-admins’), add them to that, and and then add the org-admins to
the administrative system group.