> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/administration/connecting-unanet.md).

# Connecting Unanet ERP A/E

Cogram syncs your firm's **Unanet ERP A/E** (formerly Clearview InFocus) **projects and opportunities** into Cogram and keeps them up to date automatically. An admin sets it up once with a firm API key.

Sync is **one-way**: Cogram reads from Unanet and never writes back.

<details>

<summary>How the sync works</summary>

```mermaid
flowchart LR
    U["Unanet ERP A/E<br/>(project registry)"]
    U -->|"Firm API key<br/>~6h sync + instant webhook"| CG["Cogram"]
    CG --> P["Projects"]
    CG --> O["Opportunities"]
    CG --> R["Project roles<br/>owner + team members"]
```

Cogram uses one **firm API key** (org-level) to import projects and opportunities, assign project roles (owner plus team members, matched to existing Cogram users by email), and refresh them on a schedule and on live events. Imported projects are stored in Cogram. Cogram never writes back to Unanet.

</details>

## Part 1: Set up the organization project sync (admin)

> **You need:** Owner or Admin role in Cogram, your Unanet tenant's Base API URL, and a Unanet **API key** for your firm.

### Step 1: Get your Unanet API key

In Unanet, go to **Administration → API Management → Manage Keys** and copy an API key for your firm. This key lets Cogram read your projects and opportunities.

> Treat the API key like a password. Use a key dedicated to the integration if your Unanet setup allows it, so it keeps working if staff change.

### Step 2: Open the integration in Cogram

Go to [**Organization Settings → Integrations**](https://app.cogram.com/dashboard/settings/admin/integrations) and click **Unanet ERP A/E**.

### Step 3: Enter the connection details

| Field            | Value                                                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Base API URL** | Your tenant address, usually `https://<your-firm>.infocusapp.com/platform`. Note the `/platform` suffix. Cogram warns you if it's missing. |
| **Database**     | Click **Detect** to look up the databases at that URL. If there's one, it's filled in; if there are several, pick the right one.           |
| **Firm API Key** | The key from Step 1.                                                                                                                       |

> The Base URL must be **HTTPS**. Ask your Unanet administrator if you're unsure of your tenant address or which database to use.

Click **Test** to confirm the API key works for that tenant and database before saving.

### Step 4: Turn on Project sync

In the **Project sync** card, switch **on** *"Import this organization's Unanet projects and opportunities into Cogram."*

Then pick a **Sync owner**. This Cogram user owns each synced project until Cogram matches the Unanet project manager or principal to a Cogram user by email on a later sync.

To make imported projects easy to find, check **Make newly synced projects discoverable**. Projects the sync creates then appear in the organization-wide project directory, where members can find them and request access; see [Project discoverability](/guides/projects.md#project-discoverability). This applies only to projects imported after you turn it on; projects already in Cogram keep their current discoverability setting.

Click **Save** to apply the sync settings.

### Step 5: Run the first sync

Click **Sync now** to import immediately (otherwise the first sync runs on the next scheduled cycle). Projects appear in the background within a few minutes for typical firms; longer for large accounts.

**What gets imported:**

* One Cogram project per Unanet project, with its **name** and **project code**.
* Opportunities alongside projects.
* The project **owner**, matched from the Unanet project manager / principal by email, or the Sync owner as a fallback.
* **Team members**: the project's Unanet team roster, added as project members.

Owners and team members are matched to Cogram users **by work email**. Only people who are already Cogram users receive a role; Unanet sync never creates or invites accounts. Roles you set manually in Cogram are left untouched.

After the first sync, Cogram refreshes automatically **about every 6 hours**. The card shows the last-sync time and a **Sync now** button to pull changes on demand.

## Part 2: Instant updates (webhook)

The \~6h sync keeps Cogram current, but a new or edited project can take hours to appear. The **instant-updates webhook** closes that gap: Unanet notifies Cogram the moment a project changes, so updates land in **seconds**. The periodic sync stays on as a backstop that reconciles anything a webhook missed.

Setup has two sides: enable it in Cogram (to get a URL), then register that URL in Unanet's Event Manager.

### Cogram side: enable and copy the URL

> The **Instant updates (webhook)** card appears once **Project sync** is enabled (Part 1).

1. Switch **on** **Instant updates (webhook)**.
2. Copy the **Webhook URL**. It contains a secret token unique to your organization; treat it like a password.

**Rotating and disabling:**

* **Regenerate URL** issues a new URL and **invalidates the old one immediately**. Use it if the URL may have leaked, then update it in Unanet.
* Turning the webhook **off** keeps the same token, so re-enabling later reuses the same URL, with no need to re-edit Unanet.

### Unanet side: register the URL in Event Manager

Have your **Unanet administrator** do this in the Unanet desktop client. Follow the numbered steps in the screenshot:

<figure><img src="/files/sLd8J8E6lTwXyvTeg8Qk" alt="Unanet ERP A/E Event Manager showing the Projects event list and the Settings/Webhooks tab, annotated with the five setup steps" width="900"><figcaption><p>Unanet Event Manager: the five-step webhook setup</p></figcaption></figure>

1. Open the **Administration** module (bottom-left).
2. Go to **Event Manager**.
3. In the category dropdown, select **Projects**.
4. For each of these five events, select it, check **Track Event** and **Process Webhooks**, and under the **Webhooks** tab add a row with Method **POST** and the Cogram Webhook URL:
   * `Project - Created`
   * `Project - Saved`
   * `Project - Activated`
   * `Project - Deactivated`
   * `Project - Deleted`
5. Click **Save** (top-left), **once for every event you changed**. This is the most-missed step: an unsaved event silently sends nothing.

> **Additive.** Leave any existing webhooks (for example a Newforma integration) in place; add the Cogram row alongside them. An event can POST to more than one URL.

## Synced projects in Cogram

Synced projects appear in everyone's [project list](https://app.cogram.com/dashboard/projects) automatically, with no per-user setup. Each shows its Unanet **project code**, **name**, and **team** (the project manager / principal as owner, plus the project members) for everyone matched to a Cogram user by email.

Core details are managed in Unanet: edit them there and they update in Cogram on the next sync, or in seconds when instant updates are on. Meeting notes, emails, field reports, and drawings work as usual.

The synced Unanet data (project id, lead stage, your user-defined fields, and the project's market sectors with their percentage split) is also readable through the [Cogram API](/administration/cogram-api.md); see the [interactive API docs](https://api.cogram.com/v1/docs) for the project response fields, so your own integrations can join Cogram projects back to Unanet.

## Managing the connection

### Change or remove the org connection (admin)

In [**Organization Settings → Integrations → Unanet ERP A/E**](https://app.cogram.com/dashboard/settings/admin/integrations), update the Base URL, database, or API key (leave the key blank to keep the stored one), or click **Remove** to delete the connection entirely. Removing it hides the integration for everyone in the organization.

### Stop syncing

Switch **Project sync** off and **Save**. Existing Cogram projects are preserved; the scheduled sync pauses until you re-enable it. With sync off, the instant-updates webhook is ignored too: no sync fires.

## Troubleshooting

#### Test fails: "API key not recognized"

Unanet didn't accept the API key for that database. Re-check the key under **Administration → API Management → Manage Keys** in Unanet, and confirm the **Database** is correct.

#### Detect finds no databases (admin)

Double-check the Base URL. It should be your tenant address ending in `/platform` (e.g. `https://acme.infocusapp.com/platform`). Confirm the tenant is reachable, and ask your Unanet administrator if unsure.

#### Projects aren't updating instantly

Confirm the webhook is set up on the Unanet side: for **every** event, both **Track Event** and **Process Webhooks** must be checked **and** the event **Saved**. A missed event is still reconciled by the \~6h full sync. Also check that **Project sync** is on in Cogram; with sync off, the webhook is ignored.

#### Project owner is the Sync owner, not the project manager

The Unanet project manager / principal email doesn't match a Cogram user. Invite that person to Cogram; the next sync assigns them.

#### A Unanet team member isn't on the project in Cogram

Sync assigns roles only to people who are already Cogram users, matched by work email. Invite them to Cogram (and confirm their Unanet work email matches); the next sync adds their role. Unanet sync never creates accounts.

#### I don't see "Unanet ERP A/E" in Organization Settings

Your organization may not have the integration enabled. Contact <support@cogram.com>.

## Per-user agent (early access)

> **Early access.** This is separate from project sync (above) and still evolving. It imports nothing. It lets Cogram Agent query Unanet **live and read-only**, scoped to what each person can see in Unanet.

Once an admin has connected the organization (Part 1), each person can link their own Unanet login:

1. Go to [**Account Settings → Integrations**](https://app.cogram.com/dashboard/settings/account-settings/integrations) and find **Unanet ERP A/E**.
2. Enter your Unanet **username** and **password**, then **Save**. Your password is encrypted at rest and never shown back to you.
3. Click **Test**: Cogram signs in to Unanet as you and confirms it works.

Then ask Agent in plain language, for example *"List our Unanet projects"* or *"Show me our Unanet clients."* Results are fetched live and scoped to your Unanet account.

**Troubleshooting:**

* **I don't see "Unanet ERP A/E" in my Account Settings**: an admin hasn't connected the organization yet. Ask your admin to complete [Part 1](#part-1-set-up-the-organization-project-sync-admin).
* **"Authentication failed" after Test**: Unanet rejected the sign-in. Confirm your username and password (try signing in to Unanet directly), re-enter your password in Cogram, and Test again.

## Next steps

**For admins:** [Connecting Deltek VantagePoint](/administration/connecting-vantagepoint.md), [Organization Roles](/administration/organization-roles.md)

**For everyone:** [Projects](/guides/projects.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cogram.com/administration/connecting-unanet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.