# Get started

Product: Identity Universe
Source: https://docs.fortytwo.io/identity-universe/iam-core/get-started/

## Admin consent to Fortytwo Universe

Consent has to be granted by a Global Administrator, once per tenant. See [get started](https://docs.fortytwo.io/identity-universe/get-started/) for details, and [Administrator permissions](https://docs.fortytwo.io/identity-universe/get-started/permissions/) for the roles that have to be assigned afterwards.

## Setting up IAM Core

Getting from an empty tenant to useful data is four steps, in this order.

### 1. Add a connector

A [connector](https://docs.fortytwo.io/identity-universe/iam-core/connectors/) brings a source system into IAM Core. Start with whichever system is authoritative for people — usually HR.

```PowerShell
Install-Module Fortytwo.IAM.Core.Admin -Scope CurrentUser
Connect-IAMCore

Get-IAMCoreConnectorTemplate
```

If you just want something to look at, the [demo data connectors](https://docs.fortytwo.io/identity-universe/iam-core/connectors/demodatahr/) populate a fictional municipality and need no credentials.

### 2. Look at what arrived

Before writing any rules, see what the source actually produced. Sync rules are written against these exact attribute names, so this step saves a lot of guessing:

```PowerShell
Get-IAMCoreConnectorDataStatistics -Id $Connector.id

Find-IAMCoreConnectorDataObject -ConnectorId $Connector.id -ConnectorObjectType "person" |
    Select-Object -First 1
```

### 3. Write sync rules

[Sync rules](https://docs.fortytwo.io/identity-universe/iam-core/sync/syncrules/) decide which connector objects matter and what they become. The usual order is org units first, then identities, then the relationships that tie them together.

Build them up one at a time and preview before committing:

```PowerShell
Get-IAMCoreConnectorDataObjectSyncPreview -ConnectorId $Connector.id -ConnectorObjectId $Object.id
```

### 4. Synchronize

```PowerShell
New-IAMCoreSyncJob | Wait-IAMCoreSyncJob
```

Then check the result:

```PowerShell
Get-IAMCoreIdentity | Select-Object -First 5
Get-IAMCoreOrgUnit | Show-IAMCoreOrgUnitStructure
```

## Adding a second source

Once one system is flowing, additional systems join onto what is already there rather than creating duplicates. The second connector's rules are usually [join only](https://docs.fortytwo.io/identity-universe/iam-core/sync/syncrules/#provisioning) — they enrich existing identities instead of provisioning new ones — and [priority](https://docs.fortytwo.io/identity-universe/iam-core/sync/syncrules/#priority-and-attribute-ownership) decides which system wins where both supply the same attribute.